#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?

Discussion posts and replies are publicly visible

Parents

0 hiteshd
Certified Lead Developer
over 9 years ago

Hi,

When we split the flow and if the exception timer gets executed for the service call sub process or if it is successful, then a task gets created for the same user instead of him/her continuing on the record journey i.e the context is getting switched.

I also tried using an AND which had two inputs; one a direct connection from previous node and another one from the service sub process as timer exception.
The flow works fine when service is success and UI is displayed but if there is an exception, i am getting an error with no activity class parameter. The activity chain breaks even in this case even though i have an extra input connection to AND shape with activity chain enabled
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 hiteshd
Certified Lead Developer
over 9 years ago

Hi,

When we split the flow and if the exception timer gets executed for the service call sub process or if it is successful, then a task gets created for the same user instead of him/her continuing on the record journey i.e the context is getting switched.

I also tried using an AND which had two inputs; one a direct connection from previous node and another one from the service sub process as timer exception.
The flow works fine when service is success and UI is displayed but if there is an exception, i am getting an error with no activity class parameter. The activity chain breaks even in this case even though i have an extra input connection to AND shape with activity chain enabled
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data