Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Hide parts of process from Workspace tracking

Avatar

Level 1

Currently in Workspace, users have the ability to track the entire progress of their process/request. This is very beneficial in giving the user an idea of where their process is

However, for several use cases, we'd like to prevent the user from seeing certain parts of the process. For instance, if a loan application is submitted, we'd like the user to see that it was submitted properly but not necessarily see the tracking of the process when it goes through the different levels of approval.

Is there any way to prevent tracking of a process after a certain point? Could this be done by triggering a custom event that starts a new process while completing the user's original request?

1 Accepted Solution

Avatar

Correct answer by
Employee

Process instance data is always preserved in the database. This includes user tasks generated by the process instance before and after the task assigned to Workspace user in context. Workspace client initiates a service call to fetch all tasks generated by a process instance when it is selected in Tracking tab. There is no separate service call to fetch tasks owned by the user for a process instance.

To hide tasks not owned by the user, Workspace code needs to be modified to only show those tasks whose owner matches the user in context.

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

Process instance data is always preserved in the database. This includes user tasks generated by the process instance before and after the task assigned to Workspace user in context. Workspace client initiates a service call to fetch all tasks generated by a process instance when it is selected in Tracking tab. There is no separate service call to fetch tasks owned by the user for a process instance.

To hide tasks not owned by the user, Workspace code needs to be modified to only show those tasks whose owner matches the user in context.