Hi, Something that has been confusing our users is a message they receive when downloading assets in bulk. When they hit "Download," they see a green message that says, "Your download is generating, and will appear in your inbox when ready." Our users see the word "inbox" and think, "this is going into my Outlook or email inbox." So they sit and wait around for an email that never comes. Little do they know, until they ask me, that the "inbox" is different. Totally confusing. Anyone else also find this confusing? Thanks!
Request for Feature Enhancement (RFE) Summary: Improve the UI of user group management in Touch UI Use-case: Authors managing user permissions Current/Experienced Behavior: Current UI can be confusing and hard to read Improved/Expected Behavior: New UI is simplified and made less confusing Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP 13 Customer-name/Organization name: Qantas In 6.5 the group management UI can be very confusing compared to 6.3. The UI by default shows all group memberships, including those inherited by other groups. This can be surprising compared to 6.3 which only shows explicit memberships and it makes it a lot less clear what groups the user belongs to. Additionally, the only visual distinction between assigned and inherited group memberships is that the remove button is greyed out on the latter, which is visually very difficult to tell apart and is a bad indicator of which one is which. I'd like to propose two different solution for this: 1) Instead of greying out the remove button on inherited groups, the button should just be hidden altogether. That would make it very clear which groups can and can't be removed manually. 2) Add a checkbox to filter out the inherited groups. I'd suggest making this disabled by default so it mirrors the 6.3 functionality, then users can optionally check it in order to view the inherited groups that a user has. Current 6.5 UI (it is very hard to visually distinguish the valid and invalid remove buttons). 6.5 UI with buttons removed (as you can see it is far easier to tell which groups are removable. To improve the UI layout maybe the explicit groups can be sorted to the top so that the buttons aren't at random intervals)
In order to create a true data dictionary in Workfront for Custom Fields and Forms we need a few more columns available to us. Currently we are bound to using the Description or Instructions fields to hold our history, calculations etc... The weight of the world is on the name and description fields and it becomes unruly for a user to try and decipher what is happening with the field. Due to this limitation we have to keep our Data Dictionary outside of Workfront which has a host of challenges. We would like to be able to add fields as needed to describe the custom field. Out of the box we have a need for the following: - Historical Changes - would be amazing if it was written for us but I will take a blank text field we can add data too. - Field Calculation - we currently have to put this in the description field along with our history - Audit Type - A place to designate if it is an integration field. - Business Owner field - Business Justification field - etc... As a large enterprise user with over 2000 custom fields it is a daunting challenge to keep up with all of the fields and what their purpose is. Leveraging the current base fields is a starting point but it's not enough to be scaleable.
Request for Feature Enhancement (RFE) Summary: Ability to propagate tag updates on custom fields referencing them Use-case: We have custom fields that are referencing tags. Whenever there are updates on the tag hierarchy like updates and deletions, we would need to do a lot of page re-tagging and updating since the updates are not cascading automatically. Current/Experienced Behavior: Changes on the tag hierarchy does not automatically reflect on custom tag fields Improved/Expected Behavior: Changes on the taxonomy should automatically reflect on the pages using them Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: N/A Screenshot (if applicable): Code package (if applicable):
Alerts are very important to my organization - we use them to send information to vendors and to internal stakeholders. Often times we hear that the alert was never received and there's no way to track what happened - if it bounced, was blocked, delivered, opened, etc. I'm working with a vendor right now with whom we've worked for years and he's suddenly stating that alerts aren't coming through and I have no way to know what's happening with them.Much like email tracking, it would be beneficial to see confirmation tracking on alerts.
Description - I would like to see the ability to take data from one field in Workfront and copy it down to adjacent lower (or upper) fields of the same type, similar to how you can "fill" data in Excel using the corner-drag interface. Why is this feature important to you - Due to the complexity of kickstarts, and the clumsiness of the "edit" interface when trying to mass edit data (too may clicks) I think it would be a big time-saver for users to be able to drag down copied data within the screen interface. Kickstarts are too complicated to allow most users to format and import, and the edit button takes too many clicks to get to the correct custom data section to add the value I want. How would you like the feature to work - I would like to see a dynamic interface on the selected field that indicates the ability to "drag" the data up or down to copy it into adjacent, "like" fields. The assumption would be that the task or project you're trying to drag the data into has the custom form attached and available to hold the data. Big bonus if the system was able to accept a front-end filter to move rows of data that you need to copy into adjacent rows. I think that would be a stretch, but it would be awesome UI. Current Behaviour - Right now the only ways I am aware of to mass copy data into the fields in WF are to use the edit button, after preselecting all of the tasks/projects you want to copy to. You also have to ensure that all of the tasks you selected have the custom form attached and that you also did not accidentally click a single task that already has the value in the field (Which currently completely prevents adding the exact same value to all the other fields you wanted to copy to). The other option is kickstarts. The limitation around the ability to import data to more than one custom form is crippling in this case. It completely hampers the usefulness of the import function. Additionally, using a single custom form actually flies in the face of good data custody and management. I never advise that a team put all of their pertinent data into one single custom form.
I love Adobe Status for current or past issues however I'd love a window into the future. I want a resource that gives me a heads up about scheduled maintenance ahead of time.
It would be so much more de-cluttered if we could apply a filter in here so that we only see the "Experience Cloud" audiences or only the "Target" audiences:
It would be so convenient if there was a place in the Target UI where you could enter IPs to block form showing up in reporting and from seeing experiences.
Description - Request a way to pull/see a report showing historical offer changes for each activity in Adobe Target, especially like a detailed change logs.Why is this feature important to you - This will help us consolidate, track, report and reuse the removed or replaced offers and the impacts these updates made on the Activity's performance.How would you like the feature to work - a report showing historical offer changes per activityCurrent Behaviour - The offer usage shows only if it's linked to an activity and the change log shows only high-level "Updated activity". Reference: Customer care ticket # [Incident: 211116-000423]
Feature: Please provide a feature where an email address can be entered to be notified in case a product feed indexing fails.
I know we can tag individual users within a proof, but we have a need to tag teams within a proof.
Description - Would like to be able to pull in the Resolve and Actions that are on proof comments into reporting. Why is this feature important to you - We need to be able to report on this within Workfront so we can see that our teams are being accountable to their work and give us insight into what decision was made on a comment. This would allow us to also have reports for individual users to know what happened with their feedback or not. How would you like the feature to work - Allow the Document Summary Updates feed to pull in the resolve and action decisions so they can be pulled into a Note or Proof report. Current Behaviour - Does not exist. Screenshots below showing the Proof comment thread versus what is currently in the project doc summary updates.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.