Adobe Workfront Fusion

Description - We have fusion users who create fusion scenarios, but are not acting as system admins within Workfront. To create fusion scenarios, users must be given the access level of System Admin.  For example we have users within our Corporate IT team who are experts in Jira. They create fusion scenarios that link Workfront into Jira, but their expertise in within Jira. They take training on how to work in Fusion, but their focus is not on being a  Workfront system admin. They own, document, update their fusion scenarios.Why is this feature important to you - We have users in Fusion who show as System Admins, when in reality they are not system admins. They only author and maintain fusion scenarios. We would like them to be assigned a newly created access level to denote that they are Fusion only users. We don't want or need them to be viewed as system admins, because in reality they are notHow would you like the feature to work - We would Adobe to develop an access level

Description - Please make available a production-ready Fusion API for back-end management purposes.Why is this feature important to you - Customers often have use cases where they would like to be able to automate the management of their Fusion environment. Currently there is no publicly documented and supported way to do this. This could allow Fusion customers to be more responsive when there are errors with their scenarios, or they wish to monitor the usage volumes of scenarios, or they would like to automate other DevOps style processes such as cloning scenarios, datastores etc.How would you like the feature to work - Allow API interaction with objects including Connections, Data stores, Data structures, Webhooks, Notifications, Organizations, Scenarios, Scenario folders, Teams, Templates, UsersCurrent Behaviour - Everything must be done via Fusion's UI without automation.

Description - As a Fusion Developer, I would like the ability to manage my scenario versions.Why is this feature important to you - Currently, Fusion devs can only add notes per module and we can only view changes by reverting and comparing. It's very cumbersome.How would you like the feature to work - It can be very basic to start. It should allow developers to understand what has been modified, added, or removed between different versions of the blueprints. It should allow side-by-side diffs, inline diffs, historical comparisons, and notes. For notes, it should allow Commit Messages when making changes, a change log generation that is easier to read (right now we only have the history), As a bonus, issue tracking would also be great.Current Behavior - Currently, Fusion devs can only add notes per module and we can only view changes by reverting and comparing.

The dateDifference(t1; t2; unit) function in Fusion allows you to compute the number of hours/days/etc. between two timestamps (t1 and t2) provided.  This behaves oddly whenever the number of hours in a day isn't exactly 24, which happens twice a year when crazy countries/localities switch between Daylight Savings Time and Standard Time.Example: On March 10, 2024, at 2am, the clocks "jump" forward to 3am.  That is, there technically is no 2:00am to 2:59am on March 10.  This results in March 10 having only 23 hours in the day.  (The same thing happens on November 3, except we actually repeat 2:00am to 2:59am, resulting in 25 hours in the day.)This website has more information that corroborates: https://www.ge.com/digital/documentation/csense/version2023/Blocks/Daylight_Saving_Time.htm#:~:text=In%20spring%3A%20if%20a%20one,the%20day%20to%2025%20hours.If you're trying to use something like dateDifference(t1; t2; days) and expect something like 2024-03-09

Description - OAuth authentication to Adobe Experience Cloud applicationsWhy is this feature important to you - Use OAuth to connect to AEC applications. A JWT private key has an expiration date and needs to be refreshed.How would you like the feature to work - A connection within Workfront to an AEC product (AJO/Target) should us OAuth instead of a private key.  OAuth does not use a private key to exchange for a bearer tokenCurrent Behaviour - To obtain a bearer token a private key is required.

Description - Add triggers to start the scenario for Adobe Target Fusion module so that it helps users to automatically run the scenarios based on an event trigger.Why is this feature important to you - The ability to add triggers for Adobe Target Fusion module is essential as it empowers users to automate scenario execution in response to specific event triggers. This feature enhances efficiency, enabling real-time, personalized content delivery and optimizing user experiences.How would you like the feature to work - For an ideal implementation of this feature, I'd like users to be able to define triggers within the Adobe Target Fusion module. These triggers should include a wide range of event types, such as user interactions, system events, or external data signals. Users should be able to set conditions and actions, allowing for the seamless automation of scenario execution when the specified trigger conditions are met. Current Behaviour - Users are limited to u

Tools to help better manage scenario performance would be useful to know where to focus efforts on optimizing scenario configurations.  For example, given a scenario that calls three services, a heat map showing overall processing time of a given module could indicate that a module or set of modules is heavily utilized and could benefit from a 1-2% improvement in performance.Examples of metrics to consider include:Processing time per module operationTotal processing time per module operationProcessing time variance per module operation

The Encryptor module in Fusion currently only supports ASCII Armor encoded files.  Armor-encoding bloats file size significantly and is generally not as preferable for SFTP transfer as binary-encoded files as a result. PRIMARY ASK: Have the Decrypt a PGP message module automatically detect whether the input data is Armor or binary encoded. SECONDARY ASK: Have the Encrypt a PGP message module to have an advanced option to allow the user to select which mode is preferred.

 To count items in a data store based on a condition (ex: Field = "some value"), a Fusion user has to setup a structure similar to the above:Initialize a counter to 0Search the whole data store based on the conditionGet counter referencesIncrement the counter by one each timeThis is required because the Count records data store module does not allow for conditions.The ask is to enable conditions on the Count records module.  Even if you internally have to do it via a looping mechanism like this, it greatly simplifies the life of the Fusion user and makes it an inline module rather than having to do the above PLUS the required router (ahead of the above flow) and another branch off that with a Get Variable module to get the result of the count.

We routinely have to do grouping when making API calls.  That can be over several thousand objects, grouped into bunches of only 50.  It's inefficient to deal with it using the existing mechanisms, such as aggregating to a list and then doing complex slicing with a Repeater.  It would be much more resource-efficient to have a module that aggregates up to some number "N" into a single output array.

If you "clone" a module that has input filters, the input filters are dropped.  But if you "copy" and "paste" a module, the input filters are brought over.  It's the weirdest little idiosyncrasy.  "Clone" doesn't feel like a "clone" if some aspect of it gets missed in the cloning process.(Certainly not a high priority ask.)

Description -When making edits to a scenario, we're finding the process of tracking down all usages of a reference to be cumbersome.  Our current process is to download the blueprint, open in a separate editor, and Ctrl-F to find the one(s) desired. It would be preferable to stay in the Fusion UI but have a way to "highlight all usages" based on selection of a reference ID.  That reference ID could be input using the {{14.something.`foo bar`}} syntax, even, to allow for the case where the reference has already been changed. I would NOT want a find-replace, per se, as sometimes applying the change requires consideration of other changes to go with it, hence why the ask is limited to helping identify the usages. Why is this feature important to you -If I'm a Fusion admin, keep me in Fusion.  Switching to an external tool disrupts my workflow. How would you like the feature to work -See above. Current Behaviour -See above.

Currently, there's no way to expand all operations within a Fusion module's execution bubble.It takes painstaking efforts when triaging an execution and I have a need to find an ID within a large number of operations on a module. It would save a ton of time to be able to auto-expand all operations within a module's execution, so then I can easily search (CMD+F) all operations for a specific ID.See attached screenshot.Cheers!

Description - The Webhook module in Fusion exposes an API to be called which is not protected by any secured/modern authentication method. There is a way to apply a filter on the request to check for an authentication header, but that would only support Basic Auth. Adding a native support for OAuth (likely using the Adobe IO credentials) would be a great addition to expand the use of the Webhook APIs. Why is this feature important to you - We (Best Buy) have a lot of use cases where we would want to push data from other applications into Fusion and eventually update it in Workfront. Right now, we cannot use the Webhook module because the API is not protected and doesn't support OAuth which is a core requirement by our enterprise security. How would you like the feature to work - The Webhook module should be supporting the OAuth 2 authentication which could use an Adobe IO project to generate the client credentials and validate the auth token passed in the header for the Webhook API re

Description -  Allow Fusion users to refresh Workfront API metadata on demand, rather than every time a module is opened.   Why is this feature important to you - Currently every time you click on Workfront modules (or even other connectors), it takes a long time to open because Fusion refreshes the metadata (list of available fields).  This makes it very slow to move from module to module and review or edit the configuration.  It's actually extremely rare that you really need a metadata refresh due to fields being added/changed in Workfront, and so the negative performance trade-off is not worthwhile. How would you like the feature to work -  It would be much better if there was a 'refresh metadata' button in the scenario, which would cause Fusion to refresh the metadata from the APIs of the used connectors. Even if this was only implemented for Workfront's connector it would be a massive improvement. Current Behaviour - It refreshes every time you

Description - Many times when I attempt troubleshooting problems in Workfront, I find I need to look up information from a few months back. And, of course I attempt to do just this and I can't. Ultimately, there should be at least 90 days worth of historical data.  Why is this feature important to you - I can't troubleshoot problems if I don't have the information. How would you like the feature to work - Just like now, but 90 days instead of 30.  Current Behaviour - 60 days less of historical data than what I need.

Description - We try not to edit Scenarios when live, but there are times when we do. And invariably, we replace the module and neglect to update a filter. This causes lots of error spam.   It would be good to see the same little number one sees on a module on a filter so we can fix the issue before it becomes a visible error. 

Description - Add an icon/indicator to let you know that a scenario save is still in progress.  There is only a text notification once a save is completed. Why is this feature important to you - Sometimes when you click the 'Save' icon it takes quite a long time to save. After a while you wonder whether the save has completed yet or not. There is no indicator currently to show if it is still in progress.  Sometimes you click save again and then the first save finishes and you later get another save confirmation.  Alternatively you might close the browser before the save completed and then you lose your edits. How would you like the feature to work -  Either change the colour of the Save icon to indicate that it is pending, or add a spinning circle on top of it, or even a progress bar. Something to show that it is still working on it.

Description - Enable variables that can be set at a team level and are available across multiple scenarios. Why is this feature important to you - This would aid in migrations of scenarios from team-to-team and avoid manual reconfiguration of scenarios when doing so.   How would you like the feature to work - E.g. You could store the Workfront instance subdomain (my/sb01) in a team-level variable for use in URLs that are populated into Workfront or other systems.  When a scenario is moved to a new team it would reference the variable of the same name and automatically pick up whatever subdomain is relevant for the Workfront connection in that team (production/sandbox etc). Current Behaviour - You have to manually change a variable in each scenario when moving it between teams.