Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Challenge with Folder Location Changing when Working on a Review Task in Inbox

Avatar

Avatar
Shape 1
Level 1
alyssapurdy
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Shape 1
View profile

Avatar
Shape 1
Level 1
alyssapurdy
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Shape 1
View profile
alyssapurdy
Level 1

14-09-2021

Request for Feature Enhancement (RFE) Summary: We have an challenge with our implementation of Adobe Assets specifically, that when a user is in the system working in a specific folder of the DAM, and then opens an asset via the inbox, when they close the asset, they are taken back to the folder they were originally in, not to the folder of the asset they were just reviewing. Please see below for the steps to recreate, and what we would like to have happen, and why this is a pain point for my company's implementation. This system design has negatively impacted our company because users are uploading their assets with some frequency in the wrong folder, requiring our admins to help get them moved, or deleting the mis-loaded assets and helping the users re-upload the assets.
Use-case: A user is working in a specific folder in the DAM, navigates to inbox to complete a review task, and is taken back to the original location when the review task is completed, not the the most recent folder location where they were working on the asset in the review task.
Current/Experienced Behavior:

1. A user is working in a folder in the DAM (for example, DAM>content>BusinessA>Images>Birds)
2. The user is notified that they have a review task by email or by seeing a new task showing on the inbox icon in the upper right
3. The goes to the inbox via the Inbox link in the upper right or link from an email, and opens a review task assigned to them
4. The user goes to the Payload, downloads the asset (for review purposes, if an asset is a multi-page PDF or MS file, in order to view and annotate the entire document, it has to be downloaded and uploaded as a new version) from a different folder (e.g. DAM>content>BusinessA>Documents>Brochures), and reviews and annotates it in Adobe Reader or MS application.
5. The user is taken to the folder they were working in in step 1. If the user is not observant, they try to upload the asset they were reviewing in step 4 as a new version, but it's in the Images>Birds folder, not in the Documents>Brochures folder, so it's not versioned there, it's created as a new asset in the folder where it's not intended to be.

We have confirmed this behavior several times and with our ACS DAM Strategist. We even made sure to navigate to the main screen by deleting all of the URL except the home part of the URL (https://author-yyyy-prod2.adobecqms.net/aem/start.html) between steps 1 and 2 above.

Improved/Expected Behavior: 1. A user is working in a folder in the DAM (for example, DAM>content>BusinessA>Images>Birds)
2. The user is notified that they have a review task by email or by seeing a new task showing on the inbox icon in the upper right
3. The goes to the inbox via the Inbox link in the upper right or link from an email, and opens a review task assigned to them
4. The user goes to the Payload, downloads the asset (for review purposes, if an asset is a multi-page PDF or MS file, in order to view and annotate the entire document, it has to be downloaded and uploaded as a new version) from a different folder (e.g. DAM>content>BusinessA>Documents>Brochures), and reviews and annotates it in Adobe Reader or MS application.
5. The user is taken to the folder they were working in in step 4 (e.g. DAM>content>BusinessA>Images>Birds), where they most recently interacted with the system and assets.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5, SP9
Customer-name/Organization name: 3M
Screenshot (if applicable):  
Code package (if applicable):