Request for Feature Enhancement (RFE) Summary: Image component loads rendition based on screen size, not target image size. Use-case: Google Lighthouse score complains that images are too large. Images should be sized depending on their target size. Our portrait thumbnails are loaded mostly at 1600 px width (based on screen size), although thumbnails only need to be around 500 px width across most screen sizes. Introducing the HTML "sizes" attribute did not solve the issue. The only thing that helped so far is to upload small-scale images for thumbnails. But we don't like that approach. Editors should not be required to think about images resoluition. They should just upload their high-res images and AEM Assets does the magic. Current/Experienced Behavior: Thumbnail-sized images are loaded at 1600 px and scaled down by the browser to fit into the target space leading to unsharp images or image artifacts. See attachments. Improved/Expected Behavior: The Image component loads a rendition that fits best for the target height and width. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: VERLAG DES OSTERREICHISCHEN GEWERKSCHAFTSBUNDES GMBH Screenshot (if applicable): See attachment. Code package (if applicable):
Description - Please add an option to sequential segments for After Current VisitWhy is this feature important to you - Using After 1 visit leaves a data gap of the next visit.How would you like the feature to work - Same as current sequential segments, but allow After Current Visit to optionCurrent Behavior - Limited to after 1 visit, which excludes the next visit. Here's an example from demo data
Request for Feature Enhancement (RFE) Summary: Allow AEM Folders and Assets Move in AEM Desktop Version 2.3.0 Use-case: Move Feature in AEM Desktop Application v2.3.0 Current/Experienced Behavior: Currently we are unable to move assets and folders in AEM Desktop application. Improved/Expected Behavior: Move feature should be allowed for moving assets and folders (individually at-least if not in bulk) Environment Details (AEM version/service pack, any other specifics if applicable): AEM Desktop Application v2.3.0 Customer-name/Organization name: TA Digital Screenshot (if applicable): Code package (if applicable):
Teams often want to brainstorm and begin to organize a list of tasks in something like Word and/or Excel. To avoid the cumbersome process of "uploading" the list into a project via a clunky kick-starter template, teams would like to easily copy the list of tasks from Word/Excel and paste them into a Project. Other programs they have used in the past have made this a common-practice approach. So, having a fast way to just copy and then paste a raw list of tasks into a project at any time would save time and decrease frustration/complaints.
Add a timer to Timesheets that helps to manually track time spent on a task.
Integrating the capability to bulk move Workfront Programs to a Workfront Portfolio is crucial for streamlining project management processes and enhancing user efficiency. The current limitation of manual, one-at-a-time processing for this task creates a bottleneck in workflow management. To address this, developers should prioritize the inclusion of bulk editing functionality for Workfront Programs, aligning it with the existing capability for Workfront Projects. This enhancement not only ensures consistency in user experience but also maximizes the utility of the platform. Potential implementation strategies include:Unified Interface: Design a user-friendly interface that allows users to select multiple Workfront Programs and initiate bulk moves with a few clicks.Customizable Filters: Integrate customizable filters to facilitate the selection of specific programs based on criteria such as status, deadlines, or assigned teams.Batch Processing: Implement a batch processing mechanism to handle the simultaneous movement of multiple programs, optimizing efficiency for users dealing with large project portfolios.Error Handling: Include robust error handling mechanisms to notify users of any potential issues during the bulk move process, ensuring transparency and mitigating the risk of data inconsistencies.Audit Trail: Incorporate an audit trail feature that logs all bulk move activities, providing users with a comprehensive record for tracking changes and troubleshooting if necessary.Assistance provided by an AI
Description - I'd like the ability to be able to create cross-project predecessors in project templates. Currently you're only able to create internal predecessors in templates. Cross-project predecessors are very powerful but can be time consuming to set up each time a new project is created and can cause user error if a person either forgets to set up the predecessor or does it incorrectly. Why is this feature important to you - Our users work cross-functionally very often and we'd like to be able to link tasks between the different teams without having to manually create the predecessors for every project. How would you like the feature to work - Ideally, we'd be able to set a cross-project predecessor on a task on Project A Template to a task on Project B Template. When a project is created from that template, I'd like to be able to either create a new project for all linked templates OR select an existing project to link. Example 1: Marketing creates a project using Template A that has cross-project predecessors for Template B (which belongs to the Sales team). On the 'Create Project' page, they have the ability to create both projects. Example 2: Quality has already created a project from Template B but didn't sets up any cross-project predecessors since Marketing hadn't yet created a project from Template A. When Marketing goes in to create a project from Template A, they have the ability to select an existing project to link their predecessors to (Quality's Project B).
Currently you can only 'share' tasks and update their access when they're projects. I'd like to be able to do this on templates.
Create the functionality that allows you to manage and use tasks and sets of tasks consistently across the system without excessive manual effort (similar to to how you can edit a single field or a single form that can then be reused across multiple project template) 1.) Create a task library similar to the field library that allows you to manage tasks and choose to reuse them 2.) Allow admins to create custom "Parent/Child task sets" that could be added to a Project template just like you can add in multiple forms in the Project's custom forms section (ex: if you had a Parent Task for "Design Layout" with the 4 child tasks already made, you could just add the Design Layout task section to a new project or template without having to rebuild it) Building and maintaining consistent tasks across project templates is very cumbersome. For example, currently if we need to change the description or duration of the "Design layout" task we have to make the change on every template the task appears on (basically all of them). This is a huge lift.
As an admin, I'm frequently asked to add users to the system. I generally will search for a "like" user already in the system and check to see what groups/teams/access level the current user is assigned to, and set up my new user in a similar way. I have "New from Selected Person" available to me from the People/People tab, but I don't necessarily want to set up a filter to allow me to see only the subset of users I want to see. It would be wonderful for admin users to have the option to create a new user from an existing user's details tab.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.