It’s common to expect that once an association (for example, between a Client and a Related Party) is created in one Journey, it should automatically appear in other active Journeys. However, in Fenergo, each Journey instance operates on its own data snapshot, meaning changes made within one Journey remain local until they are verified and promoted. Associations created during a Journey stay in draft form until verified — only then do they replace the previously verified records and become globally visible across all other Journeys.
Solved
Why does an association I created in one Journey, such as Onboarding, not appear or carry over into another Journey?
Best answer by jawadkhan
Each Journey instance in Fenergo operates with its own data snapshot. Associations created in one Journey (e.g., Onboarding) exist in draft form and are only made globally visible after verification.
Explanation
- Draft relationships and entity updates remain local to the current Journey context.
- Once verified by the Verify Related Party Associations V2 task, the system replaces the previously verified record with the updated one, making it visible in other Journeys. ²
- If the relationship type or policy scope is configured as “Journey-specific,” it won’t be shared across Journeys.
To ensure relationships are visible globally:
- Always include the Verify Related Party Associations V2 task at the end of the Journey.
- Confirm the relationship category is configured in Policy as a global association.
Each Journey instance in Fenergo operates with its own data snapshot. Associations created in one Journey (e.g., Onboarding) exist in draft form and are only made globally visible after verification.
Explanation
- Draft relationships and entity updates remain local to the current Journey context.
- Once verified by the Verify Related Party Associations V2 task, the system replaces the previously verified record with the updated one, making it visible in other Journeys. ²
- If the relationship type or policy scope is configured as “Journey-specific,” it won’t be shared across Journeys.
To ensure relationships are visible globally:
- Always include the Verify Related Party Associations V2 task at the end of the Journey.
- Confirm the relationship category is configured in Policy as a global association.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.