Lifecycle Events And Journeys practice questions

sn_hr_le.admin

Configuring Lifecycle Events requires the sn_hr_le.admin role, which grants write access to the Lifecycle Events [sn_hr_le] tables and their associated flows. This role satisfies the stem's requirement precisely, unlike broader HR administration roles that lack the specific scoped privileges needed to create and modify event configurations.

The activity type is not defined

Activity sets only execute activity definitions whose type is registered and configured; an undefined activity type cannot be instantiated, so its trigger condition is never evaluated. Defining the activity type restores execution, addressing the reported failure directly.

Lifecycle Event Audience

Lifecycle Event Audience defines the target population, so restricting it to the Engineering department ensures the activity set triggers only for those employees. This satisfies the department-specific trigger constraint at the event level rather than within individual activities.

sys_user

The 'Employee' audience type resolves against the User [sys_user] table, which stores internal staff records. Referencing sys_user satisfies the stem's requirement because audience membership is evaluated from user records, not from HR profile data held in sn_hr_core_profile, so the activity set targets employees correctly.

Use the 'Reset' button on the case form

The Reset button on the case form clears activity set progress and state, letting you re-run the set on the same case. This satisfies the requirement to retest without recreating the case or its associated records.

HR Case Management > All

HR Case Management > All lists every case record, including Lifecycle Event cases, filtered by the Lifecycle Event case type. This satisfies the requirement to view all active Lifecycle Event cases, since the module exposes the full case table rather than only assigned or open records.

Activity Definition

Skip conditions are configured on the Activity Definition record itself, using the condition builder to evaluate case fields. This lets the activity be bypassed when the specified condition is met, satisfying the requirement that the activity be skipped rather than cancelled or reassigned.

sn_hr_le_activity_set

The sn_hr_le_activity_set table stores the actual activity set instances generated within HR Lifecycle Events, holding each record created from the activity set definition. This satisfies the question by identifying where concrete instances, rather than templates or configuration, reside.

The last mapping applied wins

Field mappings are processed sequentially within the transform map, so when two mappings target the same destination field, the later mapping overwrites the value written by the earlier one. The final field value therefore reflects whichever mapping was applied last in execution order.

Assignment Rule on the task template

Assignment Rules on the task template automatically route each task to the correct group based on conditions such as department, so Legal receives only its own records. This enforces the visibility constraint without manual assignment, satisfying the requirement that the Legal team sees solely their specific tasks.

When using the Lifecycle Event framework

Activity Sets integrate natively with the Lifecycle Event framework, where activities attach to lifecycle events and activity sets orchestrate their sequencing. Flow Designer suits standalone automation instead, so activity sets are chosen when lifecycle events drive the process.

sn_hr_le.admin

The sn_hr_le.admin role grants access to Lifecycle Event cases, which are separate from standard HR cases. Assigning this role satisfies the requirement to view lifecycle event records, as it carries the necessary read access for that case type.

Date

A date trigger schedules an Activity Set to run automatically at a specified future time, satisfying the requirement for time-based initiation without manual intervention. This is distinct from event-driven triggers, which respond to record changes, and from manual invocation, which requires a user to start the set explicitly.

Condition

Valid trigger type.

Manual

Manual triggering lets an agent start an Activity Set directly from the HR case rather than relying on automated conditions. This satisfies scenarios where the set must be launched on demand, complementing the other trigger types such as record creation, field change or scheduled execution.

Activity Definition

An Activity Definition specifies the activity performed within a Lifecycle Event, defining what action or change occurs for the identity. It is a structural component, distinct from the event's scheduling and approval elements, and is required for the event to execute meaningfully.

Activity Set

An Activity Set groups the individual activities comprising a Lifecycle Event, organising the sequence of actions the event performs. It is a structural component, distinct from the Activity Definition, and is required to bundle related activities into a coherent event.

Activity Definition Order

Activity Definition Order controls where an individual activity sits within its parent Activity Set's sequence. It is one of the two settings the stem requires, since changing it repositions that activity relative to the others during execution.

Activity Set Order

Activity Set Order determines the sequence in which the Activity Set itself runs relative to other sets. Alongside Activity Definition Order, it is one of the two settings the stem asks for, governing execution order at the set level.

Can be based on User Criteria

Audience targeting evaluates User Criteria to decide which users receive the activity set, so membership is resolved dynamically from criteria rather than from static lists. This satisfies the requirement that targeting reflects user attributes and conditions, letting one activity set serve different populations without duplication.

Applied at the Activity Set level

Audience targeting is configured on the Activity Set, not on individual activities, so the whole set is filtered for the targeted users before its activities generate. This satisfies the constraint that targeting applies at set level, controlling which users see and receive the contained activities.

HR Case Related List

The HR Case Related List surfaces lifecycle activities linked to a case, letting agents view associated HR Tasks and events directly from the case record. This satisfies the stem's requirement as one valid method for viewing Lifecycle Event activities.

HR Task module

The HR Task module lists HR Tasks generated by Lifecycle Events, giving a consolidated view of outstanding and completed work items. This satisfies the stem's requirement as a valid method for viewing Lifecycle Event activities.

Is the base for all LE cases

The Lifecycle Event table stores every lifecycle event record and acts as the parent from which all LE case types inherit, so it forms the base for all LE cases. This satisfies the question's requirement that the statement be true of that table.

Extends sn_hr_core_case

The Lifecycle Event table extends sn_hr_core_case, inheriting the HR case framework's fields, states and workflows. This satisfies the stem's requirement that lifecycle events behave as HR cases, enabling case-type routing, SLA processing and agent assignment without duplicating base-case logic.

Execution order

Execution order determines when an activity runs relative to its siblings within the set, directly sequencing the timeline. Changing it shifts the activity earlier or later, making it one of the three factors governing activity timing.

Activity Set trigger condition

The activity set's trigger condition determines whether and when the containing set launches, which in turn controls when its member activities become eligible to run. Until the condition is met, dependent activities remain pending, directly affecting their timing.

Wait for completion

Waiting for completion is a timing factor because the activity cannot start until its predecessor finishes, so the dependency directly shifts the start date. This constraint, rather than a fixed schedule, determines when the activity becomes eligible to run.

Date

A Date trigger fires an Activity Set at a defined point relative to a case date field, such as a target completion or onboarding date. It is one of the supported trigger types, satisfying the scheduling-based activation requirement.

Manual

Manual triggers let an agent launch an Activity Set on demand from the ServiceNow interface, satisfying the requirement that a valid trigger type exists without relying on scheduled or record-based automation. This suits ad-hoc fulfilment work where timing is unpredictable and no system event initiates the flow.

Condition

Condition triggers evaluate a record against defined criteria and fire the Activity Set automatically when those criteria are met, without manual intervention or a scheduled cadence. This satisfies the stem's requirement for a valid trigger type, since ServiceNow Activity Sets support condition-based activation alongside record-creation and scheduled triggers.