Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Guided Journey - Analytics Task Type sends parameters of user, not on individual being transacted — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Guided Journey - Analytics Task Type sends parameters of user, not on individual being transacted

Received Response
61
Views
5
Comments
edited Feb 26, 2023 6:52PM in Journeys 5 comments

Summary:

Created a quick OTBI Analysis to assist the Shared Services team to help know the Hire Action Reason based on the Requisition Business Justification since they are tied. When tying this Guided Journey on Convert Pending Worker, the Analysis Parameter is sending over the Person ID of who I'm logged in as, not the Person ID of the the individual being converted.

Is this the intended behavior?

Content (required):

When creating the Guided Journey Analytics Task Type, established the Analysis Parameters for Person ID and created a prompt in the OTBI analysis for the Person ID


When I go to transact and execute the Convert Pending Worker, I select the Guided Journey I created (in this instance called "Associated Requisition Business Justification") and the associated report runs but errors out. Without a prompt or parameter, I can get it to run for a hard-coded prompt or entire list, but we want to only show the details for this single person being converting to a new hire.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!