Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Access to process attachments from another user

Avatar

Level 2

We have a process and involved users can add attachments in it. Sometimes we need to grant access (possibility to view) to these attachments for another users which are not included to that process. Are there any ways to do it? We looked for such mechanisms in ACL but all its options aren't good enough - you can only view attachments if you claim the task or if owner of the task send it to you for consultation. But we need a way to do it without any movements from the task owner, may be even without his knowledge. Task can be not completed in that moment.

Also description of all ways that can be used to access to process attachments is highly required.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Export them out to a separate database after each user step. Write an interface to retrieve them from that database and return. The interface could simply be a short lived process accessed through REST: http://example.com/services/rest/Application/Process?input=value

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Export them out to a separate database after each user step. Write an interface to retrieve them from that database and return. The interface could simply be a short lived process accessed through REST: http://example.com/services/rest/Application/Process?input=value

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----