Configure a lifecycle event activity
Create or modify a lifecycle event activity. Lifecycle Events activities can be approvals, employee tasks, fulfiller activities, notifications, flows, content, or activity containers.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Each activity must be associated with an owning group. If the activity has a targeted audience, you can use audience records to define the conditions or criteria that the subject person of a lifecycle event case must meet for the activity to trigger on their behalf. Each activity is associated with a single activity set.
Prozedur
For an approval
Configure a lifecycle event activity that is an approval. Approvals create a to-do for the specified approvers to approve or reject.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Prozedur
For an employee task
Configure a lifecycle event activity that is a task for an employee. Employee tasks are assigned to the subject person of the lifecycle event case.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Prozedur
For a fulfiller activity
Configure a lifecycle event activity that is for a fulfiller. Fulfiller activities are assigned to an agent or fulfiller in a department such as HR, IT, or Facilities.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Prozedur
For a notification
Configure a lifecycle event activity that is a notification. Notifications automate the sending of an email to the specified recipients.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Prozedur
Flow activity parameters
Use flow activity parameters on a lifecycle event activity to automatically populate values from a subflow within an activity.
You can configure subflows for a lifecycle event and pass the values for the input parameters of the subflow within the activity.
Having the ability to call any subflow from a lifecycle event activity provides you with a low code or no code configuration.
Calling subflows from a lifecycle event activity provides an enterprise-wide workflow you can use to interact with third-party applications at a specific point in a lifecycle event.
For more information, see Flows.
Use cases
| Subflow | Parameters |
|---|---|
| Terminate employee in Workday. |
|
| Subflow | Parameters |
|---|---|
| Mark employee as a no show in Workday. (Employee accepted an offer of employment, but at some point decided to back out of agreement.) |
|
| Subflow | Parameters |
|---|---|
| Switch primary job |
|
For more information, see Subflows.
Map activity fields and input parameters
You can use fields from a table to map your activity field to an input parameter.
Or, you can map activity fields to an input parameter using a custom script.
For a flow
Configure a lifecycle event activity that uses a subflow.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Prozedur
Configure activity field mapping
Use activity field mappings to map information from a field on a table, custom text, or a custom script to a flow input from a subflow.
Vorbereitungen
Warum und wann dieser Vorgang ausgeführt wird
Prozedur
For content
Configure a lifecycle event activity to schedule content. This activity type enables you to deliver relevant and tailored content to employees as part of the lifecycle event. For example, you can push company-related information or a first day at work banner to new hires as part of their onboarding.
Vorbereitungen
Role required: sn_cd.content_manager, sn_hr_le.activity_writer, and membership in the owning group that owns the activity.
Prozedur
For an activity container
Configure a lifecycle event activity that is a container for a group of activities. This activity type enables you to manage the dependencies of activities within an activity set. You can use activity containers to order activities, in parallel or sequence, as well as configure multiple activity containers within an activity set.
Vorbereitungen
Role required: sn_hr_le.activity_writer and membership in the owning group that owns the activity.
Prozedur
For a pulse survey
Configure a lifecycle event activity that is a pulse survey. Pulse surveys capture employee feedback.
Vorbereitungen
Role required:
Prozedur
Moving an activity within an activity set
There are multiple ways you can move an activity within an activity set.
- The drag-and-drop feature enables you to move an activity within an activity set or to another activity set.
- Use the reorder pop-up on an activity and select where you want the activity to reside.
- Edit the activity and select and save a new activity set or enter a new display order number to reorder an activity within an activity set.
- You cannot reorder a request activity.Hinweis:Requests have a grey background around the request card for easier identification.
- You cannot move an activity above a request activity.
- If you use the
to move an activity to another activity set, by default it moves it to the top position of the activity set below any request activities.
Reorder a life cycle event activity
You can reorder an activity within an activity set for a lifecycle event using different methods.
Vorbereitungen
Role required: admin
Prozedur
Triggering an activity from upstream activities
For a lifecycle event case, you can trigger or create an activity from an activity that is in another activity set.
Activities in later activity sets can be created based on survey responses in earlier activity sets and for users other than the person the case was created for (subject person).
You can create an activity that has a task type of Collect Employee Input and based on the results, another activity is created. In this example, the activity that has a task type of Collect Employee Input is the upstream activity. The activity that is created from this is the downstream activity.
- Upstream survey creates downstream survey
- For example, a lifecycle event activity can task a manager with taking a survey.
- The survey asks a hiring manager if their new employees require special equipment.
- The hiring manager can answer the survey indicating if the new hires require special equipment.
- If the answer is yes, a new survey can be created in a downstream activity set that asks what specific safety equipment are required.
- Anyone that has access to the original lifecycle event case can answer the second survey requesting specific safety equipment for the new hires.
- To configure this activity, associate an HR template that has an HR task type of Collect Employee Input. For more information, see Configure an HR task template and Adding an HR task to an HR case.
- System property
- The sn_hr_core.create_new_survey_instances system property determines if new survey instances are created with each survey task even when an existing survey instance for the same user exists.