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
6 replies
Subscribers
6 subscribers
Views
2836 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi, I have a requirement where a User Input Task (UIT) has a timer exceptio
sainadhn
over 9 years ago
Hi,
I have a requirement where a User Input Task (UIT) has a timer exception. UIT is triggered by timer event i.e dateTime Array. For each value in DateTime array it will trigger a task. All tasks have same deadline after which they move forward (through mentioned timer exception).
Say for example 3 UIT's are triggered one after another and they waited till common deadline and then they took the exception path and reached next node which is a sub process now it is running 3 instances at a time.
but my use case requires this sub process to run these multiple instances one after another. But they are running concurrently which is not a desired behavior that i am looking for. Is there any option / workaround available while configuring nodes to make them wait till the active node completes and then start a new instance?.
OriginalPostID-165682
OriginalPostID-165682
Discussion posts and replies are publicly visible
0
TJ
A Score Level 2
over 9 years ago
Use AND node to wait till all the UITs cross deadline and go there. Use looping flow on sub-process and make them synchronous. This way you can run as many instances of sub-process as desired and each will start running after another.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 9 years ago
see the attached process design snippet, You can append the 3 UIT's data into one CDT type (multiple) & using a status flag can create sub process instance one after other on the completion of previous subprocess task. I have attached sample Application also let me know if you need more details on it.
POC.zip
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sainadhn
over 9 years ago
Thanks for sharing your views, but my use case is little different.All tasks have same dead line means they are configured to a particular date and Time value like evening 5 PM. In the POC provided say if all the three event triggered at same time, I mean configure the timer events to now() and keep the same exception. So all the 3 instances will be active at same time and will wait for 1 minute i.e. at same time they will take the exception path.Now i need to make the sub process run one after another for arrived flows. I attached my sample use case picture and little explanation about my use case in the attachment.
I don't have multiple flows to use AND gate, in my use case AND gate will work as normal script task. so i cannot go for it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 9 years ago
So as per my understanding we have race conditions only on exception flow and user is not using "Save Changes" tempo out of box option.In that
case, we can start exception flow from timer event & not from task exception event.
Kindly find attached update process flow model.
POC2.zip
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sagarl511
A Score Level 2
over 9 years ago
Rule events can also be used. Create a boolean array. Set its value to true at particular index on exception path. Create a rule event in process model to check if all values are true and let the flow begin. Also set step numbers or sequence order of subprocesses to be started. Match it to boolean array indices.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sainadhn
over 9 years ago
Thanks sagar, vahluwalia. The suggested approaches works for me.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel