If the Workflow editor is not utilized for a Lifecycle Event, how does the system know when a task or approval should be triggered?

[Kareena]

If the Workflow editor is not utilized for a Lifecycle Event, how does the system know when a task or approval should be triggered?

[Tony Chatfield1]

Hi, could you clarify your question?
The documentation references to 'lifecycle event' point at 'Human Resources Service Management' and

https://docs.servicenow.com/bundle/london-hr-service-delivery/page/product/human-resources/concept/LEWorkflow.html

states that
The HR Activity Set Launcher workflow drives the entire Lifecycle Event process. Associated workflows drive each of the Activity Sets within a Lifecycle Event.

[Kiel Sanders]

The Lifecycle Event framework used within the Enterprise Onboarding and Transitions application allows for easy configuration of conditional, complex processes.  This is all accomplished through configuration that ultimately calls reusable workflows based on the LIfecycle Event framework.  These workflows should not be modified since they are universal to all activities run through the Lifecycle Events framework, not to specific activities and processes.  The admin should only be designing the processes through the standard configuration screens, which reduce/eliminate the need for scripting and managing a large complex workflow.

[Mohamed Ali DAG]

Hello,

the activity set trigger condition determines when it's triggered.