Product ideas | Community
Skip to main content

10000 Ideas

SubashAnumothuNew Participant

Save button in Settings->System->Customer Info should remain inactive until the user makes changesNew

Description -In Workfront, in Settings->System->Customer Info and in Settings->System->Preferences:Save and Cancel buttons coming without editing anything. Just by clicking into them getting these Save and Cancel. In other sections of settings this is not the Problem, only if we edit anything in that page then we are getting Save and Cancel buttons dynamically. Only in these 2 pages we have this problem. Those buttons not going away even I click Cancel. Only option is to move away from that Page. With this problem it is difficult to say whether I changed anything on that Page or not. (Screen shots attached).Why is this feature important to you - For consistency and user friendlynessHow would you like the feature to work - Should keep the Save and Cancel buttons visible at all times across all setup pages that require saving before leaving to ensure consistency. The buttons should remain inactive until the user makes changes. The experience is different in other pages of Settings. Example below in Settings->Proof Settings When you go to that Page, by default Save button is disabled. Once you edit anything then Save button is enabled. Screen shots below. I am expecting this behavior in Settings->System->Customer Info and Preferences pages also but it is not.Current Behaviour - Detailed above

sanchesanNew Participant

Feature Request: API Access to “Copy Technical Details” JSON in Adobe Journey OptimizerInvestigating

DescriptionAdobe Journey Optimizer (AJO) currently provides a "Copy Technical Details" option in the UI that exposes key configuration parameters of a journey in JSON format. This includes important fields such as throttlingRatePerSec, entryConditions, and activity configuration. However, this JSON is only accessible manually via the user interface, and not available through any public API. Why is this feature important to youWe are building governance and automation processes to validate AJO journeys before and after publishing. One of our goals is to enforce configuration standards, such as ensuring that the throttlingRatePerSec is always set to a specific value (e.g., 500).Having API access to this technical JSON would allow us to implement:Automated pre-publication approval workflowsRegular audits of existing journeysCI/CD-like governance for journey configurationWithout programmatic access, we are forced to rely on manual inspection, which is time-consuming and error-prone. How would you like the feature to workIdeally, Adobe would expose a public API endpoint (via Adobe I/O or Journey API) that returns the same JSON currently available in "Copy Technical Details".This endpoint should return a complete JSON structure with all configuration fields exposed in the UI technical details. Current BehaviourCurrently, the only way to access the technical details JSON is through the "Copy Technical Details" button in the AJO interface or check via UI. This action must be done manually, and there is no documented or supported API to retrieve this configuration programmatically. As a result, automation of journey validation is not possible with the current setup. Thanks!Lucas Sanches AndradeDigital Analyst @3238541 Bmg

AJODevNew Participant

Enable “Stop and Re-Publish” for Journeys in AJO Instead of DuplicatingInvestigating

Description -Currently, when we need to make changes to a published journey in AJO-such as updating content templates or making workflow adjustments-the only option is to stop the journey, duplicate it, edit the duplicate, and then publish it as a new version. This results in multiple versions of essentially the same journey and adds unnecessary steps to the update process.Why is this feature important to you -This feature would greatly improve workflow efficiency and organization. Having to duplicate journeys for every update, especially for routine changes like updating content templates, leads to a cluttered workspace, makes journey management more confusing, and increases the risk of errors. A simpler process would save time for teams and ensure a cleaner, more manageable environment.How would you like the feature to work -After stopping a published journey, I would like the ability to directly edit and re-publish the same journey-including making changes to content templates-without being forced to duplicate it. This would allow for quick updates and version control within a single journey, similar to how other platforms handle workflow and content editsCurrent Behaviour -Once a journey is published, you cannot edit and re-publish it directly. You must stop the journey, duplicate it, make your changes (including any updates to content templates) in the new copy, and then publish the duplicate. This leads to unnecessary duplication and complicates journey management.ThanksAJODev