--- sourceDocument: Australia Employee Service Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Employee Service Management ft:clusterId : - emplsm bundleId : - emplsm workflow : - Employee --- # Configure the supporting components for a lifecycle event # Configure the supporting components for a lifecycle event {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Configure the supporting components for a lifecycle event Lifecycle events in ServiceNow consist of multiple activities that require configuration of their underlying components. These components include HR task templates, order guides, catalog items, HR services, owning groups, activity types, and audience records. Properly configuring these elements ensures each activity is assigned to the correct owner and functions as intended within cross-departmental workflows such as HR, IT, or Facilities. Show full answer Show less ## Owning Groups Owning groups determine which team is responsible for a lifecycle event activity. Since lifecycle events often span multiple departments, assigning ownership to the appropriate group is critical. For example, only members of an owning group with the **snhrle.activitywriter** role can create, update, or delete activities within that group's domain. This role-based access maintains control and accountability. ## Activity Types and Configuration Lifecycle event activities can be of several types including approvals, employee tasks, fulfiller activities, notifications, and more. Each type requires different supporting components to be configured. The Enterprise Onboarding and Transitions application allows reuse of existing components such as HR services, task templates, and catalog items. Key activity types and their configuration needs include: * **Approval:** No specific configuration needed. * **Employee task and HR task:** Configure HR task templates. * **Fulfiller activity:** Configure components based on specific fulfiller type, including order guides, catalog items, HR services, incident templates, notifications, or subflows. * **Automated Order Guide:** Create an order guide. * **Catalog item:** Create or edit catalog items. * **HR service:** Configure HR services. * **Incident:** Create incident templates. * **Notification:** Create email templates. * **Flow:** Use or configure subflows; the default subflow supports multiple jobs. * **Content:** Create schedule content templates to deliver mobile, portal, notification, or to-do content. * **Activity container:** No configuration required. ## Audiences Activities can be targeted to specific audiences based on defined criteria to ensure relevance. Audience records specify which employees trigger particular activities during a lifecycle event. This capability enables tailored workflows, such as differentiated onboarding for office-based versus remote employees. If no audience is assigned, the activity applies to all employees by default. Activities that do not meet audience criteria are marked as "Skipped." ## Additional Configuration Tasks * **Configure Owning Groups:** Define or modify the user groups responsible for lifecycle event activities. * **Configure Activity Configurations:** Specify fulfillment processes and closure conditions for lifecycle event activities. * **Configure Schedule Content Templates:** Create or modify templates to deliver content associated with lifecycle event activities across different content channels. By carefully configuring these components, ServiceNow customers can streamline lifecycle event management, ensuring activities are properly owned, targeted, and executed with reusable components, enhancing efficiency and consistency across departments. 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 {#configure-supporting-components-for-lifecycle-event__ul_qlz_kkl_chb} ## Owning groups {#configure-supporting-components-for-lifecycle-event__section_xyr_s4j_chb} 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](https://servicenow-prod.fluidtopics.net/iSVwkLHw8y1gicyYfEd9HQ "Create or modify an owning group to define the user group that owns a lifecycle event activity. Each owning group is responsible for overseeing the activities that fall under their purview.") 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. ## Activity types {#configure-supporting-components-for-lifecycle-event__section_qrc_t4j_chb} 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. {#configure-supporting-components-for-lifecycle-event__table_uqp_53t_vgb__entry__2} | Activity type | Configuration requirements || |-|-|-| | Approval | N/A To learn more about approvals, see [Approvals](https://www.servicenow.com/docs/access?context=r_Approvals&version=australia&pubname=australia-build-workflows&ft:locale=en-US). || | Employee task | [Configure an HR task template](https://servicenow-prod.fluidtopics.net/MgBZDPkwK3sboH7AkoQj7A "Create or modify an HR task template to automatically populate fields on the HR task form when that task is generated. You can configure an HR task template for an HR service or lifecycle event activity.") To learn more about HR templates, see [HR templates](https://servicenow-prod.fluidtopics.net/I1iw4ulRNtCWP5u18BeGuQ "HR templates allow you to automatically populate fields on an HR case or task form. You can configure HR templates for HR services, HR catalog items, HR service activities, and lifecycle event activities."). || | Fulfiller activity | Depending on the fulfiller activity type, configure the appropriate supporting components. Note: 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](https://servicenow-prod.fluidtopics.net/LIAk2tTL9e3uDWN5rDcEHw "Create or modify an activity configuration to define the fulfillment process and conditions for closure for a lifecycle event activity."). || | Fulfiller activity | Automated Order Guide | [Create an order guide](https://www.servicenow.com/docs/access?context=t_CreateAnOrderGuide&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) To learn more about order guides, see [Order guides](https://www.servicenow.com/docs/access?context=c_ServiceCatalogOrderGuides&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). | | Fulfiller activity | Catalog item | [Create or edit a catalog item](https://www.servicenow.com/docs/access?context=t_DefineACatalogItem&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) To learn more about catalog items, see [Service catalog items](https://www.servicenow.com/docs/access?context=c_IntroductionToCatalogItems&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). | | Fulfiller activity | HR service | [Configure an HR service](https://servicenow-prod.fluidtopics.net/A_yw~z4CagxhmAMrED8nhA "Create or modify an HR service to define the request to fulfillment process for that case type. Examples of HR services include benefits enrollment, direct deposit setup, and background check requests by third-party providers.") To learn more about HR services, see [HR services](https://servicenow-prod.fluidtopics.net/ICUvqgZaB1hfeDKX6l7TGA "HR services are the requests and assistance an HR organization provides its employees, such as benefits enrollment, direct deposit setup, and requests for relocation assistance."). | | Fulfiller activity | HR task | [Configure an HR task template](https://servicenow-prod.fluidtopics.net/MgBZDPkwK3sboH7AkoQj7A "Create or modify an HR task template to automatically populate fields on the HR task form when that task is generated. You can configure an HR task template for an HR service or lifecycle event activity.") To learn more about HR templates, see [HR templates](https://servicenow-prod.fluidtopics.net/I1iw4ulRNtCWP5u18BeGuQ "HR templates allow you to automatically populate fields on an HR case or task form. You can configure HR templates for HR services, HR catalog items, HR service activities, and lifecycle event activities."). | | Fulfiller activity | Incident | [Create an incident template](https://www.servicenow.com/docs/access?context=t_CreateAnIncidentTemplate&version=australia&pubname=australia-it-service-management&ft:locale=en-US) To learn more about incident management, see [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&version=australia&pubname=australia-it-service-management&ft:locale=en-US). | | Notification | [Create an email template](https://www.servicenow.com/docs/access?context=t_CreateAnEmailTemplate&version=australia&pubname=australia-platform-administration&ft:locale=en-US) To learn more about notifications, see [Notifications](https://www.servicenow.com/docs/access?context=notifications&version=australia&pubname=australia-platform-administration&ft:locale=en-US). || | Flow | [Create a subflow](https://www.servicenow.com/docs/access?context=create-subflow&version=australia&pubname=australia-build-workflows&ft:locale=en-US) Important: 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](https://servicenow-prod.fluidtopics.net/0vcyUSwl44kZ_qPfRfdipw "Use the Jobs table to create lifecycle event cases where you can specify which job the case pertains to."). To use a different subflow for an activity, additional configuration is required. See the [Implementing multiple subflows in an LE activity \[KB0817520\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0817520) article in the HI knowledge base for more information. To learn more about subflows, see [Subflows](https://www.servicenow.com/docs/access?context=subflows&version=australia&pubname=australia-build-workflows&ft:locale=en-US). || | Content | [Configure a schedule content template for a lifecycle event activity](https://servicenow-prod.fluidtopics.net/Waz6CEGFeyka3pKTXDuc0Q "Create or modify a schedule content template to deliver content as part of a lifecycle event. Each template must be associated with the Schedule Content [sn_cd_content_visibility] table, and you can configure the template for mobile content, portal content, notification content, or to-do content.") To learn more about Content Experiences and Content Publishing, see [Content Publishing](https://servicenow-prod.fluidtopics.net/xWgSi_qWpDKDvznkpG2H6g "Content Publishing offers robust communications creation tools that enable you to create, manage, and publish a variety of content types including portal content, notifications, mobile content, and tasks."). || | Activity container | N/A || [Table 1. Activity types and corresponding configuration requirements] {#configure-supporting-components-for-lifecycle-event__table_uqp_53t_vgb} ## Audiences {#configure-supporting-components-for-lifecycle-event__section_qbw_t4j_chb} 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](https://servicenow-prod.fluidtopics.net/h369zE0BJbEluIUJ4FNKWQ "Target portal content and lifecycle event activities to specified audiences with audience records."). 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. Note: * 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. {#configure-supporting-components-for-lifecycle-event__ul_wtz_yd5_kdc} * **[Configure an owning group for a lifecycle event](https://servicenow-prod.fluidtopics.net/iSVwkLHw8y1gicyYfEd9HQ)** Create or modify an owning group to define the user group that owns a lifecycle event activity. Each owning group is responsible for overseeing the activities that fall under their purview. * **[Configure an activity configuration for a lifecycle event](https://servicenow-prod.fluidtopics.net/LIAk2tTL9e3uDWN5rDcEHw)** Create or modify an activity configuration to define the fulfillment process and conditions for closure for a lifecycle event activity. * **[Configure a schedule content template for a lifecycle event activity](https://servicenow-prod.fluidtopics.net/Waz6CEGFeyka3pKTXDuc0Q)** Create or modify a schedule content template to deliver content as part of a lifecycle event. Each template must be associated with the Schedule Content \[sn_cd_content_visibility\] table, and you can configure the template for mobile content, portal content, notification content, or to-do content. **Previous topic:** [Document the lifecycle event process](https://servicenow-prod.fluidtopics.net/jDkicZxNkOksMoD2FP66cw "Define and document the lifecycle event process. Lifecycle events are generally cross-departmental and require action from different departments.") **Next topic:** [Configure an owning group for a lifecycle event](https://servicenow-prod.fluidtopics.net/iSVwkLHw8y1gicyYfEd9HQ "Create or modify an owning group to define the user group that owns a lifecycle event activity. Each owning group is responsible for overseeing the activities that fall under their purview.")