---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/employee-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Configure an activity configuration for a lifecycle event

# Configure an
activity
configuration for a lifecycle event {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Create or modify an
activity
configuration to define the fulfillment process and conditions for closure
for a lifecycle event activity.

## Antes de Iniciar

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.

## Procedimento

1. Navigate to AllLifecycle EventsAdministrationManage Activity Configuration.
2. Click New or open a record.
3. Fill in the fields on the form.  
   {#configure-lifecycle-event-fulfiller-activity-configuration__table_wr5_stm_tgb__entry__2}

   | Field | Description ||
   |-|-|-|
   | Fulfiller activity | Name of the fulfiller activity type. ||
   | Configuration type | Configuration type. Select one of the following: ||
   | Configuration type | Catalog item | Creates a task, request, or case based on an existing catalog item. In the Catalog field, select a catalog. |
   | Configuration type | Content |   |
   | Configuration type | Flow | Creates a flow on the parent lifecycle event case. Nota: A flow automates a process with a sequence of reusable actions. See [Flow designer](https://www.servicenow.com/docs/access?context=flow-designer&version=australia&pubname=australia-application-development&ft:locale=en-US) for more information. |
   | Configuration type | HR service | Creates a case based on an HR service. |
   | Configuration type | HR task template | Creates a task based on an HR task template. |
   | Configuration type | Order guide | Creates an IT request based on an order guide. In the Catalog field, select a catalog. |
   | Configuration type | Template | Creates a record on a task table that supports templates. |
   | Configuration type | 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. {#configure-lifecycle-event-fulfiller-activity-configuration__ul_jq5_3tf_fhb} |
   | Activity closure | Conditions that must be met for the fulfiller activity to close and for the State value to change to Completed. Nota: 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. Nota: Badges display on the portal to indicate to the employee which department is fulfilling that activity. See [Configure an HR badge](https://www.servicenow.com/docs/Pp3aFe5x~~0DQtkHmgeEcQ "Use Badges to create or modify existing identification badges used to quickly identify the organization of the Assigned to person for the Activity on the HR Ticket page.") for more information. ||
   [Tabela 1. Fulfiller Activity Configuration form]

   {#configure-lifecycle-event-fulfiller-activity-configuration__table_wr5_stm_tgb}
4. Click Save.
5. In the Fulfiller Activity Configuration Mappings section, map one or more fields from the parent lifecycle event case to the child activity.
   1. Click New or open a record.
   2. Fill in the fields on the form.  
      {#configure-lifecycle-event-fulfiller-activity-configuration__table_ejy_qzt_tgb__entry__2}

      | 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. Nota: 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. Nota: 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. Nota: Make sure that the data type matches that of the source field. |
      [Tabela 2. Fulfiller Activity Configuration Mapping table]

      {#configure-lifecycle-event-fulfiller-activity-configuration__table_ejy_qzt_tgb}  
      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.
   {#configure-lifecycle-event-fulfiller-activity-configuration__substeps_cgh_jzt_tgb}
6. Click Update.