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
8 replies
Subscribers
6 subscribers
Views
3085 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
#Use Of Timer on Sub Process or in Process Flow Hi All, We have
saravanann
over 9 years ago
#Use Of Timer on Sub Process or in Process Flow
Hi All,
We have a requirement wherein we invoke a service to get some data and if the service gets timed out or takes more than 30 seconds, we should skip the service calling sub process and continue the process journey.
To achieve this we used the time/rule option on the sub process exception tab and set it to 30 seconds. Upon running the flow, we found that even though the node is skipped after 30 secs, a task gets created in task list for the same user instead of continuing the journey on the record. I believe the activity chaining breaks in this case and the same is causing the issue.
We are invoking a related action to kick start the main process which in turn calls the service sub process.
Can you please suggest how can we avoid this task creation in task list and let the user continue the journey on the record itself?
OriginalPostID-207734
OriginalPostID-207734
Discussion posts and replies are publicly visible
Parents
0
kumaraveln
over 9 years ago
As Eduardo mentioned you can split the flow (using AND), invoke the service in parallel and make it wait for 30 secs before skipping. Mean time you take the user to the next screen displaying a message to wait for 30 secs to get recent values from the service call. They can perform other operations in the screen. Either user have to refresh the task manually by saving the form and reopening from TASKS or you can provide a refresh button or link (Which will also SAVE users work). And after 30 secs if the service call times out you can update the same message variable saying the node has been skipped.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
kumaraveln
over 9 years ago
As Eduardo mentioned you can split the flow (using AND), invoke the service in parallel and make it wait for 30 secs before skipping. Mean time you take the user to the next screen displaying a message to wait for 30 secs to get recent values from the service call. They can perform other operations in the screen. Either user have to refresh the task manually by saving the form and reopening from TASKS or you can provide a refresh button or link (Which will also SAVE users work). And after 30 secs if the service call times out you can update the same message variable saying the node has been skipped.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data