Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Only titles can be added to smart crops and renditions which can make it hard for consumers to know when to use a rendition and what is it for (e.g. page components, channels, pages) Use-case: If the renditions list is long, it's confusing for users to know what reset to use for a certain use case Current/Experienced Behavior: Descriptions cannot be added to renditions Improved/Expected Behavior: Add the ability to add renditions Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: No granular control of access to a specific fields/group of fields by users/groups (i.e. not all or nothing to edit metadata) Use-case: Currently, we cannot prevent users from updating a certain field only or groups of fields in the properties. It’s either the user gets to edit all or none. This impacts creative rating and commenting. Ideally, we would want to allow asset consumers to be able to post comments or reviews, rate assets but not edit any metadata. Due to this existing restriction, only our group librarians can do that. Current/Experienced Behavior: No flexibility to set-up granular permissions Improved/Expected Behavior: Be able to set-up granular permissions Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Publish to AEM option cannot be hidden Use-case: Even if we don’t have a publish server, we cannot unhide the publish to AEM button Current/Experienced Behavior: Publish to AEM option cannot be hidden Improved/Expected Behavior: Have the ability to hide the publish to AEM button Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Users in our instance would like the ability to display projects that are shared with them in their projects screen or in a dashboard. I'm told by Support there is currently no way to do this. This would give greater visibility since any project that have involvement in would display in the view for them.
Our business users have requested for the ability to set the below option as default while creating a new proof in Workfront:Select "Combine all compatible files into single proof" as true by default.Majority of the users upload multiple files, it would be good to turn this option as true by default.
After connecting LinkedIn Lead Generation forms in LaunchPoint you will start seeing Lead Gen form fills in your Marketo instance. There is information when you double click on the "Filled out LinkedIn Lead Gen Form" activity in the activity log, that shows which Linkedin Campaign, the name of the form, etc drove the form fill. These should be available as tokens!
Ability to have Workfront Auto Save your work when completing a custom form.
When trying to access the summary icon of a proof/document in the project view it is not allowing you to click anything within the summary without un-highlighting the document you are on. Teams within our organization will add updates from this screen, access various versions and even copy the reference # of the proof for documentation. Now we cannot do any of this and have to click into document details to do so which always takes you to another screen away from the overall project. We have notated the workarounds but would like this to be fixed as returning to Classic is not an option. Thank you!
Deactivated users show up in the 'direct reports' section on the User Object.Users have complained this is confusing as they don't expect to see the deactivated (i.e. leavers) on the active form.Can we 'hide' deactivated users from the UI to front-end users?
When a task is in an iteration it assumes the planned completion date is the end of the iteration. When we have a month long iteration we frequently have tasks that will be completed at different points through out the iteration. We would like to be able to modify that start and end dates as long as it is within the iteration dates.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK