Upgrade to Event Subscriptions V2

Transcript

All right, we are one minute after the hour, so I’m going to go ahead and get started because I imagine you guys are going to have a lot of questions on today’s session. So if you just happen to stumble in, or if this is your very first customer success workshop, welcome. Today we’re going to be talking about preserving your work front fusion scenarios during the event subscriptions, the two upgrade.

Couple things here from an agenda standpoint, I’ll go through some introductions here, and then I’ll hand it off to our guest speakers here to kind of walk you through event subscriptions, what’s changing, what’s coming with V2, and how to sort of best prepare your fusion scenarios during that process.

From a housekeeping standpoint, I am going to be recording today’s session, so you guys will get a copy of the recording in your follow-up email. I’m hoping to get that out within a few hours post event, so keep an eye out for an email. After the event, you’ll get a copy of the recording, you’ll get a copy of the slide deck. If there’s resources or questions that I need to summarize, I can absolutely pull those into the follow-up email as well because this is a session focused on work front fusion. If you guys don’t have fusion, this session is really not going to be really related to your instance, so I’m just going to let you know, you might want to just pay attention, listen in the background.

It is going to be a little bit more for advanced experience fusion admin users who are needing to migrate and upgrade their event subscriptions to V2 before our deadline in January.

Everyone should have two options or three options, or I guess multiple options. In your MS Teams header, I think it’s at the bottom of your screen if I’m correct, you’ll have a chat pod, which is where you can sort of ask your peers questions, folks on this call. If you are interested in asking a question to our speakers, I encourage you to put that in the Q&A pod, and that way we can sort of track question and response versus having to dig through the entire chat. So again, chat is for maybe asking your peers, customers in attendance, some questions, recommendations, best practices. The Q&A is for our speakers here. Everyone does have the option to come on camera and off mute. Although I would encourage you to kind of hold your questions until Erica and Brooke are done speaking here. We kind of gave you the microphone option just in case you have a question and need to explain it, but you’re always more than welcome to just raise your hand at any point. If you’re like, hey, can you, we just pause here for a second, I have a question.

I think that’s all I have for housekeeping. So let me just reiterate this again, it’s going to be recorded. You’re going to get a copy of this recording, the slide deck and a follow-up email from CSS scale, which is just our team’s email address. So if you have any follow-up questions, you’re always more than welcome to reply to that. And then last but not least, just some introductions. So if you guys haven’t met me before, I am Nicole Vargas. I’m a senior customer success manager here at Adobe Workfront. I have been with Workfront about seven and a half years now. And while I have no or not too much deep expertise in the workstation, hence why I brought on our guest speakers here, Brooke and Erica. And so, Erica, I’ll let you introduce yourself first.

Yeah, hi, I’m Erica O’Neill. I’m a senior software development manager here at Adobe and manage the team that’s working on the event subscriptions, what we’re talking about today. So fabulous, and Brooke.

Yeah, hi, I am a senior software development engineer. I’ve been here for about four years and been on the same team that has managed the event subscription service. So yeah, I’m excited.

Well, we are thrilled to have you guys. I know there’s been a lot of questions around what’s changing with event subscriptions fee two. And so with that, I’m going to stop sharing my screen and pass it off to Erica. So she could share her screen and kind of walk you guys through. So again, just a reminder, if you do have questions, Q&A pod, we’ll try and address those throughout the session, but you’re always more than welcome to just raise your hand. Take it away, or take it away, Erica. Awesome, thanks, Nicole. So super excited to be with you guys here today and really glad that you’re all here to hear about our event subscriptions fee two, cause we’re excited to talk about it. Just to start off and lay some ground foundation knowledge, when we’re talking about work front event subscriptions, just want to quickly explain what event subscriptions are. So anytime that you make a change in the work front application, the work front event subscription service is going to watch for those changes and then look for a subscription based on those changes in that customer’s instance and send it forward to either a registered web hook from you as a customer or to Fusion. So today, obviously we’re talking about the Fusion side of things and how event subs powers that. When we talk about it powering Fusion triggers, there are three Fusion modules that we talk about with event subscriptions. The first two are the Adobe Workfront Watch Events module. The second is the Workfront Planning Watch Events module. And then the third is the Custom Webhook module. So for the first two, these are always powered by event subscriptions. And for the third one, this one is sometimes powered by event subscriptions, but it has to be set up. So you would create the module in Fusion and then have to go to the event subscriptions API to register that endpoint. So if you haven’t gone to the event subscriptions API to register the endpoint or your Fusion experts haven’t, then this custom webhook module is likely not powered by event subs. But the other two are always powered by event subs. So when we talk about event subscriptions V2, and I’ll get a little bit more into the details in a minute, but you see this green check mark, the Workfront Planning Watch Events module is already on event subscriptions V2 and does not need to be migrated. So the only two that are related to this change from event subs V1 to event subs V2 is the Adobe Workfront Watch Events module. And then, like I said, sometimes that custom webhook module. So if you don’t have scenarios that start with those, then you don’t have to worry about this migration.

So let’s talk about what the event subscriptions V2 actually is. The first thing that I wanna point out is that we do recommend that customers, that you as customers migrate over to event subscriptions V2 starting anytime now up until January 15th. If you don’t migrate those fusion scenarios, those webhook modules by January 15th of next year, they will be automatically upgraded. And that’s not necessarily a bad thing. We do expect most scenarios to be unaffected by this migration. However, we do recommend for all customers to go migrate those beforehand so that you can make sure that all of the scenarios that you have are working as expected. So again, you can start that anytime now. And then on January 15th, those will all automatically be upgraded to V2. And Brooke will talk about this a little bit more when she talks about how to upgrade, but all new subscriptions, so every time you create a new Workfront Watch module, those are already on V2, so you don’t have to worry about migrating those. And again, Brooke will go over the details and how you can see which subscription version that you’re on with that module. Some of the benefits of V2, like I said, we’re super excited for version two to finally come out. It’s been a couple of years in the making, and it’s a whole new infrastructure that allows us some cool things coming up. So one, the first thing is increased reliability of delivery. So right now with event subscriptions, we do deliver close to 100% of events, but there are edge cases where we can drop messages with the way that the V1 architecture is set up. And so with this migration to V2, we can guarantee that we can deliver every single message and never drop any.

The second is support for new and upcoming Workfront features in event subscriptions. So again, that Workfront Planning module is a good example of something that we couldn’t support on V1 that we can now support on V2. It was completely built from the ground up with the V2 architecture. So with new features coming out in the future of Workfront, we can support those readily in event subscriptions. So that’s really cool too.

And then the third is we have over the years had a few small bugs in the V1 version of event subscriptions that we’re fixing with this V2 change. And I’ll go over those. They are mostly small and probably have gone unnoticed by a lot of scenarios, but there are certain cases that you’ll definitely see the value of those bug fixes.

So let’s talk about what’s changing. First thing that I want to mention is that we do have a super detailed breakdown of all of the changes that are happening between V1 and V2 in our Experience League documentation. So I’m just gonna show that to you really quickly.

So this page, and again, like Nicole said, this will be sent out. So you’ll have a link to this page. Has those dates that we mentioned, the January 15th date, and it has a detailed difference between all of the V1 and V2 changes. I’m gonna skip this general changes here for a second because I will go into detail about these two general changes in just a minute. But what we won’t go into detail about is all of these other changes down here. And like I said, it looks like a lot of changes. They’re broken down very specifically by the object type and the field type that they’re supporting and what the behavior is in V1 and V2. So I encourage you to go through that and make sure there aren’t any of those edge cases. These are the bug fixes I was talking about where they are small, but if you have a scenario that’s dependent on one of these bugs, like a lot of these are in the before and after state for a specific field, we’ll say it was null before and then it had a value after, when that’s just not the case, it had a value before it was just coming through as null. So if you’re dependent on that change or something like that, then you wanna update your scenarios. But for the most part, we do expect most, the majority of scenarios to switch over to V2 without noticing any changes or impacts.

So again, I’ll talk about those two big major changes. Those are the multi-select field types and events with objects created from a template with calculated custom fields. And I’ll go over those in detail in just a second, so don’t worry too much yet. And then just to reiterate, only scenarios that start with these three modules are affected by this change. There are other watch type modules that are not powered by event subscriptions. So it’s really just these three module types and the work front planning watch events are already on V2 and you do not have to migrate. So just wanna make sure that we’re all on the same page there. So let’s go over those two general changes and I called them major changes. They are, I would say more major than the rest of the list that we have, but still fairly small and I’ll show you what I mean. So this one, the multi-select field types, let’s go to work front really quick and I will tell you what I mean by multi-select field types. So if you’re on an object and you have a custom form related to that object, if that custom form has a multi-select field or a checkbox field, that’s what we’re talking about when we talk about the multi-select values changing. So in event subscriptions V1, if you were to only choose one of these multi-select choice values, the experience that you’ll see in Fusion and the watch event side is that that field comes through as a single string value. But if you are to choose two of those options, the value would come through as an array. So this is how V1 operates today. And then when we move over to V2, it’s very similar except for that one single select field. If you’re only selecting one choice, it’s gonna come through as an array as well. So I know this is a little bit detailed technically, but I’ll show you where this actually matters in your scenarios.

So if you have a watch events module that’s watching for those objects that have that multi-select custom field value on them, and later in the scenario or in a filter in the scenario or something like that, you’re using that string value for that single select as a value for another module or like I said, a filter, that will potentially break in your scenario. So you’ll need to go through and update it to use that first value of the array instead.

So that’s the multi-select fields. The second change that I wanna talk about is the creation for new objects with calculated fields.

So when we’re talking about that, if we have a custom form, let’s go into this example, that has a calculated custom field, so only this field type, in our example, we have this calculated field example. And then we create a project from a template that includes that calculated custom fields and the form with it. If we create that object, go through the creation process, this is the scenario that we’re talking about, only this exact use case. Once that project is created or the object with the custom form attached, sorry, in event subscriptions V1, you would get that create event with the calculated custom field and an update with the calculated custom field in the new state and it wouldn’t exist in the old state. So you can see how this is another one of those bugs that I mentioned. We don’t really have an update here, we only have a create. So in version two, we are only emitting that create event. And that’s important if you are relying on an update only subscription, and then either in the subscription itself in the Workfront Watch module itself, or later in the scenario, you’re filtering by that custom calculated fields and only if it has changed or you’re using the new value on an update. But if you only care about creates, if you don’t have an update only scenario that is relying on when you create an object from a template for this to trigger, then you don’t have to worry about it.

So those are the two major changes that I wanted to go through. And as you can see, they’re still not that major. And the rest of the scenarios that we didn’t cover, the rest of the use cases are even smaller than that. So definitely we want you to take a look at your scenarios and upgrade them ahead of time to make sure that they’re still running. But for the most part, like I said, we don’t expect there to be very much disruption in the scenarios that you have. So I’m gonna pass it over now. I’m gonna stop sharing and pass it over to Brooke to walk you through what an upgrade looks like.

Okay, awesome. Let me share my screen.

Okay, so, sorry, let me see if I can go back. Okay, so how to upgrade. So like Erika mentioned earlier, every new subscription or every new scenario that you create with a watch module is created as a V2 subscription.

So that’s important to remember.

And when you’re testing your scenarios or when you’re upgrading your scenarios, we want you to be able to test that it will work. And that’s why you should definitely upgrade before that January date. There’s a couple of ways you can test your current scenarios with an upgrade. You can create a duplicate scenario with a new watch event module, which again will be automatically created with V2. That way you can watch as events come through that scenario and make sure that it is exhibiting the same exact behavior as you expect before you use the upgrade module. And then if you don’t want to duplicate the scenario and do those manual checks, you can just use the new upgrade module, which I will go over how to do as well. And I did want to just point out this important note here. When you do upgrade your watch modules or your event subscription, you will receive duplicate events for every single event delivery for a five minute window. So this includes any event you’ll receive a V1 event as well as a V2 event. And this is to ensure that you’re not missing any events as they’re on different infrastructure, but it also gives you the ability to, if V2 events are not working, you’re still receiving your V1 events and your scenario should function on those properly.

Okay, so let me, before I go through the roadmap, walk through a quick demo of how that will work. So I have a watch module here. It’s very basic, but I’ve subscribed to, hopefully this will load. I’ve subscribed to project events with a multi-select field on update records. It’s very basic. I don’t have any other modules attached, but I have this watch module already.

And I went through a couple of events last night just so that these would be prepared and ready and you wouldn’t have to wait for those events to process on the scenario. But again, this was when my subscription was V1 and I’m demoing multi-select fields because this is gonna be one of the bigger changes as Eric had discussed.

But I have, on this event, I had a multi-select field that was custom and it only had a single choice, choice three. And you can see it did come through as a string.

And then, oh, let me go back to that, so sorry.

This one here. And then this one, I updated it to include two choices and you can see in that case, it does come through as two. So this is the previous behavior on V1. And before I move on, there has been a couple of questions about how you know your watch module is on the new version. So there’s two fields down here that are important. Subscription version, which is what your watch module event subscription is on. So you can see at the time this event came through, my watch module was V1. And the event I received was a V1 event.

Okay, so back to the history. After those events came through, I did upgrade my watch module and I’m actually gonna show you that right now before I show you what happens afterwards. So here’s the watch or the upgrade module.

If you click into it, and this actually just changed today a little bit. So I don’t know if any of you have had the opportunity to upgrade module, but it changed a little bit today. So I’m gonna walk through those as well. First, you have your connection here. So this is the same connection that my event subscription watch module is connected to. In this dropdown, I’m gonna select V2. And then this target is what the change was today. You can either select all subscriptions, which is related to all subscriptions in this connection, or you can select specific subscriptions. If you don’t want to upgrade all of your subscriptions at once. So let’s say I only want to upgrade a specific subscription. I’m gonna click add item here, and I’m gonna type in my subscription ID here and add that. If you don’t know where to get your subscription ID, let me actually show you that really quick as well.

Let’s look at a previous event I had and go back to the event payload.

That I showed before, hopefully it loads. Let’s try that again. Okay, so you can see that your subscription ID is right here. So let’s say this is the only scenario you wanna test. You can copy that subscription ID here and then go back to your upgrade module.

And I wanna do specific subscription and I only wanna do this one and I’ll add it. And then I hit okay, and then I’ll just hit run once.

And that will show me that for that specific subscription, this ID here, it was updated to V2.

So let me go back to the actual watch module and I’ll show you what the events looked like after I upgraded it yesterday. Okay, so here’s the first event I received from upgrade and again, I was changing the multi-select fields, but important to note down here, again, subscription version, you can see now my subscription or my watch module is on V2, but the event version for this I received is V1 and that’s due to that five minute overlap. So again, this will guarantee that you’re not gonna lose events during the switch over and if V2 doesn’t seem to be working, you’re still processing your V1 events. But let’s go ahead and expand the new state. You can see it still came through as a single string because I had a single option and that’s expected because that’s the V1 event.

Going back to the history, I’ll show you my duplicate event.

So this was from a single change in the project. So let me actually show you that too. So that’s where I went here. Here’s my event subscription. This is me selecting a single choice and then this was me selecting two choices.

The events I’m showing you now are me selecting one choice and saving that change. So it really is only one action in the UI, but it resulted in the duplicate events for that five minute window. So again, my subscription is still V2, but you can see this duplicate event is V2. And even though it’s one choice in the multi-select, it did come through as an array.

Okay, so then I went through another action in the UI where I selected two choices and I saved that. And let me show you the duplicate events for that. So that would be these two here. So this is the first one.

And again, we’ll look at the two bottom fields so we can verify subscription version and event version. So again, we’re still on V2 for our subscription. This event that came through first as a V2 version, you can see it is an array. With the two traces I selected, and then going back to the history, let’s look at the duplicate event for that V2 subscription, but this is the V1 version of that event. And then the new state will show an array with the two choices because in V1, if it’s more than one choice, it’s an array.

So that’s going through that. And again, for the five minute window, there was another event that happened this morning and well outside of that five minute window, but I didn’t get a duplicate event. I only received the single event. So that’s how you will upgrade using your watch modules. Let’s say you’re a customer that does use that webhooks module. That’s one that would look something like this.

I have a webhooks module, but I manually went to the event subscriptions API directly to create the subscription.

I’m not gonna spend a whole lot of time because I don’t think there are as many of these as the watch module, but how you would upgrade that is going directly to our event subs API. You can upgrade a single subscription this way.

Here’s my subscription ID slash version. I can specify here that I wanna do it as a V2 and I’ll send that.

And send that and it comes back telling me that it was upgraded to V2.

There are ways to do like in the watch module, how you can upgrade all of your subscriptions.

You can do that directly through the API as well. You can send over a list of subscriptions similar to how you can add items or if you wanna do all subscriptions for your customer, you can send a body like this. And again, this is in our public documentation. If you wanna visit that, I won’t demo that too much because most of this will be through the watch module.

But so that’s how you’ll upgrade your watch modules going forward. And then on the roadmap again, I just showed what was released today, the ability to change only a single subscription from a fusion upgrade module or a list of subscriptions that isn’t just all subscriptions for that connection.

Coming June 12th, during that monthly release, event subscriptions will add the contains only filter. One of the things that has come up during these upgrade, a lot of questions we’ve had is related to those multi-select fields where you wanna know, you want your subscription set up to know if the array only has a very specific choice and event subscriptions doesn’t have a contains only functionality now, but coming June 12th, we’ll have that available so you don’t have to do any intermediate filtering between your modules. And then coming the second half of this year, the filter right now only gives you the option to select an and filter for your watch modules, but they will support the or filter as well. So you can select or when you’re setting up your subscription in your watch module.

So next steps, again, review the documentation that Erika went over and that I showed as well. There’s the full table of complete changes that are object specific, but the biggest changes that we talked about were the multi-select and the create and update events. So definitely review that table and so that you are well aware of all the changes and that you keep an eye on those dates as well. Test your event subscriptions with V2, whether you just upgrade it directly and watch during that five minute window that everything works expected or duplicate your scenarios with V2 and test that they work. Once you’ve done that, make sure you do run the upgrade module though, to upgrade your old one or delete your old scenario and just rely on the new one. And then again, upgrade all scenarios before that January 15th date. If you don’t, we will automatically upgrade them for you on January 15th, but doing the upgrade beforehand gives you more control over your testing and making sure everything’s running as expected.

So that is all I have.

If I don’t know if Erika, you were gonna take over or Nicole from here.

I think we can launch into our Q&A section now. Sounds great. Sounds great.

Yes, I’m trying to dig through and try and figure out which questions have and haven’t been answered in the chat here.

And so I know Erika and Brooke, you guys have kind of gone through some of these questions so far. I’m just gonna ask a few of these aloud and that way we can try and address as many as possible over the next 30 minutes or so.

I think people are still inquiring or have questions on the five minute window of duplicate events. If maybe we can expand on that.

I think it’s a concern where people are. So if you guys can maybe just share a little bit more information, if you have any more information, I think that would be super helpful.

Do you wanna do it Erika? You want me to? No, go ahead. Okay.

So between V1 and V2, without getting too technical, the source of those events differs. And so while you’re on the V1, you’re at a certain point in your events or where we’re receiving events and sending them to you, but the source of our V2 events are different. And so we could be at a different place and you might miss events between the switch, which is why we have the five minute window. I think you are not concerned about that and more concerned about how many times your scenario will trigger and duplicate your triggers for that five minute window. I think Erika talked about filtering after the watch module on that event version field. If you only wanna filter say for your V2 events, and if it’s not V2, then don’t process through the rest of the modules. Did you wanna add anything to that Erika? No, I think that’s great. So really the options are, if you duplicate your scenario, like Brooke mentioned, then you won’t get those duplicate events. And if you use the upgrade module, you will get duplicate events. You can also filter out the old version if you prefer to do it that way. But essentially we’re always gonna send those duplicates to make sure that you don’t miss any messages.

Yeah.

Okay, thanks Brooke. I think that hopefully that helped clarify some of the confusion for folks here on the call. There’s some a question, or actually there’s been a couple of questions around reverting back to V1 if you experienced any issues. Is that possible? And could you guys just speak to that? Yeah, actually let me share my screen again.

Oh, wrong screen. Sorry about that. Okay, so coming back to the upgrade module, here’s the upgrade module.

If you notice you’re having issues, come to your upgrade module here. And in this dropdown, you can select V1. And then if you wanna do your all subscriptions again related to that connection or the specific subscriptions that you upgraded before, add them here.

And I don’t think I still, I do have that subscription still copied.

And okay, and then I’ll run this once.

You’ll see that now for that subscription ID, it was downgraded to V1. So if you do experience issues after upgrading it, you can roll back using the exact same module. But I do wanna just preface to that January 15th date, you will not be able to downgrade. So that is also an important reason to test this before that date, because you will have the ability to downgrade and address any issues you found during your upgrade.

Okay, and so for the folks who are going to be upgrading over the next several months, one of the questions was around best practices around updating during off hours to prevent that five minute window or limiting the amount of duplicate actions. And so is that something that you would encourage folks to do or are you like, no, actually do it during a window so that you can compare V1 and V2? Yeah, I would say it’s dependent on what your biggest concern is. If you do it during the off hours, you’re gonna 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. Maybe during off hours, but create like a test instance for your common use case or like a test event, right? For my use case, it was updating the multi-select field on that project. Whatever your watch module is built around, do it during off hours maybe, and just run a test so that you can see both events come through and that it behaves as you expected.

Okay, great.

So we have a one customer who said, if the event module already shows as V2, do we need to take any action? Because I see very few scenarios as V1. My understanding is no, but I will let you guys confirm.

Yeah, if it’s already V2, you do not need to take any action.

And correct me if I’m wrong, but I believe when I was reading through the documentation, I think it was like after like April 23rd, 25th. Yeah, April 10th maybe. April 10th, okay. It was the beginning of April, but it is in the public documents.

So, okay. Another question is around upgrade, sort of bulk updating all subscriptions at one. Is there anything that customers should take into consideration or they should look for other than maybe failed scenarios? Are there any risks of upgrading everything altogether? That I again would say, I think 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. So I would say failed scenarios is probably the best way to tell that there is an issue.

Yeah.

All right, let me, I think I have two more questions and then I will maybe open it up to folks to just raise their hand. Is the only way 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? In Fusion, I think 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. Yeah. But like Brooke mentioned, our public API does have an endpoint that you can list all subscriptions at the same time and that would tell you which ones are on V1 still.

Yeah.

Okay. Is there any way to run a report to easily determine which scenarios have V1 and which are on V2? Is there any way to do that? 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.

Okay. It actually looks like someone maybe posted something in here in the chat. And again, I’m no expert on Fusion and event subscriptions, but something around Postman, you can use the admin API in Fusion, generate an API key.

So you might want to tap into some of the expertise that folks in the chat here.

I think I feel like I’ve answered a lot of the questions that came in the chat that maybe went unanswered as these guys were talking. Does anyone have a question that they want to raise their hand and ask aloud or something that I may have missed? I posted a quick question and this, again, might be slightly off topic, but is it the only way to view and manage event subscriptions? Is that only done through the Workfront API or is there a place in Workfront where we can view those? That’s a good question. And unfortunately the answer is it is only via the API at this time. Okay. Thank you.

Anyone else have any questions for Erica and Brooke? I just want to say, Oh, go ahead.

And this was very helpful information at least on my side, it’s resolved a lot of the angst, I think, so we can communicate this to our clients in a better way. So appreciate you guys putting this together for us.

Of course. Thanks for joining, Stephen.

A couple of questions came in the chat here and I will read these aloud. Do we need to make any changes to our existing Fusion web scenarios to ensure compatibility with the event subscriptions V2 upgrade? Yeah. So just in the public documentation that we kind of walked through before, there are some of those edge cases where if you’re relying on the bugs that existed in V1 in those changes, then you will need to make changes. Like we said, most probably don’t. And if your workflow is not majorly critical, you can always just upgrade it and see if the Fusion scenario fails, resolve it and then replay those events. So it’s not, yeah. Like if you have a very critical workflow that you need to trigger right away, then we would recommend really digging into that documentation and making sure the Fusion scenario isn’t reliant on one of those bugs.

Okay. I think we’ve answered this one. Is there a way to identify which version you have to, okay, again, not technically, you have to click and open each Fusion scenario and review it. Yeah. Yeah. So you’re just, yeah.

Go ahead. Yeah. So you can either click into your Fusion scenario into a historical run and see the version that is in the payload, or again, you can use the event subscriptions API to list all of your subscriptions and see the version from there.

Okay. Thanks for clarifying.

Will maximum number of returned events equal one in watch events run with immediately run option in V2? I believe so. I don’t think that is unchanged. That’s Fusion specific functionality. And the biggest change is what we are delivering to Fusion. So that should be unchanged and should still work as expected.

Okay. Yeah. Fabulous. I’m going to just share a couple of slides here and then we can always hang on the line for a few extra minutes in case anyone has any last minute questions, but I just want to highlight a couple of things that are happening.

You guys see my screen? Yes. Yes. Is it in full screen mode or is it in like? No. No. Okay. Let me try and stop. Or maybe if I just do from beginning. Oh goodness. Okay. Let’s try this again.

Okay. Fabulous. I have like three or four quick slides.

And then… Okay. Workfront user groups. If you guys are not familiar with the user group program, these are localized chapters where you can connect and network with peers in your area. There’s been a handful of new cities being launched. These are not published to the events page on Experiencing just yet. There is a separate page. And so, like I said, you guys will get a copy of this slide deck. We can always include this link in the follow-up email as well, but I just wanted to highlight that this is an opportunity for you to connect with some of your Workfront peers across the US, depending on where you’re located. The Champion program for Workfront launched this year. Applications opened May 8th. They will be closing June 10th. If you are an experienced Workfront admin who is interested in sort of being a voice and advocate, a champion for the Workfront solution, we would love to have you submit an application.

There is a webinar tomorrow. If you are interested in learning more, that webinar is posted to Experiencing on the events page. So if you’re able to register to just get some more information, this will be a great opportunity for you to have a voice, like I said, within the Workfront world. This was a slide that came from our marketing folks. There’s some Gartner peer insights that they’re looking for. If you are interested in filling out a survey under the marketing work management bucket or the collaborative work management bucket, which is basically a non-marketing use case, you’ll have the option to receive a $25 gift card when your review is published. And so you’re always more than welcome to scan the QR code now, or like I said, this will be as part of the slide deck in your followup email.

And then last but not least is just upcoming events for Workfront system admins. There’s a handful of things happening throughout the month and into early June. Like I said, there’s the Champion program. There’s some folks from DSW and Western Governance talk about how they’re managing resources in Workfront. There’s a session of Workfront planning with product. There’s one with on data connect with the product team.

There’s some admin chats, which are sort of open office hour sessions. And so that’s all I have for everyone from sort of a end of event housekeeping wrap up. But like I said, we’re happy to stay on the call. Should you guys have any followup questions for Erica and Brock? Otherwise you’re more than welcome to jump. Although I did believe Cynthia, she put a link to a survey in the chat. If you guys can just fill that out, it’s totally anonymous. It’ll take you maybe one minute just to get some feedback on today’s session, what you liked, what you didn’t like, and I’ll be sharing everything back with Brock and Erica. Like I said, it’s totally anonymous. So honesty is truly appreciated there. Like I said, 15 minutes. If you guys want to drop, have 15 minutes back in your day. Thank you so much for joining us. If you have more questions for the folks here, we are happy to stay for the next few minutes. So I will just stop talking. And if anyone has any questions, feel free to just raise your hand and come off mute.

It does look like someone did post another question in the Q&A that maybe we could just talk about real quick.

Demoing how to filter the scenario version. So not seeing the field as adoption to filter against, or is, yeah, I do see it when I view scenario history. I actually haven’t tried that. Erica, have you tried that filtering the event version? Yeah, and here, I guess let me open. I do have one open.

Hopefully my session is still good. And I’ll show this really quick. Sorry. No, no, you’re good. Okay. All right, so if you have, sorry, let’s go back to the diagram.

All right, so let’s say you have the Workfront Watch Events module. What I’m talking about is the Fusion filter functionality here where you would take in the event payload, you have the event version.

And if that is equal to V2 or V1, that’s what I’m talking about when I’m talking about filtering. And only the version that you want goes through to the next module.

Yeah, Ross.

Yeah, I don’t see that option.

And I’m on the Watch Event.

Like a previous one.

On the Watch Events module, you’re saying you don’t see the, in the history. I see it in the history, but when I add a filter into the scenario, and I go to set up the filter and add the condition, I only see event type, subscription ID, new state, old state, and then event time.

Okay.

That, if you run, if it hasn’t run in the last, I guess it would probably be in the last month. So if your scenario has run in the last month and you’re still not seeing that as an option, I would say you can reach out to support and we’ll figure out what’s going on with your instance. But yeah, you should be able to see that in the event payload if it’s run recently. Yeah, this is a very active scenario. Yeah, okay. Yeah, please reach out to support and we can dive deeper into your specific instance and why that’s not showing up. Okay, thank you. Thanks.

Looks like there’s another hand. I’m gonna say your name wrong and you’ve been very active in the chat. Do you wanna? Don’t worry, don’t worry, yeah. Thanks. So could we please clarify what exactly the option all subscriptions means in the new module? I tested this back and forth and I came to the conclusion that the connection I choose in the module defines a work front instance and all subscriptions of that instance will be affected or impacted, is that correct? That’s right. All of the modules that are associated with that same connection will be upgraded. You’re exactly right.

I’m sorry to be picky on this, but I think what you said slightly means different what I said, because I found that the connection defines the work front instance and all subscriptions of that instance are updated even if they don’t belong to the same connection. So assume another team within Fusion creates another connection to the same instance.

The subscription of that team are also impacted. You’re right. That’s right. That’s a good clarification because you can have multiple connections for the same work front instance and it is across the entire work front instance. All of the subscriptions for that work front instance will be upgraded. Okay, clear. Thank you. Just wanted to know because it means potentially we need to inform the other teams within Fusion but changes I make impact them as well.

Right. That’s true. Or when you’re using the upgrade module if you don’t want to upgrade all for that connection or that work front instance, you do have the ability to specify individual subscriptions. So if you know the exact scenarios you want you can only update those ones. But I know that that can be a lot if you have a lot of scenarios. I don’t have that money. Okay. I’m really happy about that by the way.

Yeah. And I appreciate that feedback came from the community post and the Fusion team added it because of that post. So thanks for that. My post. Yeah, I know. Thank you. Thank you guys.

Thank you.

Thank you. There was another question in the chat. So is there a documentation available that outlines the key differences and improvements in version two? And since we have many Fusion scenarios is there a method to identify which ones are impacted or to reproduce any of the changes or bugs being addressed? We did point out the documentation. I’ll post it here again in the chat the link to the changes in version two.

And again, we definitely went over the two biggest global changes but there are object specific ones that we did not go over. So definitely make sure you review those tables there to see the changes.

And then method to identify which ones are impacted.

I think it was asked before there’s not a report or anything we can run that will tell you which ones are impacted but any of your Fusion scenarios that begin with. So if you have the watch module or the web hooks module that uses event subscriptions those are the ones that you would need to address. And again, either using the upgrade module for your watch modules or duplicating your scenarios and testing.

And it looks like there’s one more question from Rose Maria. If you can, if we can help check which version the web hook is on. And I would say, like Brooke mentioned you can see it in the payload that comes back from the web hook. And if you need additional help, obviously we can always open a ticket and help you identify that through our support team.

Yep, and then there’s another one in the Q and A. So how to check the version in a custom web hook module. It doesn’t show that in the history.

So they might not be surfacing the event version or the subscription version in the custom web hooks module. If that’s the case, I hope you’re a little familiar with the event subscriptions API. That’s how the subscription needed to be set up but you can again hit the event subscriptions API directly to get all of your subscription details including your subscription version. That is also in our public documentation as well. The exact end points you need to list your subscriptions. And we’ll double check the web hook module should show this in the history. It should show it on the event itself because we’re sending it from event subscriptions directly. We’ll double check and make sure there’s not a bug there. And then if you’re still seeing it now, again, I would recommend reaching out to our support team because you really should be able to see it in execution history if it’s executed recently.

Yeah, agreed.

Thanks for clarifying ladies.

Honestly, I think you guys did a fabulous job. You guys have answered so many. I put you on the spot here and made you answer questions aloud and live which is always the hardest part of any session. And so I’m sure the folks on the call here really appreciated your expertise, your demos to kind of walking everyone through some recommendations and best practices. So I just want to wrap up. We’ll give everyone seven minutes back in their day but really just thank you so much to Erica and Brooke for hopping on and kind of giving a little bit more inside scoop to what’s happening with event subscriptions B2. So Erica and Brooke, I don’t know if you have any last words but otherwise thank you. Thank you everybody. This was great. Yeah. Yeah, thank you guys. Thank you guys. Yeah.

Awesome. You guys will get a follow-up email shortly after. And so keep an eye out for that. And should anything else come up feel free to reach out to us or customer support and we’ll get you taken care of. So have a great rest of your day guys. We’ll see you soon. Bye.