Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

William--
William--New Participant

Template Placeholder Roles based on User/Project RelationshipsNew

DescriptionIn a project template, I want to assign certain tasks to users based on their relationship to the project, as opposed to their Job Role. E.g., I want to assign the task "Project Setup" to whichever user is the Project Owner. Or, assign "Set Project Priority" to whichever user is the Program Owner in which the project resides. Or, assign "Provide Follow Up Feedback" to whomever was the Converted Request Originator. In all these examples, there often isn't a placeholder role that can be assigned to the template task because the users referenced by these terms don't typically share the same set of job roles. Why is this feature important to youThis feature would reduce the burden of project administration and user error, since there is currently no mechanism to make these types of assignments in bulk.   How would you like the feature to workWhen a template is applied to a project, Workfront would replace these placeholder roles in the template tasks with whichever user is referenced (Project Owner, Project Sponsor, Program Owner, Portfolio Owner, Converted Request Originator, Project Owner Manager, Converted Request Originator Manager, etc.)  Current Behaviour No such capability exists currently. An admin would have to add every one of these roles to every user profile, and the PM would still need go through the multi-step process of making bulk assignments.We do have a Fusion scenario in place to do this, but such a feature would be useful to all Workfront customers and reduce our dependence on Fusion scenarios to make assignments that should be possible without requiring an automation platform.

CuriousUser1922New Participant

Adobe Data Warehouse FTP "User Credential Security" and "Fixed Location Dropdown + Secure File Sharing ONLY Option"New

Description - For enterprise companies that have thousands of users accessing Adobe Data Warehouse: There is no visibility into where users send their files from an admin perspective, without initiating a report request from Adobe. (No self-service governance)There is no way of knowing if the reports being sent are done so using secure methods. Nor is there a way of displaying SFTP options ONLY.There is no control for where files can be transferred.Why is this feature important to you - With no alert system, control, or visibility into who is sending what information and where, we leave ourselves extremely vulnerable to malicious intent or interception from external hackers. The Adobe products pride themselves in encouraging self-service models but they lack appropriate governance capabilities to ensure everyone can operate with a safety net.  How would you like the feature to work - At a minimum, we would like admins to have the ability to control what locations are available to ADW users AND the ability to allow SFTP methods only, regardless of the location's ability to receive both FTP and SFTP.  Current Behaviour - Everyone can send whatever data is available in Adobe Data Warehouse (based on the data they have access to) to whatever location they want without interception from the company on whether or not the contents and location are safe. This extreme flexibility is not scalable safely for large companies. 

---achimEmployee

AEM Assets: Apply Metadata Profile to Assets on MoveInvestigating

Request for Feature Enhancement (RFE) Summary: Apply Metadata Profile properties to assets when they are moved into a folder, that is associated with that property.  Use-cases: 1. User uploads an asset to a folder "upload" for pre-screening. From here, the assets are moved to their final destination to complete the meta data. 2. User accidentally uploads asset to the wrong folder and successively corrects by moving into the proper folder.  Current/Experienced Behavior: Currently, metadata Profiles are applied only when assets are uploaded to a folder. They are not applied, when an already uploaded asset is moved from another folder into the marked folder.   Improved/Expected Behavior: Issue: The above is somewhat unintuitive: User apply metadata profiles to ensure, that all assets in that folder have the same set of defaults. There is no reason not to apply the profile on move. I.e. we end up with a mix of assets in a folder. Some assets have the profile applied some have not.  Expected Behavior:  Apply Metadata Profile properties to assets when they are moved into a folder, that is associated with that property.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS  2023.9.13665.20230927T063259Z Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):