Considerations for Importing a Journey Template Configuration

This topic describes the considerations to import a journey template on the Checklist Template setup page.

You can use the Export button on the setup page to quickly export the journey template to either review offline in Microsoft Excel, or attach to the servive request (SR) for Support and Development to review.

Similarly, you can use the Import button on the setup page for a one-off import of the journey template. For example, for a Customer Connect sharing initiative. This button is hidden by default and enabled using a profile option.

Here are some points you need to consider when importing a journey template xml:

What are you importing?	What you need to do before importing
Enterprise Onboarding journey category	First import the step journeys (journeys of the category Enterprise Onboarding Step) in the destination environment with the same names as in the XML file.
Journey that has an eligibility profile associated to it	Ensure that the eligibility profiles are available in the destination environment with the exact same names.
Journey that has tasks of the type Electronic Signature – Native	Configure the document to be signed in the destination environment with the exact same name and residing in the same path as in the XML file.
Journey that has tasks of the type Electronic Signature – DocuSign	Configure the DocuSign integration in the destination environment with the exact same name as in the XML file.
Journey that has tasks of the type Questionnaire	Configure the questionnaires with the exact same codes in the destination environment.
Journey that has tasks of the type Document	Attach the document again to the task in the destination environment because the documents associated with the task won’t be imported into the destination environment.
Journey that has tasks of the type Report	Configure the report in the destination environment with the same name and residing in the same path as in the XML file.
Journey that has tasks of the type I-9 configuration	Configure the I-9 codes in the destination environment with the same names as in the XML file.
Journey that has tasks of the type Configurable Form	Configure the Descriptive Flexfield (DFF) Context in the destination environment with the same context name as in the XML file. You can then create the segments for the context after importing.
Journeys that have been translated to more than one language.	Translations won't be imported.

It's recommended not to use Export or Import when migrating your configuration across different environments. To migrate your configuration across environments, use the Functional Setup Manager (FSM) feature. To see the documentation about the feature, go to Oracle Help Center > Human Resources > Implement > Using Functional Setup Manager > Setup Data Export and Import