Configure the supporting components for a lifecycle event

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 3 min. de leitura

    • Configure the supporting components for a lifecycle event. Lifecycle events are a collection of activities. For each activity, you must identify and configure the underlying components that support it, such as HR task templates, order guides, catalog items, and HR services. You must also identify and configure the relevant owning groups, activity types, and audience records.

    • Owning groups
    • Activity types
    • Audiences

    Owning groups

    Owning groups control who owns a lifecycle event activity. Because lifecycle events are generally cross-departmental, it's critical that ownership of each activity is assigned to the appropriate group, such as for HR, IT, or Facilities. Each owning group is responsible for overseeing the activities that fall under their purview. See Configure an owning group for a lifecycle event for more information.

    To create, update, or delete an activity, you must be both a member of the associated owning group and have the sn_hr_le.activity_writer role. For example, only members of the HR activity writers owning group with the sn_hr_le.activity_writer role can configure an HR activity.

    Different owning groups and the lifecycle event activities they are responsible for.

    Activity types

    Lifecycle event activities can be approvals, employee activities, fulfiller activities, notifications, and more. Depending on the activity type, you must configure the appropriate components that underlie it.

    A key benefit of the Enterprise Onboarding and Transitions application is that you can reuse existing components and processes. These components and processes include existing HR services, HR task templates, or catalog items. For each activity, determine whether there’s an existing component that you can use or if you must configure a new one.

    Tabela 1. Activity types and corresponding configuration requirements
    Activity type Configuration requirements
    Approval

    N/A

    To learn more about approvals, see Approvals.
    Employee task Configure an HR task template

    To learn more about HR templates, see HR templates.
    Fulfiller activity Depending on the fulfiller activity type, configure the appropriate supporting components.
    Nota:
    The following fulfiller activity types are preconfigured with the Enterprise Onboarding and Transitions application. To configure additional types, see Configure an activity configuration for a lifecycle event.
    Automated Order Guide Create an order guide

    To learn more about order guides, see Order guides.
    Catalog item Create or edit a catalog item

    To learn more about catalog items, see Service catalog items.
    HR service Configure an HR service

    To learn more about HR services, see HR services.
    HR task Configure an HR task template

    To learn more about HR templates, see HR templates.
    Incident Create an incident template

    To learn more about incident management, see Incident Management.
    Notification Create an email template

    To learn more about notifications, see Notifications.
    Flow Create a subflow
    Importante:
    The only subflow available for use by default is the Switch primary job subflow. This subflow is used to support multiple jobs in a lifecycle event.

    To use a different subflow for an activity, additional configuration is required. See the Implementing multiple subflows in an LE activity [KB0817520] article in the HI knowledge base for more information.

    To learn more about subflows, see Subflows.
    Content Configure a schedule content template for a lifecycle event activity

    To learn more about Content Experiences and Content Publishing, see Content Publishing.
    Activity container N/A

    Audiences

    Not all lifecycle event activities are required for all employees. Some activities are intended for a target audience. You can use audience records to define the criteria that the subject person of a lifecycle event case must meet for the activity to trigger on their behalf. For more information, see Audiences.

    Clearly defined audience criteria enable you to create targeted workflows for different audience types. For example, you can create a tailored onboarding experience for newly hired employees depending on whether the employee is office-based or remote.

    Nota:
    • If an activity isn't associated with an audience record, then the activity triggers for all employees.
    • If a subject person doesn't meet the audience criteria defined for an activity set during the evaluation process, the State field in the corresponding activity set is set to Skipped.

    GIF that demonstrates how you can use audience records to created targeted lifecycle event experiences.