Adobe Workfront First Quarter 2026 Release Webinar

Transcript

All right, welcome everyone. I’m going to go ahead and get us started. Welcome to the Adobe Workfront first quarter release webinar. We’re going to be going over many of the features that are going to be released next week. We’ll talk about timing and all that in just a second, but let’s talk through a few housekeeping things. One, this session is being recorded as you just heard. We actually recorded it in two places just in case. So keep an eye out for an email later today. It’ll probably be afternoon my time. Once we get notes and the recording and the deck, we’ll send all of that to you so you have all this goodness to reference as you’re getting ready for the release. Do you mind resharing Leslie? I’m sorry. Oh, thank you. It’s just because of the recording. No worries. Yeah.

Thank you, thank you. So we’ll…

All right, so let’s talk about the agenda today. We’re going to do some welcome and introductions. Go through the release. We’ll do a review of today. We’ll try and save some time for Q&A, but if we don’t get to it, we’ll make sure we export that Q&A and try and address those. And then we’ll wrap up.

So these are our speakers today. We do have them on.

I’m going to jump in. I’m not going to read this list because you’re going to get to know them along the way.

A couple of things I want to call out. Again, you’re going to get a copy of the slides in the follow-up email later today. So you’ll have access to all these cool things. So we do call out the section of the release notes. So you know kind of where this fits in when you’re looking at that release page. This will jump you right to where it is. This links you to the exact item.

We do flag if it’s part of workflow, planning, automation, so that you know kind of what we’re talking about. You can keep track there. And then if there are any requirements, we do try and link them here so you know, if you want to use this feature, are you going to have access? Do you need to work with another sysadmin, something like that? You have all that information there.

let’s jump into workflow.

I have Jonah here, Jonah. Hello, hello. Hello, are you ready? Yep, sounds good. Thank you. All right, most of my stuff is really straightforward and we have a lot, so I’ll be quick. First off, managing priorities and layout templates. So previously, if you’re a priorities customer, this was just a toggle and system setup. Now it’s been moved to layout templates to be more consistent with the rest of the products that we offer. If you had it on before this change, it will continue to stay on for you. If you had it off, it will be off. So no need to worry about changing or editing anything. It should just work seamlessly when you make this change. But moving forward, if you need to add new users to priorities, you’ll do it through layout templates.

And next.

All right, custom form conflicts. So when you’re managing big massive custom forms, we’ve added a little dialogue that’ll check for conflicts in it and let you know what might be affected before you save any of the changes.

You can see that little dialogue over there on the right.

And hopefully this will just save you from causing any issues before you save. So check it out and next.

All right, some more custom data stuff. So now you’re able to see who has created a custom object and when they created it. You’ll be able to see it in views, reports, et cetera. Note that if these custom objects were created prior to November 13th, 2025, that it will not populate. So all of your old stuff, you’re not gonna see it, but anything moving forward, you will be able to see that information. I see a lot of people like that one. And next.

Okay, another quick one. Updates to the dialogue when you’re saving layout templates. So prior to these changes, you just had save and cancel. Now we have apply so that you can apply those changes and then keep moving forward. Helps a lot when you’re making a bunch of changes to a layout template and you don’t wanna lose them. And this is also just more consistent with our product. And next.

All right, some field management stuff.

We know customers can have upwards of several thousand fields within their system. You’re now able to mark fields as active or inactive. And by doing so, if it’s inactive, they will be excluded from reports and like the field library and whatnot. So feel free to play around with it and hopefully clean up your system.

All right, this should be my last one. So we made a quick update to the mentions widget in home. We’ve gotten a lot of feedback that there was a ton of chatter and unnecessary information around assignments and whatnot there. So it’s been trimmed down to only include comments made by the user or when they’re actually mentioned. Hence, we call it the mention widget and it included a lot more that was inaccurate. So that has been changed. And the look and feel is also a lot more aligned with the rest of the updates area across Workfront.

And that should be it. Yeah, thank you, Jonah.

Feel free to drop questions in the Q&A pod and Jonah, hopefully you can kind of keep an eye over there and help answer anything we’ve got, but those were great updates. Thank you.

Jeff, are you ready? I am, thanks Leslie. And thanks Jonah for those previous updates there. And hello everyone. We’ve got several updates here within the content section. I think you’ll find they’re pretty meaningful and impactful as well. And so the first to discuss here, or actually the first couple, will be related to our Adobe Express Workfront proof integration. And so one of the things that we’ve been able to add here over this past quarter is now when you have a creative going to submit an asset for review through Workfront, they’ll actually be able to attach that review to an existing project. So there’s a project selector field here that they can use to go ahead and search and find an existing project to attach that asset review to. So for those that are starting to take advantage of this integration, that’s going to be a new capability that’s available here with our first release of the year. We can keep moving, Leslie, and we’ll highlight the next. Yeah, no problem. The next enhancement that’s once again specific to the Adobe Express Workfront integration. And to this point, if you had your Express product as well as your Workfront product in different IMS orgs, unfortunately, you weren’t able to connect and use the integration. But moving forward, we’ve basically introduced cross-org or cross-IMS org functionality to enable this integration. So if you do have those products housed in different admin consoles to say, you’ll be able to go ahead and now take advantage of the integration. So once again, a very meaningful impactful enhancement there for our users on this integration.

We can move to the next slide there. Great.

So speaking of another integration, this is specific to our Workfront and AEM native integration. We have what we call the asset selector component, which is a portal into AEM that Workfront users can use today to go ahead and navigate folders, to link folders, as well as assets into Workfront. What we’ve done is been able to actually introduce another object here, specifically collections, into that component. And so users now not only will be able to attach and navigate through folders, but they can navigate and attach collections as well into a Workfront object.

So once again, another great enhancement there as it relates to that integration. And then last but not least, as far as this section is concerned, for those that are participating as beta customers with the AI reviewer functionality, you’ll be very much aware and instructed that, hey, to go ahead and set up configurations as well as details that enhance the AI reviewer model around review appropriate to your brand. You’ve had to do that through Adobe or Gen Studio Foundation to this point. But one of the things we’ve done is we’ve actually brought in, for admin specifically, within the Setup menu, the ability now to go ahead and configure to make edits to those brand settings directly inside of Workfront. And you’ll find those under the Review and Approval section within the Setup menu. So for those, once again, participating in that beta, you’ll see that go live with the release that we’re highlighting here in our webinar.

And that’s it. I think Matt’s up with the next section there. Awesome, thank you, Jeff.

Hey, everybody. Hey, Matt. Let’s get into it, Leslie. All right, love it. OK, this first one is more of a public service announcement. Most of you will have nothing that you’ll need to do. But over the last couple of months, we detected an issue where organizations that were using the other groups IDs, role IDs, or team IDs and doing an evaluation with a null operator, is null or not null, were getting mixed results in their filters for users that would fit that criteria.

We’ve always had two ways to access that same type of information. One is by traversing through the other groups ID, or other groups colon ID, roles colon ID, and so on. Our recommendation is that all customers pivot to use the other roles ID, or the other groups colon ID approach, the roles ID colon approach.

And to facilitate that, we’ve removed the option to choose these problematic shortcuts inside of the field and then remove the option to use the other roles when defining a filter.

The functionality, if you were not using a null operator, will continue to work. It’s supported in text mode.

But we just wanted to make it so that you were less likely to run into that situation by only promoting the items, the paths that do work. Why don’t we move on to the next topic? I’ll just mention on that one. There were only 600 or so reports across the entire customer base that had that condition. And half of those were our support team, probably trying to troubleshoot that type of issue. And so it’s a very small footprint of people who will need to make an adjustment there.

Moving on to more of a Canvas dashboards feature, one of the things that we have introduced is the ability for you to quickly toggle between the currencies that are displayed. This applies primarily to customers that have multiple currencies configured in their exchange rates portion of the setup area and will allow you to quickly toggle between the currencies that you have defined. This is especially helpful for those international organizations where a report might be defined in US dollars, but the primary viewer of that report is in Europe.

And so they will be able to switch to the European euro and be able to visualize that data. That is a sticky preference. It’ll be remembered for that user once they’ve selected it. They can always revert back to the default and know what the default view is supposed to be. There’s also a handful of other enhancements inside of this capability where if it’s an important report that should not be toggled off of the defined currency at the report level, whether it’s a KPI or if it is a chart or even specific columns inside of tables, you can elect to opt out of the currency toggle. So those will be locked into the currency as defined on the report.

Let’s move on. Yeah. We’ve also introduced a back by we had a lot of feedback on this one. This was the number one feedback item when we launched the open beta of Canvas dashboards is for us to have a duplicate report. And so we’ve introduced that. I don’t know that there’s a whole lot more to say about it. It’s pretty straightforward. Just use that action menu and you can duplicate the report.

We’ve also introduced a quick search capability on tables. This includes a table report inside of Canvas dashboard as well as a drill down for any of the segments of a chart. And so one of the enhancements over previous iterations of a similar feature for the classic reporting is that this quick search, this quick filter searches all pages of the report. And so it’s not just searching the content on the first page that’s loaded. It’s searching the entire universe of results for that particular report.

Let’s keep going. Yeah. We’ve also introduced a handful of charting options. We’ll start with some of the pie chart options. The first one is for us to show a total.

And what this really allows us to do is represent the data as a donut. We give you the ability to change the label that shows up in the center.

And there’s a handful of other pie chart preferences. Let’s move on to the next slide. I think there’s another one here. The other thing that we’ll allow you to do is to hide the segment labels on the chart itself and represent those as a legend. This is especially important when you have series that are defined with names that are extra long and force the report to shrink down to become nearly illegible so that we can make space for those segment labels. So one thing that I do want to mention on this one is we’re giving you a lot of tools to represent the data in the most meaningful way. In some cases where there’s a lot of segments to be displayed, this legend option may not be the best approach. And so be aware of the data that is being represented in the chart and how you want to present that. And choose the right options, toggling on and off these different things, like using the legend, the placement of the legend, as well as whether or not you’re going to show or hide the segment labels.

I also mentioned on that legend piece, we are adding the legend option also applies to multi-series and stacked column charts. And so just be aware of that as well. Let’s go. Yeah, we’re also introducing the new reference line. This is a pretty rudimentary first version of the reference line. I think that there’s more that we can do with it. It’s static, essentially. You’ll come in and you’ll identify a threshold or a target that is meaningful for the data set that’s being represented.

And you can establish a reference line. We do provide a couple of options around whether or not it’s dashed or solid line. And there’s a handful of other options for the line types. Like it can’t be represented as a percentage of a piece of data or dynamically set. But I think that there’s opportunities for us to grow into those types of dynamic representations of a reference line in the future.

We’re also allowing you to customize the axis labels as they’re represented on the chart. The primary use case for this is, you’ll notice on the bottom axis of my example chart, it says entry date month, which is fine. The way that this would normally be represented is we would provide the full path of how you got to the entry date. And in some cases, that’s very helpful for us to know that you went through, you’re coming from the task object to the project object and you’re showing the project’s entry date. In some cases, that’s just noise and it gets very long very quickly. And in addition, on my y-axis in this example report, I want to just show request count. I don’t want to show requests.name.count because that doesn’t really convey to the consumer of the report what they’re supposed to be taking away from that. And so we wanted to provide a path for you to set those labels on your own.

We’ve also made some improvements around how we represent groupings. And in this case, one of the existing conditions within classic reporting, and it also persisted inside of Canvas Dashboards reports, is that the grouping totals only reflect the items on the page. And so within Canvas Dashboards, we have the flexibility now to be able to represent those numbers as a number of the full set of records that represent that. So you can see in that bottom example for the product group vector, there’s 66 of a total of 196 items that we’re now currently displaying, but you know that there’s more items on subsequent pages.

We’ve also introduced a handful of guardrails around Canvas Dashboards. We’ve seen people starting to utilize it and where we’re starting to hit performance issues. We felt that it was important for us to start adding some guardrails when we released the open beta. We kind of just let it be the wild, wild west without any guardrails, but we found that there are some certain conditions. This is just one example of a guardrail. This is just one example that’s in the screenshot here around the number of reports per dashboard.

25 is the limit that we set that’s consistent with the classic dashboarding experience.

Those of you that have exceeded that limit already will continue to represent the reports that you’ve added to the dashboard, but you won’t be able to add any additional reports until you get down below the 25 limit.

So the other limits that we’ve added have to do with the total number of groupings on a table view. In classic reporting, there’s a max number of three groupings. We’ve been able to exceed that and still hit our performance targets for loading the reports, and so we’re providing up to five groupings. We have set a limit on the distance that you can traverse as you’re adding fields or groupings or filtering. In classic reporting, the distance is two objects away, two relationships away for filters and four relationships away for columns in a view and groupings. In this case, we are unifying around a limit of 10 for all three of the columns as well as the filtering as well as the grouping, which we’re really pleased to be able to provide more than we are currently providing in classic reporting. There’s also a column limit.

Over 95% of the reports inside of classic reporting have fewer than 25 columns, so we added a limit there. We can explore alterations to that limit, but we wanted to have a limit in there, and we’ll monitor and see if we can exceed that 25 column limit. I know some of you have reports that have dozens or even over 100 columns, and so we do want to be able to accommodate those in the future, but for now we’re at a limit of 25.

And then there is a total number of limit, a total number of dashboard filters that we are allowing, and that is a limit of 10.

That was a lot. Okay. Yeah. Thank you so much, Matt. I know there were some questions in the chat. There might be some in the Q&A pod as well if you want to hop over there. We appreciate you. Thank you, guys. And I think I saw a request. I think Jonah is coming back to help us with request enhancements. No, I’ll cover that lately. Thank you. Hi, everyone. We have a bunch of updates on the new requesting experience.

The first thing is that the created object link, which is basically the converted object alternative in the new experience, you’ll be able to directly click on the object on that column that will navigate you to either the work from planning and not with this release, but we are doing the same thing for the issue request as well. So the converted objects will appear in here with the link, and it will navigate you to the created object slash converted object. And the same experience we have for my request widget. Basically, it’s the same thing in the new requesting experience and my widget.

Next slide, Leslie. Yep. So as you might already know, we have a new view creation mechanism in the new request experience. And in here, we added the sharing option. So as you know, we have system views, which are defined by the system admin through the layout template, and each individual user can create their own views. And now we added the sharing option, so they can create a view and share with the group, company, or specific teams or users, and they can either give these entities view access or manage access.

Yeah, I think that’s it for this slide. And the next one. Yeah, so this is one of the powerful additions to this new view. So now you can add custom fields to your view, to your table view in the new requesting experience. Basically, this will allow you to bring more fields from your request forms, both from planning request form and from the request queues, like legacy request queues from workflow that we have, if you want to see more data on the specific request.

Yeah, I think the next slide.

Yeah, another addition which will make views more usable for system admins, for teams and groups, is the current user wildcard. As you can see, you can now create a view that will use the me logged in user or current user wildcard. So you can basically create a view that you can share with the company, with teams and groups, and each individual users will see their own requests in this view.

And yeah, you can either share with this setting, with this filter, or just as an admin, you can go to the layout templates and you can share the view through the layout templates, basically.

Yeah, that’s it from this slide. Yeah, the next one, maybe some of you are already aware of this feature, but now the form filling powered by AI is available for everyone, but you should have the AI enabled through the setup area in Workfront. So what it does, basically it allows you to type in a prompt. It can be an email thread or a Slack thread or whatever text and attach a document, for example, a campaign brief, and it will automatically fill in the request form for you, where you can later scan through the whole form. You can either accept all the changes done by AI or reject all of them or accept each individual suggestion. And this thing, like this AI powered prompt and document filling, also is available not only for the whole form, but for each section. So you can actually go on and use the AI to populate only a specific section of your request form.

Yep, next one. Yeah, the draft, I think this is one of the highly anticipated ones for the new experience. So drafts are already available in the new requesting experience. Their status is basically a new status that is, I don’t know if you can see or not, but it says draft. This makes it even more powerful. So you can actually combine drafts with different other requests when filtering or later will enable grouping as well. So in this case, basically you’re using it as an ordinary status and it is filterable. And you can also use custom fields to see different, more information on your drafts as well in this view. And if you’re trying to submit a new request through the search or through the recent cards, recently accessed request form cards, you can see at the top it shows all the drafts that you have for this specific form. So you can choose and continue from where you stopped the last time. Yeah, I think that’s it for this slide. And the deletion, yeah, this is pretty straightforward. So now you can for both work from planning requests and for issue requests, you will be able to select one or multiple requests in here directly from this view. There is no need to go inside of each individual request like in the previous, like in the old experience to delete it. You can do the whole thing in here and we respect the permissions, the deletion permissions that the user has that you have set up in the request queue details basically.

And the next one, I think, yeah, this should be the last one. And this is one of the big ones as well. So copy and submit is supported already in the new experience. So you can actually copy one of your submitted requests and you can basically change one or two things in there and submit that new request. So this makes it really quick to submit multiple similar requests.

And yeah, I think this should be it for the requests. I’ll jump into Q&A to see what kind of questions do we have there. Can I just ask one quick question in regards to the request experience? People are asking about a date, a deadline for when the old request will be sunsetted. I feel like this is a hot topic in the chat. So maybe you can just answer that before moving on. Yeah, so right now we don’t have any hard deadlines for the old experience deprecation, but we are working on that and this kind of enhancements on the new experience and the reaction that we’re getting from our customers will kind of guide us to the right direction in terms of when should we sunset the old experience. We’re tracking the adoption there. So after the Q1, we’ll have a better understanding when this date should be for the deprecation for the old experience. I would say my feeling is that in Q2 or Max Q3, we’ll be ready to deprecate the old experience and transition all our customers to the new experience. But we don’t have that hard deadline now. What our customers can do at this point is provide as much feedback as they can on the new experience so we know that basically it works for them and it is much better than what we had before and it’s much powerful than what we had before. This is what we’re looking for at this stage.

Awesome. Thank you, Katch.

Thank you.

Jeremy? All right. Happy New Year, folks. Good to see you. I have two quick ones. The first is for my custom form fans out there. We have increased the ability to, if you’re using check boxes or multi-select dropdown fields, we have increased that limit. I think right now it’s sitting somewhere between 255 selections, if I’m not mistaken.

We upped that to 5,000. Yeah. All right.

So yeah, pretty simple one.

This last one is if you have not migrated to the Adobe Unified experience yet, please do so. We are at 90% of our customers.

This unlocks a couple of different things. One, you’re a little bit more embedded into the Adobe ecosystem. You get the easier access to the AI assistant and it also unlocks zero touch, which is pretty much allowing you to have users click work front links and get access automatically, kind of like in the olden days where you could kind of auto provision a user with very minimal access. So if you haven’t migrated, please let us know. We can get you in touch with our migration specialist, Merit, but we are like at 90% of customers and we want to get the last few over the line. So thanks. That’s it. Awesome. Thanks, Jeremy. Hopefully you can pop over the Q&A pod and answer anything over there.

All right, Sam, I know you have a demo, so I’m going to stop sharing so you can share.

All right. Great. Can you hear me OK? Yeah, thank you. Yeah. If you wouldn’t mind, maybe start with the slide and then we’ll pop over to the demonstration. Sure. Let me grab that.

Sure.

All right. Here we go.

Wonderful. So first thing I want to highlight from work from automation and integration is some recent changes to web hooks. One of the problems that we see pretty consistently is that people or organizations will have a large number of web hooks, but they don’t all have the same priority. There are some web hooks that are really important. They’re part of a user workflow, and we really want those to be able to be prioritized over ones that maybe it’s something that doesn’t need to run very frequently or a minute delay or a few seconds delay wouldn’t matter. So what we’ve done is added in the ability to add priorities, and this would allow you to set high, medium or low priorities on your web hooks, and the high ones will be processed first. Quick note, that’s across all teams, so it’s not restricted to one. It’s an organization wide setting. And now I’ll go ahead and share my screen and I’ll show this new option.

All right. So same place as you’d normally manage web hooks. It’s over here on the left. And then for all the web hooks that you want to highlight, you were able to select low, medium and high and indicate where you want to put those in. What I found is probably the easiest way to do this because, you know, we all start they all start out. Hey, Sam. Oh, yeah. This screen is blank. Can you try maybe sharing one more time? Oh, give me one second. I’m going to share again.

How’s that? Did it pull up? Still, I just see. Oh.

No, still blank.

That’s very strange. I’m going to try one more time to see if there’s.

Maybe we’ll try sharing a window instead and see instead of a screen.

How about that? Any better? Still blank. Someone suggested maybe someone else share. I can try sharing real quick and then try to try again.

And.

Try again, Sam. And then.

Anything kind of moving around the window a little bit. It is all blank, which is so strange. I know you and I have been screen shares before. Yeah. So maybe maybe drop from the meeting and come back quickly and try. Yeah, I will do that real. OK. Thank you.

While we have a second, can I ask another question then from the top? People have asked about sharing feedback on the new request experience. I know in the in the past, Workfront has had sort of dedicated buttons for different areas where feedback is requested is where would where would the new request experience feedback? Where should we recommend customers put that? For now, I would say they can contact their customer support specialists or like we can always share my email so they can directly contact me regarding the feedback. But we’re working on adding a feedback button that will make it much easier to submit their feedback through through the UI of the request page.

Awesome. Thank you. Thanks. And Sam, we can see your screen now. So that was perfect. Thanks for doing that. Wonderful. All this technology and restarting still helps with most of it. I know. Is it.

Exactly. Exactly. Great. Well, where we left off is just highlighting the set of priorities. And you’ll notice that most of mine are set to low because that’s where the default is. When you will log in, they’ll all be set there. And that means they’re all being treated equally. Our intent there is it’ll be a lot easier for you to just say these are my high priorities and select those.

So please feel free to start using that highlight, you know, and you’ll be able to now prioritize your most important fusion scenarios. One other quick thing while we’re here, in case you missed it last year, we did add a button so you can find your the scenarios that are associated with a webhook right from this screen. So neat little connection there. All right. And then you know what, Leslie, just to avoid any possible problems with this.

Why don’t I share my first and we’ll come back to the slide. Yeah. Why don’t I share the next slide and I’ll demo it. Love it. Just because I’ve got that up there. It shouldn’t be a problem at all. All right.

So I wanted to highlight a new capability for navigating within fusion. And as some of you know, once you get over 20, you know, you might even get up to 200 different modules in the scenario. It’s tremendously difficult to search for module by name and to find it. And this is something where there was a tool in the fusion dev tool to do this. But, you know, it was disjointed and really not really the best experience for finding those. So interest in improving that. What we’ve done is added a search and select tool. Now, this can come up from your function tray down at the bottom. That’s that search icon. You can also launch this through the function or control K. So on Windows, of course, control K and function K on the on an Apple machine. And this will bring up a window from here. You can click on a module. Infusion will navigate to that module. You can also search for one. So let’s say I wanted to look for all my expense modules. I can search by that by the module title, but also by the connector and then select it. By the way, you can do all that from a keyboard and it’ll be able to show the module. You navigate to the module and change the parameters. So we’re hoping this improves the experience, makes it a little bit easier for designers, especially when you’re dealing with large number of scenarios.

Let’s see, I’ll go ahead and pass that back to you. Looking to the last slide there.

Right. And then just to highlight a few recent connectors, we recently released the Adobe Substance Connector. So if you’re doing 3D images and assets that you’re working with 3D content, you’ll be able to use that. Just another addition on the content supply chain. Being able to automate and connect that. We also added Adobe InDesign, and so that’ll be available for you if you want to do any InDesign automations. And then not Adobe, but one I think that a lot of us end up using is there’s a Viva Vault Connector. Now you’ll see a beta tag on this. It is available now. We’re just wrapping up some feedback with some early adopters and we’ll be finalizing that later this month. So you expect a full release now. I don’t expect a lot of changes to that. You’ll just probably see a few enhancements. So no problems starting to use that right now. Awesome. I think that’s all and then I’ll check you with it. Perfect. Thank you, Sam.

All right. Now we’ve got Workfront Planning, Lilit.

Hello, thanks, Leslie. And hi, everyone. So I will cover the big enhancements that we are bringing to Workfront Planning. And then there are going to be a number of other enhancements as well. So I would encourage everyone to go and check our release notes for some additional new capabilities. So first off, I would like to start from the global record type. So this is a new concept that we are introducing into Workfront Planning. And this through this capability, it will be possible to define a record type in one primary workspace and then reuse it across multiple team workspaces. So what we have been hearing from our customers is that it’s very difficult to make sure that different teams who operate in their own workspaces, they can operate with the same structure, with the same metadata. It’s difficult for the admins to enforce some standardization across teams. So with this capability, the operations admins can define, let’s say, the campaign’s record type in the enterprise marketing workspace as displayed on the screenshot. And then this same campaign record type can be pulled into the peer media and social workspaces. So from each of these workspaces, the local teams can input their own records, which will be marked with the corresponding workspace. And what is powerful with this concept is that all of these local team workspaces, they will only see their own data, whatever is available to them. But on the primary workspace, all of the workspace members will automatically get access to all the team records. So basically, you will add the leadership to the main workspace and they will automatically unlock this cross-invisibility. They will see all of their campaigns that the teams are doing without necessarily bringing everyone into this one huge giant workspace that will become a nightmare to govern. So this is a pretty advanced capability. And I’d like to highlight that this has some packaging restrictions. So, yeah, just make sure that you check whether this is available for your package or not. So just to clarify, this is not available with the lowest packages.

Another thing that we are introducing into the system are the record level permissions. And this is something that we have been hearing a lot from across the board, right, from all of our customers we’ve been talking to. And with this capability, you will be able to control access to individual records. So right now, if you add someone as a contributor to your workspace, they get to edit or delete any record, which we know is not desirable. So with record permissions, you can just select the campaign that you want to make the only and limited to all of the contributors as the only access. Or you can even hide it and make it available to certain people. So this is coming soon with the upcoming release. And just another thing I want to highlight here as well is that record permissions are going to be only available in the production environment at this point.

So please don’t be surprised that you don’t see it in preview and it’s not yet notified on our release pages just because it’s not available in preview.

Next up, we are introducing a new concept of record type hierarchies within workspaces. And as you know, right now the record types and their connections are linear. There is no note of, let’s say, this is a higher level object and then it breaks down to these other things, right? And it makes it very difficult to navigate and understand how the work flows and what is the structure of work. So with this new enhancement, you will be able to define hierarchies within a workspace and even multiple parallel hierarchies in the same workspace. And once you do that, so let’s say, for example, I have campaigns to programs to deliverables to projects. Whenever you open a specific record from these record types, you will see breadcrumbs on top of the record. So this will also help you understand where this specific record stands in my work hierarchy and how it like where does it contribute. And one important note is that you can also use the work front project as part of the hierarchy. So let’s say if you connect the project to one of your activities or campaigns, if you navigate to the project within the breadcrumb section, you will be able to switch to the specific workspace and view where this project stands in the hierarchy for that specific workspace. Or you can then switch back to the native work front breadcrumbs.

Yes, let’s move on. And we also have introduced a lot of enhancements to the connected records pages.

For those who like who don’t remember, connected record pages. If you go to a campaign record, for example, open a specific campaign, you can create custom pages to display its connected records. So, for example, campaigns have connections to programs. You can create a section that will show all of its connected programs. And obviously, we only had one default table view, which was not very customizable and like it was not possible to, let’s say, switch to timeline or calendar views. So what we have done is we are now just introducing the full view system into this connected records page. For example, here on the screenshot, we can see the programs list that are connected to this specific campaign. And here you can like it is switched to the timeline. You can also update the filters, all of its settings or switch to some other view, create a new view and even share the views. And whatever new view you create from here, it will also appear in the main program list as well. So this is basically the exact same view system as in the connected record type itself. And also, it’s not displayed on this screenshot, but if you switch to if time to table view here, it will also have the new role control as well. So you not only can connect new items, but you can also create new ones here. So these are the main things that I wanted to highlight that related to planning. So back to you, Leslie.

Awesome. Thank you. I mentioned in the chat, we somehow my computer, I don’t know if it’s coming back from vacation. It totally skipped one of our interest slides. So we’re going to cover that right now. The big highlights, right? When is this happening? January 15th in the evening mountain time.

If you’re on fast release, it will happen the day before.

So next week, mark your calendars. Helpful tip from former admin. Make sure you are clearing your cash or using an incognito window if you’re starting to see some weird things. That’s usually my first line of defense when stuff starts to happen so you can see if something just kind of got stuck. But yeah, that’s when you might start noticing some things. Wanted to include all these helpful links in here. The release notes. That’s what these are all based off of a link on how you can access the preview, which is where you can look at the stuff ahead of time before Thursday. Customer customer support is always going to be available for you if you have questions or if you run into issues, you start to see bugs.

The status site is great. It will list any performance issues, outages. If you start seeing some slowness or weirdness there, there is the known issues page. That’s another great place you can double check before you reach out to support. But I would say it’s always good to reach out to support so that they know who’s impacted and how large that impact might be if things are going on. And then we did talk a little quickly about the fast release. There’s more information about that if you’d rather get some of these things monthly instead of in the quarterly release, there is an option for that. And then we also have an awesome video from Monique, who’s on today, about how she prepares for a release. So definitely recommend checking that out. Lots of great tips in there. So let’s see what else we got for you. Lots of events this month. We’ve got tomorrow the Connect admin chat for marketing and creative. And then we do our admin one on one series that’s kicking off this month with the getting started with Workfront. We run through setup and some things in there. Resources. If you’re a new admin, if you have new group admins, it’s a great place to get started. We also have the Workfront Collective. If you attended at the end of last year, there was a great exists workshop that Skye and I think it was Nathan did. And there’s going to be a follow up in the community where you can ask questions, get help. She left you with some homework. So that’s where you want to come back and get those questions answered. And then Sam is going to be back with more Fusion goodness at the end of January. So those are some of the great events. We hope you’ll check those out on the Experience League page. There’s an events page that has these on there. And then most not quite all, but most of our past events have been uploaded to the on demand page. So if you miss anything, you’ll want to check that out. We’ve been posting them in the community, but this will be your kind of one stop shop to get those recordings. And that will be where you can find them going forward. So I also wanted to call out Adobe Summit. It’s a little bit later this year. It’s in April, but you are still in prime time to get your registration discounts. So for the early bird details, you can save three hundred dollars on an in-person pass if you register by February 13th. Or if you have a group, there’s a discount for that as well for three or more. So check out summit dot Adobe dot com for that.

We will pop it in the chat, but we would love your feedback on today’s event. There’s just a short survey. It’s anonymous. Let us know what you thought, how we could improve. We do read through those and share those with product. So we’d love your feedback there. And then we have a couple minutes. I don’t know if there’s been anything I know folks have been in the Q&A pod and the chat. Is there anything we want to address live while we’ve got a minute here? So I think at least from the Q&A pod, we’ve got most things taken care of. There was a lot of questions about the deactivated fields and how that was going to affect reporting. And I know we answered that in a couple of places, but I’m just sort of sharing that with product. Like there’s a little bit of heartburn. Their concern, maybe. Yeah. OK. Good to know. Yeah, it’s a big one. I’m not sure about the chat. I think we’re good. Sam, I see you want to ask a question. Do you want to raise your hand? I can give you.

Oh, there. We give you access.

All right, Sam. Yeah. Can you hear me OK? Yeah.

So right now I’m building a solution leveraging fission that depends upon having different calculations in the same calculated field, but on different forms.

And I’m wondering, is there a move towards locking that down so we can not have different calculations in the calculated fields based on the form they’re in? Based on the, sorry, you cut out there. Based on the form that they’re in. OK. Sam, is that something you’re comfortable answering? Sam and Sam. Nice to meet you Sam, by the way. I think that might be a question on the custom forms themselves. Sam, is that right? Is maybe you’re using the same field infusion, but you’re maybe getting two different calculations because of how that field is treated on two different forms? Yes, intentionally. So my concern is that you guys are going to lock it down so that I cannot do that. Is my concern.

Oh, lock down the calculated fields? Right, so that we can’t have different calculations in the same field on different forms.

Because, you know, the feature you guys presented earlier where you could check to see if there was a conflict with a different form.

I’m just wondering if that’s a precursor to you locking it down so that we cannot do that.

I’m not totally sure on that. I work more on the fusion and let me see here. Is anybody with the forms designer still on? Maybe Lili or? Yeah, I’m not really sure to be honest, we could maybe check and get back to you because I guess the PM who introduced that would be the best person to answer correctly.

Okay, we can.

Yeah, take that one offline. Thank you, Samuel.

There was a question in the chat that a few people have been up liking around changes coming to. Yeah, how with frame IO. Jeff, I don’t know if you’re still on this call. He is not. So we’ll probably take that one offline as well. Yeah, but I did make note of that. It was checking to see if he’s here. So we’ll, we’ll take that one and we’ll include something in the follow up email or if we don’t have it in time for that. There will be a post in the community and we’ll follow up there. Heather.

Oh, I have to give you so sorry. You do this for.

Hi. Hi. So my question was on some of those kind of reports on the canvas dashboards that were shared.

You know, I really love some of the features and enhancements to, you know, the charts and customizing the labels and the donut. Is that only available in reports created through the canvas dashboard? Yeah, the majority of what I what I presented today were canvas dashboard visualization enhancements only.

The one exception to that was the first thing that I presented around using the other groups and other teams and other roles.

Everything else was was canvas visualization focused.

So just the ones that you’ve created from canvas dashboard. That’s correct. Yeah.

Okay. Thank you, Dylan.

Hi, can you hear me? Yeah. Hi.

So I asked the question in the chat, I wasn’t able to get to the QA. It just comes up blank for me. But in work front planning, especially with the request, is there any timeline on being able to add documents to those? It is literally the only reason we are not using planning right now, because I can’t have my marketers put in their creative brief in those requests.

Sorry, is this about the work from planning requests? Correct. Yeah. So we’re currently working on that. So the main idea of the request for in work from planning is that whatever was attached or added to the request, whether it’s a text or a drop down, right, whatever. It kind of coming from the planning table. So at the end of the day, the attached documents need to appear on the planning side on the planning table. So we’re working with work from planning team to first introduce the document itself on the planning table and add the support of the document on the request side as well. So if we want the document to end up on the record itself, on the planning record itself, we need to have the document field on the planning side as well. So what I can say is that this is a work in progress and we are working with planning product team to understand the document field on the planning side and on the planning request side. Okay. So no timeline. It’s just something you guys are trying to figure out. Yeah. Yeah. Yeah. That’s something like we have some dependencies that we need to manage there. So definitely something that we want ASAP. This is a priority for both requests and for planning as well. Hopefully Q2. But I don’t want to give any promises because we don’t have the final solution ready from the product side. So once we have that, we can definitely communicate the timelines as well. Okay. Perfect. I just want to let you guys know it is like the only reason that we can’t fully move over to planning right now, which is a big setback with everything that we’ve been working with. But thank you so much.

Sure. Yeah. Thank you. All right. I know we are over on time. Thank you all for your time today. We are going to try and compile stuff from the chat stuff from the Q&A and get that out to you via email later this afternoon. But thank you to our product presenters. Fabulous information today. Get ready for the release next week and keep an eye out for that email. So thank you so much and have a great day.