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
4 replies
Subscribers
10 subscribers
Views
3323 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Related action visibility
tanmayareddyn241
over 8 years ago
Hi,
We are using related action heavily in our application. When a user clicks the related action multiple time repeatedly with less than seconds difference or, if two users click on the related action at the same time, then multiple instance of the process start, we should avoid this, the process should only start once for the person who clicked it the first time.
I tried to solve this in multiple ways:
1. I made a process model report for this process and used query analytics expression to get a count of instances of the process by passing some process variables, now I used this in the exception flow and checked if the count is greater than 1 then end the process. In this case when related action is clicked multiple times all the instances are ending by exception.
2. I made a task report by process model and used query analytics expression to get a count of "assigned" and "accepted" ...
OriginalPostID-240499
Discussion posts and replies are publicly visible
Parents
0
benjamins
over 8 years ago
Its going to be hard to stop the clicking of a related action multiple times quickly. Any checks that you put in place to stop a user from proceeding if a process already exists wouldn't have time to be updated in time. You could have a timer where if the process doesn't end in X minutes/hours/days then the process ends.
If you are having issues with the process report, the other option is to create a database table and log when you enter and leave the process. If any subsequent processes try to come in, you query the database and see if an "active" record exists.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
benjamins
over 8 years ago
Its going to be hard to stop the clicking of a related action multiple times quickly. Any checks that you put in place to stop a user from proceeding if a process already exists wouldn't have time to be updated in time. You could have a timer where if the process doesn't end in X minutes/hours/days then the process ends.
If you are having issues with the process report, the other option is to create a database table and log when you enter and leave the process. If any subsequent processes try to come in, you query the database and see if an "active" record exists.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data