[Event Follow-Up] Preserving Your Fusion Scenarios During the Event Subscriptions V2 Upgrade – May 2025

[NicholeVargas]

First and foremost, a huge thank you to Erika and Brooke from the Adobe Software Development Team for taking the time this morning to share their expertise and recommendations around upgrading Fusion scenarios to Event Subscriptions V2. If you weren't able to attend, you're in luck - below are links to the slide deck and recording, along with a short summary of what was explained: 

• Slide Deck PDF 
• Workshop Recording 

Resources and Recommendations: 

• Review the documentation on event subscriptions V2 changes to understand all potential impacts, as today’s session only covered the 2 biggest changes.  
  • Only scenarios that start with Adobe Workfront watch events module or custom webhook modules need to be migrated; Workfront planning watch events modules are already on v2 
  • All new subscriptions created after the 25.2 release (April 10, 2025) are created as Version 2. 
  • The two major changes in V2 are multi-select fields will always return as arrays (even with single selections), and objects created from templates with calculated custom fields will only trigger create events (not update events). 
• All scenarios will be automatically updated on January 15, 2026, so be sure to test event subscriptions with V2 before then!  
• During the 5-minute window after upgrading, users will receive duplicate events (both V1and V2) to ensure no events are missed during the transition. 
• Users can check which version their subscription is on by examining the event payload in scenario history or by using the event subscriptions API. 

A list of FAQs from the event are published below as comments, so be sure to review those for more information. We are looking to do another session on this topic so that everyone gets their questions answered and feels confident on what needs to be done prior to the January 15, 2026 deadline, so stay tuned for more! 

[NicholeVargas]

Question: Will it be possible to have OR statements in event filters?  

Answer: It's not possible with the standard Fusion UI, but it is possible to create custom webhooks to create simple OR statements. You can also point multiple subscriptions to the same webhook that results in OR operators. The downside is that this is not visible on the Fusion UI. We (Workfront) are planning support for this in the second half of the year. 

[NicholeVargas]

Question: Is there any way to run a report to easily determine which scenarios have V1 and which have V2? 

Answer:It's a good question. There isn't yet, but we are working with the Fusion team/our counterparts on the Fusion UI to try and develop that report to get to customers.

But (tip from the chat) if you are familiar with Postman, or curl you can use the Admin API in Fusion (you generate the API Key from the "Profile" section in Fusion). Examples of reading the Webhooks in Fusion are available on the https://make.com documentation. https://developers.make.com/api-documentation/api-reference/hooks 

[NicholeVargas]

Question: Would you recommend upgrading the scenarios during off-hours to limit duplicate events?   

Answer: I would say it's dependent on what your biggest concern is. If you do it during the off hours, you're going have less duplicates for sure. But you might also have less data to tell you that there might be a problem with the V2 events. So, it really depends. You can always create a test instance for your common use case or a test event and run a test that you can see both events come through to confirm that it behaves as you expect it would.  

[NicholeVargas]

Question: Is there anything that customers should take into consideration or look for when bulk updating all subscriptions at once other than failed scenarios?  

Answer: That I again, I would say is dependent on what you're most concerned about. But if you do upgrade all your scenarios at once, if you have a lot of scenarios, that's a lot to manually watch. I would say failed scenarios is probably the best way to tell that there is an issue. 

[NicholeVargas]

Question: Is the only to see that it's currently a V1 or V2 through a scenario that has run. Meaning you have to click into every scenario, look at a historical run? 

Answer: In Fusion, that's the only way to see. Event subs does have an API where you can go get your subscription and it will tell you if it's V1 or V2, but you'd have to hit our API directly in Fusion. I think that the only way to tell is once your scenario has run once and looking at the event payload. Our public API does have an end point that you can list all subscriptions at the same time and that would tell you which ones are on V1 still.  

[NicholeVargas]

Question: Is the only way to view and manage events subscriptions through the Workfront API? Or is there a place in Workfront where we can view those? 

Answer: Unfortunately, the answer is it is only via the API at this time.  

[_Manish_Singh]

Hello @NicholeVargas - I would like to highlight an API call discrepancy related to the multi-selection topic discussed at 13:10 in the video. The issue is not directly related to the event subscriptions but highlights multi-selection field behaviour in the API call when a single value is selected versus multiple selections.

When a single selection is made, the API call returns a string:

However, when multiple values are selected, it returns an array:

For consistency, multi-selection API calls should return an array even for single selections, as it causes issues while dealing with external lookups.

It would be great if you can share this with Erika and the engineering team at Adobe.

[NicholeVargas]

@_Manish_Singh Thanks for reaching out and sharing this concern - I've passed this along to the Software Development team for additional consideration! 

[bhorrocks]

Hi @_Manish_Singh, thanks for bringing this up. You are correct that the multi-select field returning a string if only a single value is selected is not solely related to Event Subscriptions. While v2 Event Subscriptions will start returning arrays no matter how many options are selected, the Workfront API does still return a string when a single value is selected. 

This is something that is going to change with the release of the v21 Workfront API which is scheduled for September 2025. Once that is released, you can see the desired behavior when using v21 of the Workfront API directly. Hope that helps!

[viovi]

It was mentioned that we could get a list of existing subscriptions via API. Could you please provide an example of such request?

[bhorrocks]

Hi @viovi, yes you can get a list of existing subscriptions via the API. If you are familiar with cURL, below is a snippet of an example request. 

curl --request GET \
  --url https://<HOSTNAME>/attask/eventsubscription/api/v1/subscriptions \
  --header 'sessionID: <SESSION ID>'

This will return a response similar to the below:

{
	"subscriptions": [
		{
			"id": "<SUBSCRIPTION ID>",
			"dateCreated": "2024-10-10T16:00:00.217157",
			"dateModified": "2024-10-10T16:00:00.217157",
			"authToken": "<AUTH TOKEN>",
			"customerId": "<CUSTOMER ID>",
			"eventType": "UPDATE",
			"objCode": "PROJ",
			"objId": "",
			"url": "<URL>",
			"base64Encoding": false,
			"subscriptionUrl": {
				"url": "<URL>",
				"dateCreated": "2024-10-10T16:00:00.217157",
				"successes": 1,
				"failures": 0,
				"disabledAt": null,
				"frozenAt": null
			},
			"filters": [],
			"filterConnector": "AND",
			"version": "v2", # HERE IS WHERE THE SUBSCRIPTION VERSION IS
			"dateVersionUpdated": "2025-01-15T04:22:03.557054"
		}
	],
	"meta": {
		"page": 1,
		"limit": 100,
		"page_count": 1,
		"total_count": 1
	}
}

In the above example, there is only a single subscription but it will return a list of subscriptions if you have more than one. This endpoint is also documented in our public documentation here, I recommend referencing this page when making your request.

[viovi]

@bhorrocks, thank you!

Where can we get the sessionID as the DevTool in Fusion does not show it. Could you please advise?

[bhorrocks]

Sorry for my late reply. This page details how you can get a sessionID using the Workfront API.