Task template fields

  • Release version: Zurich
  • Updated July 31, 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 Task template fields

    Task templates in Journey Accelerator enable you to define reusable task configurations that help streamline task management within plans. By filling in specific task template fields, you create templates that standardize task properties, assignment, scheduling, and behavior for consistent execution.

    Show full answer Show less

    Key Fields and Their Functions

    • Name: A descriptive label for the task template to identify the associated activity.
    • Table: Select the Task [snjatask] table to enable access to template-specific fields tracked in Journey Accelerator.
    • Template Fields: Define task properties such as:
      • Mandatory: Mark tasks required or optional.
      • Editable: Control if users can modify task fields or delete tasks. When false, plan creators cannot change task name, description, or optional status, and users cannot delete the task.
      • Type: Choose between Regular (standard task) or Calendar (integrated with Microsoft Office 365 calendar events).
      • Active: Enable the template for use; only active tasks are available for managers.
      • Task short description: Appears in the plan interface as a brief summary.
      • Task description: Detailed explanation of the task.
    • Parent plan table: Links tasks to the overarching Journey Accelerator Plan [snjaplan] table, enabling plan-related field access.
    • Assign to source: Determines the default assignee category: Employee, Manager, or Mentor. Note that initially only the first mentor is assigned for multiple mentors; managers can reassign tasks later.
    • Relative due date trigger: Sets the condition for task assignment based on the plan's publish date. Use the Start on condition exclusively (default selection).
    • Date offset type: Defines whether the task triggers On or After the relative due date trigger; After is recommended and default.
    • Number of offset days: Specify the number of days to offset the task assignment from the trigger date. Only days should be used (hours set to zero). For example, setting Start on + After + 5 days triggers the task 5 days after the plan publish date.

    Practical Benefits for ServiceNow Customers

    • Standardizes task creation across plans for consistent execution and reporting.
    • Enables fine-grained control over task properties, including mandatory status and edit permissions.
    • Supports integration with Microsoft Office 365 calendar events for schedulable tasks.
    • Facilitates dynamic task assignment to appropriate users, with flexibility to reassign after plan creation.
    • Allows precise scheduling of task assignments relative to plan milestones, improving workflow timing and coordination.

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

    Table 1. Task template fields and descriptions
    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 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.
    • Editable: Set to true to enable users to modify task fields. Set to false so that users can't modify certain fields in the task.
      Note:
      When editable = false, the following occurs:
      • The plan creator can't change the To-do name, To-do description, or This to-do is optional fields.
      • Users can't delete the to-do task from a plan.
    • 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.