Build better products with our product team
Description - Sometimes I create multiple panels for experiments and one is for historical information (last 3 months) and the rest are to measure the experiences. If I use "apply to all panels", it will change the historical one too, and I don't want that.Why is this feature important to you - It would save time and ease frustrationHow would you like the feature to work - I would like to either lock a panel's dates or group panels so that I could "apply to all in the group"Current Behavior - It is either all or none with panels.
We would love if the proofing tool could support internal PDF reference links that are built within the initial PDF rather than converting it to a flat image. For instance, if a large manual/guide is uploaded with a table of contents that has page numbers that link to other pages, or if there are "jump to page 5" or "return to contents" type links that would work in the actual PDF, that these links would work within the proof viewer also. Currently our reviewers have to download and open the PDF separately to test all of the PDF reference links, then go back into the proofing tool to comment things like "link does not go to proper page" or "link is broken", etc. This takes extra time and creates room for error. Current behavior is that the proofing tool only supports clicking links to external sites (like if there is a link for www.testwebsite.com, you can click that link within the proofing tool), but if you click links that move you to different parts of a PDF (like "jump to Table of Contents"), they are no longer clickable and become just a flat image. We would like these links to still be active and to move you to the proper page/location within the proofing tool. Thank you!
I would like to suggest the addition of a new functionality to record issues on the Portfolio/Program page.Currently, there are workarounds for recording Portfolio level risks/issues, but there is no direct way to register them on the same page. This could be a valuable addition for portfolio managers who want to register risks and issues that are not specific to a particular project, but rather a higher-level concern.This feature would enhance the program and portfolio management capabilities and visibility of such higher-level risks/issues.
Description - It would be great if within Launch we could apply tags to rules and data elements to categorise. We have to get creative with naming conventions to describe what a rule does and what is firing within it. If I could tag a rule with "google ads" and filter all the rules where that tag exists, I can easily edit a pixel firing on those rules. Right now, I have to write it in the name or click into every rule. Other tag managers have this simple UX feature. Why is this feature important to you - It helps us organise our implementation, and saves a lot of time. QoL function. How would you like the feature to work - Explained in the description. Current Behaviour - As above - naming conventions have to do all of the heavy lifting.
I'm referring to the functionality outlined here: Configure system updates & System-tracked updates Currently:When making changes to a Project template there is no indication in the update stream of changes made. Additionally there are no options to add template specific fields to the update stream. This means that there are very few ways to identify when and what changes were made to a project template. If a user mistakenly removes a predecessor from a task or modifies the assignments we have no way of knowing. What I would like to see:It would greatly improve project management and troubleshooting if changes made at the project template level were tracked in the update stream on the template. Additionally, it would be helpful to have the ability to add template specific fields in the update stream. This would make identifying the source of timeline related issues easier by giving some insight on when changes were made to the template. As a side note: I also think it would be great to have the option to track changes to predecessors in the update stream as well.
I'd love the ability to permission people/roles from seeing previous versions of a proof in Workfront Proof. For example, we start routing a proof internally and it goes through several rounds of proofing. Now it's ready for the client to see it. I'd love to send the most recent approved version to the client for review but don't want them to have access to the previous versions. They mark that up, edits are made, another couple rounds of internal review and then the approved version goes back to client. At that point they only have access to the versions of the proof they were a part of. Why is this feature important to me? This would allow us to have one document that spans the entire life of the project but would prevent clients from seeing all of the back and forth that happened to get that piece approved. To accomplish this in the current state we have to create a clean document to send over for client review. When we go that route we are left with 2 unappealing options: 1. Have multiple documents for the same deliverable or 2. Someone has to transfer all of the client markups back to the original document's proof.
Description - Would like to have the ability to 'sort' report data, specifically data from a field that allows for more than 1 selection so that further excel work could be streamlined. Why is this feature important to you - This is important for our budgeting system that we built in Workfront. The data captured in Workfront is exported to excel frequently and further looked at/put into pivot tables, charts, etc. How would you like the feature to work - To have an "advanced option" in that column of data to sort the data in a specific order, or even order of how the field values are displayed in the field would be great. Example: we have apple, orange, banana, peach and plum as field values. Adam selects apple and plum and his data shows as Apple, Plum. Lucy select apple, orange, banana and her data shows as Banana, Orange and Apple. While looking at Adam and Lucy's data in our report, Apple is not aligned as the first option therefore when exporting to excel it makes it more difficult to continue reviewing the data.Current Behaviour - Workfront currently displays the data in a report in the order it was selected by the user.
Request for Feature Enhancement (RFE) Summary: The AEM Content Fragment UI should allow users to configure columns based on their preferences, making it easier to display the desired information in a more accessible format. Use-case: In the view settings menu or directly in the table results, we should be able to customize column options based on the available fields in the Content Fragments. Current/Experienced Behavior: In the settings (Customize Table), we can only select a few generic fields. Improved/Expected Behavior: Our goal is to be able to select any available fields in the Content Fragment (configurable) such as the variations, the profile owner, the profile image, the title, the description, the social media profiles, the country, the city, the job type, and the skills. We want to display the selected fields in separate columns according to our preferences. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Accenture Screenshot (if applicable): Current options for "Customize table" Code package (if applicable):
Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Make Managed Publication working for Content Fragments as it is working already for AEM Sites for References. Anwendungsfall: Managed Publication for Content Fragments Aktuelles/erlebtes Verhalten: References can't be controlled in a meaningful way for Content Fragments. Modified & unpublished References are just published as part of the Managed Publication without any control about it. Verbessertes/erwartetes Verhalten: Managed Publication for Content Fragments is expected to work as in AEM Sites, incl. enhanced filter possibilities. Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): AEMaaCS Name des Kunden/der Organisation: Accenture PLC für smart Europe GmbH Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Request for Feature Enhancement (RFE) Summary: Would like the following feature - Extend AEM Assets Bulk Import to have other data sources besides Azure Blob Storage or S3 instance. Use-case: We want to import assets to AEMaaCS from other 3rd party cloud-based CMS such as Kapost and Box. Currently the best alternate option seems to be to transfer data (6.5 TB) to a S3 or Azure instance and then migrate it to AEM. Current/Experienced Behavior: No option to configure an alternate data source (save S3 and Azure) for cloud to cloud migration Improved/Expected Behavior: Ability to configure custom 3rd party cloud data source to import assets and metadata in bulk from any cloud based CMS. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS - Version - 2023.03 Customer-name/Organization name: TA Digital Screenshot (if applicable): N.A Code package (if applicable): N.A @kautuk_sahni
When a task/issue is assigned to multiple people, individual users can mark 'done with my part.' This is not available for tasks/issues assigned to Teams. Would like the ability for anyone in the assigned Team to be able to mark 'done with my part.'
Description - You're doing well with v1 of the Data Dictionary, but you still have room to improve. You need to add a line where components are missing tags. Why is this feature important to you - Yes, they are optional to add, but these are a feature that make components so much easier to find, use, and manage, that once people understand the value, they will want to be able to manage them better.How would you like the feature to work - Just like the current interface, add another line that has a filter button to view all components missing Tags.Current Behavior - Currently, we are only given the four choices below:
Straightforward idea: with folders.json effectively acting as an "all assets" query at this point, could please get the ability to segregate out what assets are retrieved by having the folderType value available for parameterization?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.