Build better products with our product team
SUMMARY FOR WORKFRONT FUSION detailed Observability requirements.We are working on offloading the Workfront Fusion logs to Splunk and have explored the recently shared Workfront fusion activity log api . Below are the enhancements we are looking to get from Workfront Fusion platform._______________________________________________________________________1.Fetching Notification Logs (Execution State/Errors/history)• Currently Fusion maintains execution logs for each scenario, and you can view these logs in the Fusion UI under the scenario’s execution history.• Enhancement: Is there a way to fetch notification logs or see where they are stored (e.g., scenario stopped, execution errors)?________________________________________2. Enhanced Message Field for Module Actions (Create/Delete/Modify/etc.)• Currently, Fusion logs actions such as module creation, deletion, and modification, but the log messages are not highly descriptive about the specific changes made.• Enhancement: Is it possible to enhance the message field for all actions on scenario modules? More detailed logging (e.g., which field or configuration was changed) for audit and troubleshooting purposes.________________________________________3.Enhanced Message Field for Scenario Scheduling ChangesCurrent Behavior:When you activate, deactivate, or update a scenario schedule (such as changing the frequency), the audit log or message field records a generic message like <user> updated <scenario>.• Currently, the message field does not provide granular details about what specific attribute (like frequency) was changed.• Enhancement: Can the message field capture more details (e.g., “changed the frequency to 30 mins”)?________________________________________4.Retrieving “Folder” Details Alongside Other Properties• Currently, Fusion scenarios and modules do not natively expose a “folder” property in the API responses.• Enhancement: Is there a way to get “folder” details with properties like teamId, entity, etc.?
We have Workfront proofing custom form with fields, as per requirement we have to hide the few field values. We have submitted the Adobe Support request (https://experienceleague.adobe.com/en/support?support-tab=my-cases&case-id=E-002089146&org-id=A1B8BC4D584032500A495DE5%40AdobeOrg#home) & team suggested to submit a feature request to enhance the feature. Example: Field Name: Vehicle (Project Type) Field Values to hide: Digital Paid Media and Third Party E‑CommerceFind the attached screenshot for more details;
Description - ability to create custom fields/forms that we could attach to hour types in WF.Why is this feature important to you - would allow for improved grouping and reporting for charts and graphs.How would you like the feature to work - TBDCurrent Behaviour - Not able to lump hour types together in current setup.
This might sound unusual, but I request custom form for HOUR object. On hour records, such as on January 1, we would like the option to enter more information along with the comments.There is where the custom form should be available:
The flow test option in Dynamic Chat is a great tool and our team loves it for testing that the answers go the way we want it to. The only downfall is that if you have the 1st node (possibly others) as a conditional set, for example we have it set to identify customers vs everyone else, you can only ever test the first path. There isn’t currently a way to use the testing option to go down one of the other paths to see how the conversation will work. I’m not sure the best way to implement this, but perhaps in the test flow, the 1st option can be select your branching option? Or something similar?
Request for Feature Enhancement (RFE) Summary: Use-case: In AEM, a proper preview can be generated, but this functionality is missing in Content Hub. Current/Experienced Behavior: Many assets are stored in ZIP file formats, but Content Hub currently displays them as blank folders or icons. Improved/Expected Behavior: need for a feature to generate previews for ZIP files automatically to avoid manual effort Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
There’s a function that I really like in the Developer Console: In order to delete a project, you need to enter the name of the project in order to delete it.It would be nice to set some Workfront objects with that setting (request queues, certain projects, etc.). Perhaps a toggle switch on the object’s settings.When you’re an admin and you’re stressed and you have 20 tabs open, the possibility of deleting something you shouldn’t becomes greater than 0%. If the admins have the power to delete anything in-system (and we do), we should have a check on things to ensure that we’re deleting the right things.
Currently with Dynamic Chat, if one of our BDRs misses the chat, the only option is to display a message and possibly display their calendar link. What we would like to have is if the agent misses the chat, after it displays the fallback message, we want to reroute it back into the bot workflow to ask additional questions so we can send it to someone to do a follow up. It’s a better experience as well for someone engaging with the bot because it isn’t just a they’re not available and that’s it.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK