Journey Accelerator task template fields

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    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 Journey Accelerator task template fields

    Journey Accelerator task templates in ServiceNow define the structure and properties of tasks within a journey plan. These templates enable consistent task creation, assignment, scheduling, and tracking to support the overall management of journeys. Properly configuring the task template fields ensures tasks are aligned with the journey plan and assigned to appropriate users with clear timelines.

    Show full answer Show less

    Key Fields and Their Practical Use

    • Name: Provides a descriptive identifier for the task activity, helping users recognize the task purpose quickly.
    • Table: Select the Journey Accelerator Task [snjatask] table to track tasks and enable template field visibility.
    • Template: Defines fields specific to the chosen table, stored in the Journey Accelerator Task table for consistent task details.
    • Mandatory: Set to true if the task must be completed; false to make the task optional within the journey.
    • Type: Choose between Regular (standard to-do task) or Calendar (schedulable task linked to Microsoft Office 365 calendar events).
    • Active: Enables the task template for manager use; only active templates can be assigned in plans.
    • Task Short Description: A brief summary shown to users, appearing in the Journey Accelerator plan and task management views.
    • Task Description: Provides detailed information about the task to guide users on its requirements.
    • Parent Plan Table: Links the task template to the Journey Accelerator Plan [snjaplan] table, ensuring the task is associated with the correct journey plan.
    • Assign to Source: Specifies who the task is assigned to—Employee, Manager, or Mentor. Initially, only the first mentor receives tasks, but managers can reassign them afterward.
    • Relative Due Date Trigger: Defines when a task is assigned relative to the plan’s publish date. Use the Start on condition only, which is the default and recommended option.
    • Date Offset Type: Specifies if the task assignment is triggered On or After the relative due date trigger; the default and recommended setting is After.
    • Number of Offset Days: Specifies the number of days after the trigger date when the task is assigned. Only days should be specified, with hours set to zero. For example, setting this to 5 means the task triggers 5 days after the plan’s publish date.

    Practical Considerations for ServiceNow Customers

    By accurately completing these fields, you ensure tasks are created with clear responsibilities, deadlines, and descriptions aligned to the journey plan. Activating templates and assigning tasks properly allows managers to control task distribution and timing effectively. Using the recommended settings for date triggers prevents confusion and ensures tasks appear at the right time relative to the journey’s progress. This setup facilitates smooth execution and tracking of journey-related activities in ServiceNow.

    To make a task template, fill in the Journey Accelerator task template fields.

    Table 1. Task template fields and description
    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:
    • Mandatory: Set to true to make the task required. Set to false to make the task optional.
    • Type
      • Regular: Standard to-do task template.
      • Calendar: Schedulable task. Creates to-do task linked to Microsoft Office 365 calendar event.
    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:
    • Employee
    • Manager
    • Mentor
      Note:
      Initially, only the first mentor is assigned with to-do tasks in the list with multiple entries. Managers can reassign the to-do tasks to other mentors after the plan is created.
    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.
    • Created
    • End on
    • Start on
    • Updated
    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.
    • On
    • After
    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.
    • Days
    • Hours
    Note:
    Only specify days, and keep hours set at 0 (zero).

    For example: If the Relative Due Date Trigger = Start On, Date Offset type = After, and Number of offset days = 5 days, the task is configured to trigger 5 days after the publish date of the plan.