Considerations When Using Enterprise Onboarding Journey Category
An Enterprise Onboarding journey template is a specific journey that you create to onboard new hires either before, on, or after their joining date.
It contains a master journey and step journeys. An Enterprise Onboarding step includes tasks that need to be performed in each phase of the onboarding process. The master journey links steps in the onboarding process. You need to configure at least one step that needs to be linked to this master journey. There's no maximum limit for the number of journey steps that can be created. You can specify the sequence of the steps. For example, in your master journey, you can configure a step titled Your First Day to include onboarding tasks that the employee needs to complete on their joining date. You can add one or more tasks that a new hire needs to perform before their first day, such as providing identity proofs.
- There can be only one active instance of the journey of this category. However, let's say you specify the Move to HR and Add Pending Worker actions in enterprise onboarding journeys. In this case, the Move to HR action internally calls the Add Pending Worker action so that both the journeys can get assigned at the same time. For the worker, the Journeys page displays the journey assigned most recently. Therefore, it's recommended not to use both these actions together.
- If your enterprise onboarding journey has multiple steps, then the action you specify in the master template and first step template must be the same.
- When you manually assign a journey, eligibility profiles aren't evaluated for the enterprise onboarding master journey. However, eligibility profiles are evaluated for enterprise onboarding step journey and journey tasks.
- In a rehire process, if the rehired employee already has an in-progress enterprise onboarding category journey from a previous employment, then another instance of an enterprise onboarding journey won't be assigned to them.
- Only one action can be configured in the master enterprise onboarding category journey.
- You can't assign a step journey by itself. You need to assign the entire Enterprise Onboarding category journey.
- You can't delete only the step journey. When you delete an assigned journey, it will delete all the tasks of all the step journeys in that journey.
- You can’t configure a task with a preceding task from another enterprise onboarding step template.
- You can’t use task groups.
- You can't create recurring schedules.
- Notifications aren't sent when an enterprise onboarding step journey is activated.
- You can't configure a reminder alert template for a task in a step journey.
- You can configure nudges only for the Enterprise Onboarding journey, and not for step journeys.
- When you force close an assigned journey, it closes all the tasks of all the step journeys in that journey. It displays the tasks in the step journey only when the criteria is met.
- In Journeys, tasks in all step journeys are displayed even when the step isn't yet active. However, these tasks remain disabled until activated. Whereas in enterprise onboarding, only the step name is visible. The tasks within the step display only when the step becomes active.
- In Journeys, if an enterprise onboarding journey is split into individual journeys, the line manager and HR can see all individual journeys as deferred journeys on the Assigned Journeys tab. However, the employee can see the journey only when it becomes active.
Therefore it’s recommended to use other categories when configuring journeys for these reasons:
- You can associate multiple actions based on which the journey is assigned.
- You can assign the same journey multiple times.
- The configuration is simple and consistent.