Journey Accelerator task template fields
Summarize
Summary of Journey Accelerator task template fields
The Journey Accelerator task template fields enable ServiceNow customers to create and configure task templates within the Journey Accelerator application. These templates standardize task creation, assignment, scheduling, and tracking, enhancing the management of journey plans and activities.
Show less
Key Features
- Name: Assign a descriptive name for each task activity to clearly identify its purpose.
- Table Selection: Choose the Journey Accelerator Task [snjatask] table to access and manage task template fields.
- Template Fields: Define fields that appear only when a table is selected and are tracked in the Journey Accelerator Task table.
- Mandatory: Specify whether the task is required (true) or optional (false) within the journey plan.
- Type: Select between Regular (standard to-do tasks) and Calendar (schedulable tasks linked to Microsoft Office 365 calendar events).
- Active: Enable the task template for use; only active templates are available for managers.
- Task Descriptions: Provide a brief description for quick reference and a detailed description for clarity on task requirements.
- Parent Plan Table: Associate tasks with the Journey Accelerator Plan [snjaplan] table to link tasks to higher-level plans.
- Assign to Source: Assign tasks to users such as Employee, Manager, or Mentor. Initially, the first mentor is assigned, but managers can reassign tasks post plan creation.
- Relative Due Date Trigger: Configure when tasks are assigned based on the plan’s publish date using conditions like “Start on.” Only the “Start on” condition is recommended for use.
- Date Offset Type: Determine if the task triggers “On” or “After” a certain date, with “After” being the recommended default.
- Number of Offset Days: Set the number of days (hours should remain at zero) after the trigger date when the task assignment occurs—for example, 5 days after the plan publish date.
Practical Application for ServiceNow Customers
By leveraging these task template fields, customers can systematically create tasks that align with journey plans, automate task assignment timing, and ensure clarity on task requirements and responsibilities. The integration with Microsoft Office 365 calendar allows for synchronized scheduling. Active management of task templates ensures that only valid, current templates are available, enhancing workflow efficiency. Understanding and using the relative due date triggers and offset parameters helps automate task scheduling relative to plan milestones, reducing manual oversight and improving timely execution.
To make a task template, fill in the Journey Accelerator task template fields.
| Field | Description |
|---|---|
| Name | Descriptive name for the activity that is associated with the task. |
| Table | Table that is used to track tasks and fields. Select the Journey Accelerator Task [sn_ja_task] table to enable access to the template fields. |
| Template |
Template fields that appear only when a table is selected. Template fields are tracked in the Journey Accelerator Task [sn_ja_task] table. The following settings apply to the overall properties of the task:
|
| Active | Option that enables the task template when selected. Only active tasks are available for managers to use. |
| Task short description | Brief description of the task. This text appears to users from the Journey Accelerator plan. This field appears in the Short description field when you are managing tasks in stages. |
| Task description | Detailed description of the task. |
| Parent plan table | Higher-level table that associates an entry in the Journey Accelerator Task [sn_ja_task] with the table that tracks plans, Journey Accelerator Plan [sn_ja_plan]. Selecting the Journey Accelerator enables access to the plan-related fields. |
| Assign to source | User who is assigned the task:
|
| Relative due date trigger | Condition that is used to trigger when a task is assigned based on the publish date of the plan. This condition is evaluated with Date offset type and Date offset type.
Note: Only use the Start on condition. Start on is selected by default. |
| Date offset type | Condition that is used to trigger when a task is assigned. This condition is evaluated with Relative due date trigger and Number of offset days.
Note: The After condition is the default selection. We recommend that you use only the After condition. |
| Number of offset days | Condition that is used to trigger when a task is assigned. This condition is evaluated with Relative due date trigger and Date offset type.
Note: Only specify days, and keep hours set at 0 (zero). For example: If the |