Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
13 replies
Subscribers
4 subscribers
Views
5031 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Reports
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...
OriginalPostID-194424
Discussion posts and replies are publicly visible
Parents
0
miteshp
over 8 years ago
Startprocesswrite function requires one click from a user to trigger the process. Moreover it seems it doesn't return the process id to be passed to the later rules. I fear this approach doesn't work.
Regarding the memory issue we can archive the process after a very small duration. As every time the user refreshes the page it will create a new process instance and soon as you fetched the instance in query analytics you don't need the process in memory anymore.
Can you please share your thoughts on this.
Thanks!!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
miteshp
over 8 years ago
Startprocesswrite function requires one click from a user to trigger the process. Moreover it seems it doesn't return the process id to be passed to the later rules. I fear this approach doesn't work.
Regarding the memory issue we can archive the process after a very small duration. As every time the user refreshes the page it will create a new process instance and soon as you fetched the instance in query analytics you don't need the process in memory anymore.
Can you please share your thoughts on this.
Thanks!!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data