|
**Journey configuration name**
|
Provide a name for the Journey that helps managers identify the intended use case so they can customize the Journey with activity sets or stages.
|
|
**Type**
|
A Journey type is a category used to identify the intention of the journey, such as onboarding, leave of absence, or career growth.**Note:** This value is used for reporting and categorization. If using Journey Accelerator, keeping the **Plan type** and the **Journey type** consistent is helpful.
|
|
**Journey source**
|
- **Lifecycle Events**: Use Lifecycle Events to facilitate cross-department tasks, such as approvals.
- **Journey Accelerator**: Use Journey Accelerator modules to create templates for different audiences, such as a department-specific onboarding process.
- **Lifecycle Events and Journey Accelerator**: The Journey will contain both a Lifecycle Event and Journey Accelerator plan.
|
|
**Lifecycle event type**
|
Select a lifecycle event for the Journey configuration. Lifecycle Events are created and managed from the **Manage Lifecycle Event** form. Go to **All** > **Lifecycle Events** > **Manage Lifecycle Event** to add or manage lifecycle events. See, [Lifecycle Events]().
|
|
**Journey accelerator plan type**
|
Journey Accelerator plan types are configured by an administrator. Plan types include plans for transitions such as onboarding, offboarding, or promotions.
|
|
**Active**
|
Indicates whether the Journey configuration is available \(active\) for use in Journey designer.
|
|
**Update on manager change**
|
Option to enable a change in manager. Selecting this option will update the journey configuration and make it eligible for a manager change.
The following fields of tasks are updated on reassignment:
- HR Case: Subject person, Opened for
- HR Task: Assigned to
- Incident: Caller
- JA Task: Assigned to
- Approvals: Assigned to
- Requests: Requested for
**Note:** For this functionality to work, ensure that you copy the flow **Manager Change - Journeys** and activate it. To activate a flow, see [Activate a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/flow-activate.md). Also note that email notifications are sent to the old manager, new manager, assigned agent, and the user updating the manager in `sys_user`.
|
|
**Journey mobile image**
|
The image that appears at the top of the Journey when viewed in the mobile app. See, [Journeys on Now Mobile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/journey-designer/journeys-mobile-now.md).
|
|
**Can be used as a template**
|
Indicates whether the Journey configuration can be triggered from the **Create journey** widget.
|