Best Practices for Improved Performance in Lifecycle Events - HRSD

[AP2K]

                                   Best Practices for Improved Performance in Lifecycle Events

The more complex the underlying workflow, the slower the load times of activities for employees and managers in the Lifecycle Event Request page(hrm_ticket_page).

• Note: This document isn’t intended for the new Journey Designer User Interface and only refers to the Request Page(hrm_ticket_page).

Maximum no. of activities in an activity set:

 It is recommended to have 10 activities or less triggering at a time, irrespective of being part of an activity set or an activity container. The more you trigger at the same time, the worse the performance it would be. You can have this exceeded for non-complex activities.

The following factors can further performance implications:

• An employee completing at task that triggers a HR service, the more complex the request, the slower the performance.
• Triggering multiple activity sets at one time (more the background call, slower the performance)

Performance Metrics:

Here by referencing this to the following User Interface only,

• Request page (specifically for lifecycle events)
• Note: The request UI has slower performance than the new journey page available with Journey designer.

Performance Metrics for a Lifecycle case on Requests Page:

The performance expectations related to Lifecycle events and its improvements were delivered as part of the updates in the release version since Employee Center Core 27.1.1 store release.

Note: One of the best ways to troubleshoot any Lifecycle Event issue is to check the Lifecycle Event workflow execution and the activity set execution contexts. Also, each of the activity sets has an associated activity set context which displays all the workflow history – this gives you the details of what’s running with the Lifecycle Event workflow. For more trouble shooting FAQs, refer to the useful resources below.

Useful Resources:

• Troubleshooting best practice FAQs
• Migrating Lifecycle Events experience to leverage the new journey designer