194424 - no subject - I am creating a Tempo Report for listing

miteshp over 8 years ago

I am creating a Tempo Report for listing all the active tasks in appian from all processes along with the corresponding owners for those tasks.

It seems when we view the report using System Administrator's account, Appian lists all the tasks from all processes. But when we view as a basic user, it lists only the tasks from process models you are privileged to. A shorter list. Which is as per Process Model Security (Viewer Role) theory.

The requirement is to have this report for management where users are not authorised to perform any actions/related actions but they should be able to see what's happening and what tasks are still pending and with whom.

It seems if we associate a group as viewer to a process model they will be able to see the reports on those models but will also get the access to initiate the related action.

Can we create a custom role in Appian for process model security with access to view reports? Is there any other way to achieve th...

Discussion posts and replies are publicly visible

Parents

0 Chris over 8 years ago

We've accomplished similar use cases by either granting view access to the model and handling quick tasks / related actions permissions accordingly (blocking said group), or creating a process that runs periodically loading task data into CDT, writes to the data store, then is visible in a Tempo/SAIL report via query rule. At this time you can also put a little note on the form that the data is updated periodically (can show last updated datetime), while also giving them a 'Refresh' button that utilizes the start process writer to refresh the data, calling & chaining through the same update process (so data is automatically refreshed on the form once chaining completes).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 8 years ago

We've accomplished similar use cases by either granting view access to the model and handling quick tasks / related actions permissions accordingly (blocking said group), or creating a process that runs periodically loading task data into CDT, writes to the data store, then is visible in a Tempo/SAIL report via query rule. At this time you can also put a little note on the form that the data is updated periodically (can show last updated datetime), while also giving them a 'Refresh' button that utilizes the start process writer to refresh the data, calling & chaining through the same update process (so data is automatically refreshed on the form once chaining completes).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data