Best Practices for HR Lifecycle Events

[AP2K]

                                                             Best Practices for Lifecycle Events

Below are the best practices for an optimized performance and avoiding runtime issues when creating a lifecycle event.

Note: This isn’t intended to cover every consideration and should not be treated as a sole source for implementation, purposed for general reference.

1. It is NOT recommended to modify a lifecycle event in Production environment if there are ongoing cases without complete round of testing. The changes to the configuration could cause unexpected consequence to the ongoing cases based on where they are within the workflow. If Changes are needed in the production while there are ongoing cases, it’s recommended to take the following approach,

• Cloning Prod and test the existing Lifecycle Event cases to see if they counter any issues
• Cloning the lifecycle event and creating new cases with the new lifecycle event.

Note: This approach will lead to more maintenance overhead.  Also, this will not satisfy the customer use case if the customer wants the new config changes to be applied to the existing cases.

2. It is NOT recommended to modify the subject person on a lifecycle event case if it has already been triggered or create a lifecycle event case without a subject person. This may lead to issues within the workflow.                               
3. If trying to modify the evaluation interval to trigger the activity sets more immediately – it is recommended to use a Conditional Business Rule to immediately trigger an activity set. If this is a situation to encounter,  the Resume case button can help to re-execute the processing and the cancelled activities can be reprocessed.                                 
4. Rescind vs Cancel -  

Rescind should be used when you need to retract an already triggered process. For example, if you have a new hire who has already begun the onboarding process, but has decided not to join the organization, you can rescind their lifecycle event case. This can roll back the process that’s been configured for the lifecycle event to ensure the right activities are triggered.

You can Cancel a case when you don’t need any counter processes to trigger.

5. Purpose of Resume: There are two purposes for Resuming a case:
   1. When a Lifecycle Event activity set it errored or cancelled. You will need to fix the error and then you can resume the case.
      •  "Do not manually error out an activity set to apply changes and resume the workflow”. This will cause dangling workflow context where the old context is still in active state using computational resources.
      •  To Note: You can also reference the work notes in the case to see why a case may have errored.
   2. When you suspend a case and are ready to ‘resume’ it,  procedure can be referenced from Suspend and Resume an HR Case

6. When Specifying the Lifecycle Event type on the HR service being used to trigger the Lifecycle Event. The type should not contain the same Lifecycle Event type being called by an activity in the same Lifecycle Event. This will lead to an endless loop. The lifecycle even type is used to trigger the selective lifecycle event. If trying to create an HR case from a Lifecycle Event, you should use a normal HR Case.