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
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Calling Document Record Deep link from Journey Task with Person ID Parameter

Dear Oracle Customer Cloud Connect Community,

I hope this message finds you well.

I am encountering an issue while attempting to call a deep link from a journey task within the Oracle system. Specifically, the problem lies in passing the "pPersonId" parameter, which is Base64 Encoded. Due to this encoding, the deep link fails to function as intended.

Below is the URL generated through Journey Task:

<POD>/fscmUI/faces/deeplink?objType=DOCUMENT_RECORDS_ANY&action=NONE&objKey=pMode=CREATE;pSystemDocType=GLB_MEDICAL_QUESTIONNAIRE;pPersonId=MzAwMDAwMDQ5MTIxMzE3

where "MzAwMDAwMDQ5MTIxMzE3" is the Encoded value of Person ID

I am reaching out to inquire if anyone in the community has encountered a similar issue and, if so, whether there are any known solutions or workarounds to effectively utilize a deep link where a Person Id value needs to be passed.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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