1. Implementing and Using Journeys
  2. Overview of Guided Journeys

Overview of Guided Journeys

You can provide guidance such as tutorials, company policies, and best practices in the context of an HCM flow using guided journey tasks. For example, tasks to help a line manager transfer an employee.

Based on the way you setup the guided journey, when employees, line managers, or HR specialists initiate an action they see a Guide Me button. This button appears in ADF and Redwood pages at the section header level, page header level, or both. It lists tasks that you add to guide the user in their transaction.

There are several aspects involved in creating a guided journey.
  • First, you need to enable guided journeys using the ORA_PER_GUIDED_JOURNEYS_ENABLED profile option. To do this, use the Manage Administrator Profile Values task in the Setup and Maintenance work area and change the profile value to Y.
  • You use the Guided Journey category in Checklist Templates to setup and add tasks that are relevant for the guided journey. You can only use tasks of the type Analytics, Document, Embedded Learning, External URL, Manual Task, Questionnaire, Report, and Video in a guided journey.
  • Once the guided journey setup is done, you use the Transaction Design Studio (TDS) to associate it to an action using TDS rules. You use specific attributes available for a TDS action to further determine for whom the guided should display.
  • You’re done after you select and add tasks that you want to display at the page header or section header region.
Here are some points to consider:
  • Guided journeys are supported on Redwood pages.
  • Guided journeys display in various responsive pages configured in TDS to help complete the transaction. You can’t assign a guided journey to a worker, so guided journeys don’t appear on the My Journeys or Assigned Journeys tabs in the Journeys app.
  • You can't change the category of an existing journey to Guided Journey. Instead, define a new guided journey.
  • It’s recommended to use only one guided journey per TDS action.
  • Only a limited set of TDS actions are currently available for configuring guided journeys.
  • You can use Set Modal Window Properties during setup to specify the size of the modal window that opens up in the guided journey. Here are the properties you need to specify (applicable for mobile view as well):
    • width - The width of the modal window in pixels. The default is 500.
    • height - The height of the modal window in pixels. The default is 350.
    • modal - The type of window. Attributes are Y or N. Y indicates modal window and N indicates non-modal window.
    • resize - The option to resize. Attributes are Y or N. Y indicates users can resize the window.

    For example, width=400;height=300;modal=Y;resize=Y

  • Except the Questionnaire task type, all other task types used in guided journeys are read-only type tasks which don’t save any data anywhere.
  • It isn’t possible to see the responses provided by the user as part of a guided journey questionnaire task anywhere. The responses are stored in the PER_CHK_GUIDED_RESPONSES questionnaire tables. You can build your own OTBI reports to extract this data.
For more information on guided journeys, see these resources:
  • Contextual and Guided Journeys (https://community.oracle.com/customerconnect/discussion/631002) on Customer Connect.
  • Use Transaction Design Studio to Configure Field Displays in this guide.
  • Transaction Design Studio -What It Is and How It Works (Document ID 2504404.1) on My Oracle Support.