An issue was encountered when triggering a Related Party (RP) journey through the Launchpad. Although the RP journey appears to be successfully triggered and marked as complete via the checkpoint task, it is not properly linked to the Related Party.
The triggered journey is not accessible from the Connected Journeys view and navigating to it results in a “Something went wrong” error. Additionally, the journey is not visible at the Related Party entity level, and the Related Party name is missing within the checkpoint task.
This issue prevents validation of the RP journey flow and blocks proper configuration of the Review Scheduler.
Root Cause:
When journeys are created via the RP Launchpad task, access layers from the entity draft are reassigned to the newly created child journey.
For Example, the child journey inherited the following access layers:
{
"geographic": [
"Global"
],
"businessRelated": [
"Institutional Entity Access Layer"
]
}
However, the tenant configuration contains the following access layers:
[
{
"id": "0d1b4925-4e8a-4720-b8af-e710562d091f",
"dataKey": "ICS Entity Access Layer",
"label": "ICS Entity Access Layer",
"type": "BusinessRelated",
"dataType": "Entity",
"sensitiveDataKind": "None"
},
{
"id": "db8ceadb-eb3f-449a-857e-d7929164a782",
"dataKey": "ICS Journey Access Layer",
"label": "ICS Journey Access Layer",
"type": "BusinessRelated",
"dataType": "Journey",
"sensitiveDataKind": "None"
},
{
"id": "01431a37-b6a8-483e-b279-684af9da0bd3",
"dataKey": "Institutional Entity Access Layer",
"label": "Institutional Entity Access Layer",
"type": "BusinessRelated",
"dataType": "Entity",
"sensitiveDataKind": "None"
},
{
"id": "b0ce7cff-d5f2-4dcc-83af-5ef328d03c0c",
"dataKey": "Institutional Journey Access Layer",
"label": "Institutional Journey Access Layer",
"type": "BusinessRelated",
"dataType": "Journey",
"sensitiveDataKind": "None"
}
]
The issue occurs because there is no “Institutional Entity Access Layer” configured for dataType “Journey”, meaning the user does not have access to the created journey. This results in the journey being inaccessible and not properly linked to the Related Party.
Resolution:
Ensure that matching access layers exist for both Entity and Journey data types when journeys are created via the RP Launchpad.
Specifically, if the system assigns “Institutional Entity Access Layer” at the entity level, a corresponding Journey-type access layer must also exist or be mapped correctly.
Without this alignment, the user will not have access to the created journey, leading to broken navigation and missing linkage in Connected Journeys.