Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

GregoryCrNew Participant

Allow Individual Approval Decisions on Joint ProofsNew

Description - Our Creative teams have Projects that require multiple versions of a creative to be rendered with slight differences in size, composition, and messaging within the artwork itself.  The general theme still rolls up to the project itself, but the variances require individual Approvals by the legal team to ensure the offerings, messaging, and overall creative association is allowed from a legal standpoint.  The issue we are running into is trying to create a joint proof for all of these similar (But slightly different) creatives, is that we can only approve or reject all at once.  If only one or two of the creatives get rejected, we have to start the whole proof of all creative assets over again with a version 2.Why is this feature important to you - It will save time and effort on our creative team that is currently spread thin from a resource allocation standpoint.How would you like the feature to work - I would like to be able to submit individual approvals on the combined proof.  The combined proof creates a zip file that acts as the actual reviewed file.  With Individual Approvals enabled, an approval on each separate file would create a nonzipped version of the file to be saved in the documents folder (OR a specified "Approved" Folder if possible).  Anything not approved would have to be changed and iterated in the Proof Version 2.  EX: a combined Proof of 5 files has three approved and 2 Rejected.  The 3 approved files are saved as individual files in an "Approved Folder" in the documents section.  The two rejected will be required to be uploaded as a version 2 combined proof. Current Behavior - The combined proof is created as a zip file for the actual review file, but you must approve or reject all files at the same time.  No individual approval is possible.

HuiDeShaoNew Participant

Improvement Request: Please improve the visibility logic of Manage Publication buttonInvestigating

Request for Feature Enhancement (RFE) Summary: Improve the visibility logic of Manage Publication button Use-case: For a node, make the button of Manage Publication visible when the conditions are meeting crx:replicate + workflow users. Current/Experienced Behavior: 1. workflow-users are seeing Manage Publication functionality even if users don't have crx:replicate privilege.2. crx:replicate privilege is making both of Quick Publish and Manage Publication visible for a node. However, Quick Publish is working well, and Manage Publication requires additional permissions from workflow-users. Adding users into workflow-users group will cause another problem where users will see Manage Publication feature for the nodes which don't have crx:replicate privilege. It doesn't make sense because the publish access from workflow-users is extended to the nodes even only having jcr:read privilege. Improved/Expected Behavior: The visibility logic of Manage Publication button should be improved. The expected behavior is to make this button visible when meeting both of conditions: 1. the node is having crx:replicate privilege2. the user is in workflow-users groupNOTE: If Manage Publication can work like Quick Publish (the same visibility logic; no  need to add users into workflow-users), it is great. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud ServiceAEM Release: 2023.10.14029.20231020T111912Z Customer-name/Organization name: Kyndryl Screenshot (if applicable):   Code package (if applicable):