Build better products with our product team
OverviewThis change request proposes adding functionality to allow users to delete multiple journeys simultaneously from the Journey overview, with built-in dependency checks to prevent deletion of journeys in active states.Current BehaviorCurrently, users can select multiple journeys in the Journey overview (indicated by a blue line showing the number of selected items), but must delete journeys individually through each journey's ellipsis menu.Proposed ChangesEnable bulk deletion of multiple selected journeys through a single actionImplement/Keep as is - dependency checks to prevent deletion of "Published" (including "In review", "Dry Run") journeys. Only delete when status is Draft, Draft (Test), Finished or similar. Add a "Delete Selected" button that appears in the blue selection bar when multiple journeys are selectedDisplay a confirmation dialog showing:Number of journeys that will be deletedNumber of journeys that cannot be deleted (with their states)Option to proceed with deleting eligible journeys onlyValidationOnly journeys in Draft, Draft (Test), Finished or similar status can be deletedIf mixed selection (some eligible, some ineligible), provide clear feedback on which can be deletedAfter deletion, the selection counter should accurately reflect remaining selected itemsError HandlingIf deletion fails for any journey, show appropriate error messageProvide detailed feedback on which journeys were successfully deleted and which weren'tBenefitsImproved user efficiency when managing multiple journeysReduced risk of accidentally deleting active journeysConsistent user experience for bulk operations
BackgroundAudiences currently tracks Audience lifecycle statusThere is no way to know when the lifecycle status was last changed or who changed itBusiness NeedTrack the timestamp when an Audience's lifecycle status changesTrack which user or system process made the lifecycle status changeEnable reporting and analysis based on status change dates and responsible partiesSupport accountability and audit trail for audience managementProposed SolutionAdd two new columns to the Audience table/entity:"Lifecycle Status Updated Date" - timestamp of the last status change"Lifecycle Status Changed By" - identifier of the user or system that made the changeConfigure both columns to automatically update whenever the lifecycle status field is modified:Date field: current timestampChanged By field: current user ID or system identifierMake these fields visible in the IU interface alongside the lifecycle statusInclude these fields in relevant reports, audit logs, and analytics viewsBenefitsComplete audit trail of audience lifecycle changesAccountability for status changesAbility to measure time spent in each lifecycle stageSupport for time-based automation and workflowsEnhanced reporting capabilitiesAbility to follow up with specific users who made changes when questions arise
Description -Why is this feature important to you - Client requirementHow would you like the feature to work - On the kanban board we want to show the details of checklist items or sub task which we added into the ticket can show on board itself along the with ticket name. So user no need to go inside the ticket everytime to see the checklist items and can mark complete from the board.Current Behaviour - We need to go inside of each ticket to get the details.
Today: Landingpages are used for opt out (unsubscribe) to emails. Link to this page is placed in a email fragment in the footer of all email. A standard way of doing this. When this link to this page is created in the email designer tool, it adds a landing-page-id to the link. This in a unique ID that need to be there present for the link to work. And here comes the challenge .... If you use a Sandbox for testing, that many do. We have all our email fragments present in the test Sandbox. And it you then have created links to a landingpage for opt out, that page does not exist in the test Sandbox, or the other way around.The problem:We are running into a problem either way we look at this. If we create the link to the opt out page from the test Sandbox, this will not work when moving the fragments to a Prod Sandbox. Or if the link is created in Prod it will not work in Test. The result of not having the right landingpage present in eighter Test or Prod we are not able to send Proofs. The need:It is not a sustainable solution that we need to change the landingpage-id in this out out links to get email fragments and Proof sendings to work, when working with a test and prod environment. Especially when you easily can move fragments and templates with no problems between Sandboxes. But in most cases it is a link in a footer fragment that will not work if you aren't able to move the landingpages as well.
When moving email fragments from a test Sandbox to a prod Sandbox all Fragments are by default set to Draft when moved. And that is OK. But you need to go into one and one of the moved Fragments and publish them. It would be a faster and more easy way of working it we could select several fragments at once and publish them in one batch. That saves unnecessary repeatable work.
I get an error in the Journey canvas about missing opt out link in the email body. Se attached image. This is not correct - since there is a opt out link present in a Footer fragment in the same template. The opt out link i coded in the fragment, and are present in the same way with the same ID-s that is needed for the link to work. But for some reason this manually coded link is not recognized as a out out link when AJO checks the code/template. Se picture of the code with the link. It would be nice if manually placed code also could be recognized when it is actually the same code that AJO is creating. This is an unnecessary error message that cases a lot of confusion.
In all Sandboxes, prod and test, we sometimes need to clean up the environment. Meaning f ex deleting old Journeys, not used Journeys and Journeys used for testing. Today it is only possible to delete Journeys one by one. It would be better if there where a option where you could select several Journeys and batch delete them with one click. Deleting one by one seems unnecessary and time consuming.
Please give us a savable filter for the Campaign list in Adobe Journey Optimizer. We will have a large number of users creating Campaigns and this list will grow very fast. So we need a way to focus the view of these users to what they should see when they look at the list. Great would be multiple savable filters and a DEFAULT option. So one of the saved filters is enabled when a user enters the page.
In Adobe Journey Optimizer Campaigns there is a feature checking if a mail has any issues or problems. We would like to extend this functionality and make our own custom checks if a mail (or any other channel) fulfills our quality standards. This would include the following checks: - (profanity) word filter- image size- overall size- branding guides (fonts, colors, having color palettes or other brand related restrictions while content editing is also desirable…)- remove tracking pixel if no consent for tracking exists (we want to send to both with the same campaign, recipients that consented and those who didn’t)- check URLs- missing assets- when an audience is selected and we include personalization, let us know how many empty or ’invalid’ records for this personalization exist- audience checks before send (this could also become a part of approval process)- let us do audience count validations before sendout (final numbers, blacklist (suppression) subtracted, quarantines, etc.)
It is nice to be able to store/move and organize Fragments in a folder structure. But when you start to have many Fragments and you want to organize them, it is hard to know witch Fragments is in witch folder, and if a Fragment has been placed in a folder or not. So to be able to work faster and easier we would like to have a feature that could show the name of the folder where a Fragment is stored in the folder structure. It would/should then also be easy to see if a Fragment is still on Root, and has not been moved into any folder. This option would make it easier for the user to manage the Fragments in a folder structure. And with a increasing number of Fragments a fast and easy working process is needed to not spend to much time on administration that should be used on running you business.
We are today able to use folders to structure our e-mail templates in a folder tree. The same folder tree is not visible then you are creating a new email and are picking a template from the customized stored. The folder structure should also bee visible when creating the emails, and not just when to administrate them. It is when you are looking for a specific template in the list of templates you really need the folder structure, and not from a administrative perspective. It seems a little meaningless to having a folder structure when the end user cant see it and use it - the one user that really need it to make the workday faster and easier.
We are today able to use folders to structure our e-mail fragments in a folder tree. The same folder tree is not visible then you are creating a new email and are picking fragments from the customized fragments you have created earlier. The folder structure should also bee visible when creating the emails using fragments, and not just when to administrate them. It is when you are looking for a specific fragment in the list of all your fragments you really need the folder structure, and not from a administrative perspective. It seems a little meaningless to having a folder structure when the end user cant see it and use it - the one user that really need it to make the workday faster and easier, is the user that creates emails - where the fragments is actually been used. We would love if the folder structure became visible also when creating emails, from the email designer.
When you are working with creating fragments or creating email templates you can store these in a folder structure. If you then go into the structure, open a template or fragment to make some changes and save when you then goes back in the GUI you start again from a "closed" folder structure. You dont come back to where you was in the structure. We would like the system to remember the folder you have open, and that you return to that folder after you have saved your changes to eighter a email template or a fragment (both where there is a folders structure created). Not go back to root, and you need to navigate again to find your "work" that you are working on.
Description - Add personalization (direct profile attributes and PQL functions) support to Offer custom attributes to be able to pull content from the attributes inside decision policy used in code-based channel. Why is this feature important to you/How would you like the feature to work - Only way to have content (with personalization) and offer (capping & eligibility etc) configured in one place i.e. in the offer item. Otherwise content need to be written directly in code-based channel personalization editor or in a separate content fragment resulting in long if/else conditions inside decision policy (when there are many offers in the collection used in the policy) that are not user friendly or easy to maintain. This way, business users would not need to touch the code-based channel editor, only the offers. Ideally, personalization code could be written in one custom field and called in another one for easier maintainability. Please refer to image attached. Current Behaviour - Only static text is supported in Offer custom parameters.
Description - Currently, audiences defined in Adobe Experience Platform (AEP) are not directly available in Customer Journey Analytics (CJA). This limits the ability to perform advanced segmentation and analysis within navigational reports.his functionality was previously available when using Adobe Audience Manager with Adobe Analytics, where the dimension "Audience Name" allowed direct access to existing audiences. This enabled the kind of segmentation and analysis that is now missing between AEP and CJA.Why is this feature important to you - The lack of direct integration prevents:a)Analyzing navigational behavior of users depending on specific AEP audiences (designed with attribute conditions).b)Enriching navigational reports with segmentation criteria defined in AEP, especially when such data is not available through connected dataviews in CJA; as this attribute data is not useful for daily reports in CJA.This affects the efficiency of analysis and the ability to make business decisions based on relevant audience segments.How would you like the feature to work - the same way AAM Audiences were available in AA.Current Behaviour - We can only create segments (if the data/conditions used in AEP are available in CJA) or doing "manual jobs" via API, which is not very optimal and productive.
Description - Would love to see an option to add modules to a dashboard that affect the user seeing them regarding a particular approval type. Why is this feature important to you - It stacks all approval-types into one module instead of separate reportsHow would you like the feature to work - Drag and drop the module like it is on the homepage, and change the filters to point to a team of people instead of one person.Current Behaviour - If I use Task, Request and Document Approvals, right now I would need to write three reports. I'd prefer to see all approvals related to a specific team to look just like the Homepage module for approvals.
Request for Feature Enhancement (RFE) Summary: The new editor for content fragments allow to see translations (see screenshots) but doesn't allow to create a translations and you need go with the old editor with a bad UX experience Use-case: I'm an editor and I want to add a translations to a content fragments from the new editor and I need disable new editor go to assets folder and see translations versions and add new translations Current/Experienced Behavior: I'm an editor and I go to edit a content fragment. I click in the right panel and I see if has a translations if case I don't have a translation I can add a new translation Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - Can we have the notifications more robust? Why is this feature important to you - It's important b/c it's my daily life How would you like the feature to work - It would be awesome when you click on the webpage if you could filter by viewed and not viewed? Also if the notifications you need to check would come up to the top. Also, if you check your notification in any other place in the Workfront system can it automatically update the number in the menu to a lower number similar to how Microsoft Teams works? It's very manual to check Notifications in so many different places and they are not linked. Current Behaviour - All you can do is mark the notification as seen
Description –Currently, assets such as audiences and activities created via the Audience API or Activity API in Adobe Target cannot be edited in the Adobe Target UI. Why is this feature important to you –Our customers want to use AI to create audiences and activities automatically. However, there are cases where they need to review and manually edit these assets later in the Target UI. The inability to do so limits flexibility and usability for marketing teams. How would you like the feature to work –We want assets created via the Audience or Activity API to be editable directly in the Adobe Target UI, just like those created manually within the interface. This would ensure consistency and allow users to make adjustments without recreating assets. Current Behaviour –Assets created using the Audience API or Activity API are not editable through the Adobe Target UI. Any updates or modifications must be done programmatically through API calls.
Description -Adobe Workfront allows for setting up complex webhook trigger conditions, including "OR" comparison. This allows for triggering webhooks for cases like "Field 1 OR Field 2 Changed". The "Watch Event" module in Fusion, however, only allows for "AND" conditions. This results in cases where we either need to (1) duplicate scenarios for each of the "OR" cases so that our admins can see the actual trigger conditions or (2) setup the complex webhook trigger using the Workfront API but lose visibility into the conditions within Fusion, meaning our admins are in the dark. Why is this feature important to you -We want to both ensure our admins have (1) clarity on each of the scenarios' setup and (2) not duplicating effort and (3) are empowered without specialty knowledge like having to use Workfront APIs via Postman/curl/etc. How would you like the feature to work -Whatever filter criteria expressions are supported by the Workfront API should be reflected in the Fusion "Watch Events" UI. Certainly, the ability to do an "OR" is one of those essential things. Current Behaviour -See description above.
Description - currently the Workload balancer view maxes out at 12 weeks/3 months. Our team finds it difficult to scope projects when they have to keep adjusting the date range. Adding the ability to scroll to the end of the project would be extremely helpful.Why is this feature important to you - Our team members prefer to scope projects in excel because they can easily enter planned hours over any period of time. it is difficult to get them to use the workload balancer instead because it is more cumbersome.How would you like the feature to work - instead of maxing out at 12 weeks/3 months, max out to the last planned completion date and allow users to scrollCurrent Behaviour - it stops at 12 weeks/ 3 months and requires users to change the view range to keep scoping hours.
Description - Currently we can turn off "log hours" at the project level, but users still see it on their timesheets AND people with manage access still have the ability to track time. It would be amazing if we could turn off completely at the project (or task level) the ability to log hours which in turn prevents a task from showing on a timesheet Why is this feature important to you - we want users to track time to specific tasks and keep their timesheets as easy to view as possible so it's easy for workers to track time and easy for project owners to viewHow would you like the feature to work - a simple option at the project and/or task level to disable the ability to log hours.Current Behaviour - turning off 'log hours' at the project level still shows assigned tasks on timesheets and users with manage access can still log hours.
Description - See screenshot for description.Why is this feature important to you -How would you like the feature to work - We need to be able to right-click on links to open items in a new tab. We also need to see late tasks in a separate category. The "this week" category should be reserved only for deadlines that are still upcoming in a given week.Current Behaviour -
A great addition to Workfront would be the ability to add external links via the Main Menu or Top Navigation bar that could be set via layout templates or by the user (custom pins for top navigation). This would dramatically assist with Workfront becoming the work management solution that can drive users to various areas quickly. Currently, the external links need to be embedded into dashboards and with many users serving many different roles, this becomes a challenge and causes too many clicks via way too many dashboards.
Description: Currently, Issues can only be raised at the project level. However, some issues impact the entire portfolio/program, and therefore need visibility and ownership beyond a single project.How would you like the feature to work: Enable an Issues section in the Program and Portfolio left-hand panel, similar to Projects. Users should be able to raise, assign, track, and report on issues directly at the Program or Portfolio level. Current Behaviour: Issues are restricted to the project workspace only. Program and portfolio views do not currently provide an option to manage issues that span across multiple projects.Example below: Issues section should be available in portfolio and program page along with queue topics management to address the issue.This is a very much needed feature, other tools in the market already offer it.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
