Lifecycle event issue

[_Gaurav]

Hi Folks!

While setting up a lifecycle event, I ran into a problem where, depending on the conditions, I had to create more than 150 activities/tasks for my LE. This required me to create more than 50 activity sets, which takes time to submit the case and sometimes prevents the LE from being attached to the case.
Even with the activity container it didn't function well.

If someone faced the same issue or has any suggestions on how to overcome the issue, please share.

Thanks in advance!

[Sandeep Rajput]

@_Gaurav In your lifecycle event, the number of activities and activity sets are certainly on the higher set. Please be informed that each of these activities and activity sets will have separate workflows attached to them and image having 200+ workflow contexts being triggered per case on your instance. The overall performance of your case would significantly go down. As you already mentioned in worst case the LE would not get attached to the case.

I recommend restructuring/refactoring your lifecycle events to multiple lifecycle events and only keep those activities/activity sets which are  relevant.

We also faced similar situation in the past where we tried to use a single lifecycle event to support onboarding process for more than 10 countries, needless to say the LE was a mess we encountered several performance related issues. Later we decided to create separate lifecycle events to support each country and now our LEs are more simple and performant than what we used to have earlier.

Hope this helps.

[_Gaurav]

@Sandeep Rajput Thanks for such a good explanation.
In my scenario, even if I separate the LE, I must create 5 different services, 5 record producers, and 5 lifecycle events. However, in all these processes most of the tasks are common.

[Sandeep Rajput]

@_Gaurav If the activities and tasks are common then it will not make sense to replicate them across the multiple lifecycle event.

In this case you have following options.

1. Create Flow type activities: You can generate the HR tasks via a flow and the flow can be triggered via an activity in the lifecycle event. The flow used here will generate a group of tasks which you might be triggering via different activities in your lifecycle event

2. HR Service Activity: Second option would be to create a fulfiller activity of type HR Service.

This HR Service will have a fulfillment of type Service Activities 

You can trigger multiple tasks via Service Activities associated with an HR Service.

Hope this helps.

[_Gaurav]

@Sandeep Rajput 
HR service won't help me in this case neither flow because then the visibility of the tasks won't be cleared to the client.
Please let me know the understanding.