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
This request is for Adobe Target. Please add to the Target Admin API "List Activities" endpoint a param/value pair with "modifiedBy" that would correspond with the already-existing "modifiedAt" param/value pair. Doing this work manually takes 1 FTE an average of 7 hours/month. This costs us $21k/year and hundreds of thousands in Business Decisions made from this.
Currently, we can only retrieve deleted Projects, Tasks, Issues, Documents, and Templates from the recycle bin. Sometimes, Template Tasks are deleted by mistake and also need to be restored. Because this is not an option in the recycle bin, however, we have to rebuild these from scratch if they are deleted accidentally.
Description - Allow DWG file types to be ProofedWhy is this feature important to you - We have many different Teams who use AutoCAD for initial designs and wish to collaborate via Proof. Current State these Users have to convert this file type into a pdf, which greatly increases their workflow. How would you like the feature to work -Like any other approved file type in ProofCurrent Behaviour - It is not a supported file type
Hi, I have a suggestion for Approval Processes. Right now, when an Approval Process is attached to a Project, Task, or Issue, any time that object is put into the status it triggers the Approval Path. What I would like to see is a configuration setting that would only allow each Approval Path to trigger once per Approval Process use. For instance, I have a Project that triggers an Approval with three Paths‚ÄîCurrent, Go-Live, and Complete. Once the Project goes Current, and then moves on to another status, I don’t want that Project to be sent out for approval again for the Current Status, even if it is put back into it. Then the same would apply to the other Statuses on that Approval Process as well. I think the current setup is fine, as there is definitely a use-case to re-trigger Approval Paths multiple times. Could we get a setting when configuring the Approval Process to toggle whether each Path could only trigger once, or multiple times?
It is important to us that, when you import a package with changes to existing email Fragments the existing Fragment can be updated not just imported. When you use Fragments in many templates it become a problem when the Newley imported fragment comes in as a new "file with a new id" the templates using the old existing fragment is not been updated with the new version. This most be done manually template by template where the fragments is used - and change the old one to the new one. We hope that this can be automated when importing a fragment you can choose is this new one should update a old one - and witch. Even better is you also can do multiple selection where it is the same process for many segments.
We would like to have the possibility to put conditions on a whole e-mail fragment, on the fragment it self. Meaning when creating a Fragment it would be nice to be able to create conditions on how the fragment should behave when been used. It could be conditions like, who should be able to see this Fragment and not bases on attributes. This can be done today but with coding it directly in the Fragment code. A interface to do this would be very helpful and create a new dimension to the use of Fragments. Yes this can be done inside the template when dragging the fragment in, and setting the condition on the container - but it we do this in the fragment itself this is then pre defined for all user that used this fragment - and is working directly out of the box when dropping the fragment into a template. This is really helpful if you are creating a library with pre defined Fragments with pre defined logic on the fragment. Then the end user can just use them without setting the right settings every time the fragment is been used.
Description - Would love to see Adobe Journey Optimizer enhanced with an AI-based feature that detects and alerts on journey anomalies—such as sharp engagement drops, routing errors, or unexpected delays in customer progress.Why is this feature important to you - Improves real-time decision-making by flagging issues before they hurt the customer experience.Helps marketers optimize journeys proactively rather than reactively.Reduces manual effort in monitoring complex journeys across channels. How would you like the feature to work -This could be powered by Adobe Sensei and visualized through a heatmap or alerts dashboard, with potential tie-ins to Adobe Analytics and Workfront. Curious if others see value in this? Would this help your teams optimize journeys more efficiently?
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
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
Current Behaviour - Currently there is strict rule when it comes to capping. If we set up capping ex. 5 mails i one month then 6 mails in that month would not be send. Why is this feature important to you - service companies (telco, banks) have churn campaigns. Often they would like to ignore message capping rule in order to retain customer How would you like the feature to work - simple checkbox with text - ignore capping rules in journey properties
Description -Why is this feature important to you - to quickly and easily see what has been sent to our customers and to continuously check and monitor it How would you like the feature to work -similar to the email channel, I can store a seedlist in the channel configuration Current Behaviour - it is not possible to do this in a simple way, we make do with including individual profiles in the segment which we then exclude from the contact rules, all very cumbersome
Description - Increase the maximum number of nodes allowed per journey Why is this feature important to you - for companies with multiple brands (including different sending domains) and complex journeys, this will allow journeys to be condensed into one true journey, allowing customers to flex brand in line with real-time behaviour whilst continuing the journey. We are also limited by the number of journeys allowed, this will reduce the number of journeys that we require whilst streamlining journey management. How would you like the feature to work - For the cap on number of nodes within journeys to be increased, to allow more sophisticated journeys and the encompassing of more channels. Current Behaviour - We are capped by the number of nodes and have to split out programmes across multiple journeys
We have in several occasions experienced that created content in a email templates disappears - and needs to be redone. This is extremely annoying and time consuming for the content producers. There are several theories what this happens, some from you at Adobe also. Like: there is several tabs open with the same template open, or there are several users working on the same Journey and/or email at the same time. To avoid this kind of situations where content actually disappears, we would like to have a features that lock the content to the user that has it open - and changes can not be done to the content by other than one user at the time. When open and try to change content when it is open already a warning message should appear and inform that this template/journey is blocked be user xxxxx. You can take over the editing role by overtaking the role. What we would like is basically a build in control feature that makes it possible for just one user to make changes at the same time to emails and Journeys.
When you have many master e-mail templates in use, and you need to do a change f ex to styling that is placed in the Head section of the templates, it takes a lot of time to update all templates with the change. If the email templates could have a centralized place where the head section was stored it could be maintained from one place - the whole style config used in the head section for all templates. This makes it easier and faster to maintain the system especially when you have many different templates to maintain.
It is important to us to be able to select multiple email templates at the same time and do a batch delete instead of deleting one by one. This is time consuming and unnecessary. The same goes for archiving Fragments. It would be nice if we could have multiple selections of Fragments and then do a batch archiving. A similar process is also wanted when you are creating a package of templates and/or fragments to be moved from one sandbox to another. It would be nice if we could do a multiple selection instead of selecting one by one fragment and one by one template into one package, This is time consuming for a administrator to do. We hope for a better and smoother solution here.
Currently we have an inhouse design team utilizing Proof to get approvals on animated web advertising. However, these ads have to be built at several unique sizes and all of them need signed off on. Since the only way for the approvers to see the animations is through a video proof, the designers are forced to upload all these sizes one at a time. This is making the tool more time consuming for them and also more frustrating for the approvers who have to open all these separate proofs for these very small, very similar pieces of art. Any way to address this would be appreciated.
Description - Customize the Task Summary in Workload BalancerWhy is this feature important to you - We would need to customize fields that are getting displayed here so that it is each for the resourcing manager to choose the required fields that is neededHow would you like the feature to work - Provide an option to user to choose the fields that are displayed in Open summary section. This should be either controlled by assigning appropriate Template changes Current Behaviour - No option to edit the fields that are displayed in Task Summary field
I was developing a campaign to track records created by Web API users and assign a specific person source accordingly. Although the campaign was set up, it currently qualifies all records created via the API because there’s no way to specify or filter by the individual API user. To improve this, I suggest Marketo to introduce a "User" constraint in the trigger “Person is Created” and the filter "Person was created" to identify which user created the record. This capability would streamline tracking and attribution, making campaign management more precise and efficient.
Description: I would like the "Create CSV (Advanced)" Fusion modul to include the options "delimiterType" (Comma / Tab / Other) and "Delimiter Character" (displayed & required only if "delimiterType"="Other"), so that I can generate a CSV file with not only Comma as a delimiter.Why is this feature important to you: This would allow us to generate CSV with delimiter aligned to local needsHow would you like the feature to work: Delimiter in the generated CSV file is defined by the user in the module configCurrent Behaviour: CSV is always generated with comma as delimiter
Description - As an queue owner, I need the ability do deactivate a Queue Topic without having to delete it or obfuscate it by moving it to a "hidden" topic group.Why is this feature important to you - this will save a lot of time and effort when managing an intake queue. Allowing me to toggle a queue topic will also support intakes windows (e.g. annual or quarterly intakes) without having to (a) leave the queue topic open and manage misdirected requests, (b) delete and recreate the queue topic each time it is needed, or (c) move the queue topic to another section (e.g. z_do not use - ugly!) and back again when i need it. How would you like the feature to work -I would like to be able to "edit queue topic" and toggle an option to "deactivate queue topic / active queue topic"Current Behaviour - No functionality exists to deactivate a queue topic.@jessere1
It would be great if you could customize a calendar on the Vi !rtual Report Suite level rather than only on the parent report suite.Example: Creating a virtual Report suite which has the week starting on Mondays instead of Sunday.
Description - Add a toggle switch to queue topics that allows deactivation of the topic.Why is this feature important to you - When we need to revise a queue by way of omitting a topic, we have two options: delete the topic, which deletes the associated data, or rebuild the queue. A deactivation switch for topics would make queue administration much simpler and efficient. Additionally, it would bring the functionality in parity with many other objects in Workfront.How would you like the feature to work - Similar to many other objects in Workfront, there would be a simple toggle switch to deactivate a topic. This would hide the topic from general view, but retain detail.Current Behaviour - We cannot deactivate topics.
Description - When building a custom form you can view fields and sections in the form library. On the right panel it will note if it is used on other forms and you can click "view related forms" to get the full list. This list is incredibly helpful as is but would be more powerful if it indicated active vs inactive forms. Why is this feature important to you - Knowing that a field is only seen on inactive forms would quickly indicate that it shouldn't be used for the form I am creating/updating. It also tells me that if I wanted to make an update to the field (hide/show a choice, rename it, change the lable) no active How would you like the feature to work - Even something as simple as making the inactive forms gray and keeping the active as blue would help. Or if there's more real estate adding an x icon next to inactive forms. Another idea is to split the list into two sections one for active and the other inactive. Current Behaviour - I have to either open another tab, look at the custom forms list and quick search the form name to see if it's an active form; or run a report for active forms and see if these are on the list
Request for Feature Enhancement (RFE) Summary: When user account is created in Admin Console side, then the user gets sync up with AEM & user is shown in AEM side.In the same way, when user account is DELETED from Admin console, then that user shall be removed from AEM. Use-case: Management of user addition, user deletion from Admin Console. User addition/deletion policy shall have a clear user case in association with Admin Console. Current/Experienced Behavior: If existing user is DELETED from Admin console, then that user is shown as "enabled in AEM" & not removed from AEM. Improved/Expected Behavior: When user is created, then the user is shown in AEM side.In the same way, if existing user is DELETED from Admin console, then that user shall be removed from AEM Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud 2021.05 version Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
