Install Journey designer version 2

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 1 minute to read

    • Install the Journey designer version 2 [sn_jny] application to enable administrators and managers to create and manage various professional and personal events and journeys.

    Before you begin

    Note:
    You must upgrade to Utah before you can install Journey designer version 2.
    Dependent plugins and apps for Journey designer:
    • Human Resources Scoped App: Core [com.sn_hr_core]
    • Human Resources Scoped App: Lifecycle Events for Enterprise [com.sn_hr_lifecycle_ent]
    • Employee Center Pro 28.0.1 [sn_ex_sp_pro]
    • HR Taxonomy 1.2.1[sn_hr_emp_taxonomy]
    • Journey Accelerator 6.0.5 [sn_ja]
    • Retry Framework 1.0.2 [sn_retry_handler]
    Role required: admin.

    About this task

    Journey designer version 2 (JD) must be installed as a store application on the Utah family release.
    Note:
    The Journey designer app also installs the Journey Accelerator v6.0.0 [sn_ja] application.

    Procedure

    1. Go to the ServiceNow Store and find the Journey designer [sn_jny] application using the filter criteria and search bar.

      In the list next to the Install button, the versions that are available to you’re displayed.

    2. Select a version from the list and select Install.

      In the Install dialog box that is displayed, any dependencies that are installed along with your application are listed.

    3. If you're prompted, follow the links to the ServiceNow Store to get any additional entitlements for dependencies.
    4. If demo data is available and you want to install it, select the Load demo data check box.

      Demo data comprises sample records that describe application features for common use cases. Load demo data when you first install the application on a development or test instance.

    5. Select Install.

    What to do next

    When Journey designer is installed, outstanding Lifecycle Events cases aren’t affected. You can migrate existing HR services to use journeys instead of Lifecycle Events. See, Journeys Migration Guide.