Configure an activity configuration for a lifecycle event
Create or modify an activity configuration to define the fulfillment process and conditions for closure for a lifecycle event activity.
Before you begin
Role required: sn_hr_le.admin or sn_hr_le.activity_set_manager
A key benefit of the Enterprise Onboarding and Transitions application is that you can leverage existing fulfillment processes from different departments to fulfill lifecycle event activities that are assigned to them. For example, you can use a fulfillment process set up by the IT department to fulfill lifecycle event activities assigned to IT. Preconfigured activity types are available to use. You can also configure your own custom activity types.
Procedure
Navigate to All > Lifecycle Events > Administration > Manage Activity Configuration.
Click New or open a record.
Fill in the fields on the form.
| Field | Description | |
|---|---|---|
| Fulfiller activity | Name of the fulfiller activity type. | |
| Configuration type | Configuration type. Select one of the following: | |
| Catalog item | Creates a task, request, or case based on an existing catalog item. In the Catalog field, select a catalog. | |
| Content | ||
| Flow | Creates a flow on the parent lifecycle event case.Note: A flow automates a process with a sequence of reusable actions. See Flow designer for more information. | |
| HR service | Creates a case based on an HR service. | |
| HR task template | Creates a task based on an HR task template. | |
| Order guide | Creates an IT request based on an order guide. In the Catalog field, select a catalog. | |
| Template | Creates a record on a task table that supports templates. | |
| Workflow | Creates a workflow on the parent lifecycle event case. In the following fields, provide the following:- Workflow: A workflow that runs on the parent lifecycle event case. - Workflow required fields: Fields on the activity form that are required to be populated for the workflow. - Workflow optional fields: Fields on the activity form that are optional and populated for the workflow. | |
| Activity closure | Conditions that must be met for the fulfiller activity to close and for the State value to change to Completed.Note: Once all of the activities in an activity set are completed, then the State value of the activity set will change to Finished. | |
| Active | Option to activate the fulfiller activity type for use. | |
| Task table | Table that the fulfiller activity type is associated with. Depending on the Configuration type selected, you can select a table or the field is automatically set to a table. | |
| Badge | Badge that the fulfiller activity type is associated with.Note: Badges display on the portal to indicate to the employee which department is fulfilling that activity. See Configure an HR badge for more information. | |
Click Save.
In the Fulfiller Activity Configuration Mappings section, map one or more fields from the parent lifecycle event case to the child activity.
Click New or open a record.
Fill in the fields on the form.
| Field | Description |
|---|---|
| Activity type configuration | This field is automatically set to the name of the fulfiller activity type. |
| Map from table | HR case table that the parent HR service is associated with.Note: Make sure that this table matches that of the HR case table associated with the parent HR service. |
| Map from field | Field that is being mapped from.Note: Make sure that the data type matches that of the target field. |
| Map to table | This field is automatically set to the table that the fulfiller activity type is associated with. |
| Map to field | Field that is being mapped to.Note: Make sure that the data type matches that of the source field. |
For example, the preconfigured fulfiller activity type for catalog items maps the subject\_person field from the HR Lifecycle Events Case \[sn\_hr\_le\_case\] table to the requested\_for field on the Request \[sc\_request\] table so that the activity form is automatically populated with the name of the user that the catalog item is being requested for.
3. Click **Submit** or **Update**.
4. Repeat the process as needed.
- Click Update.
Parent Topic:Configure the supporting components for a lifecycle event