Observed Behaviour
In OGS journeys:
The OGS Related Client Launchpad triggers specified journeys
This mainly occurs when the Materiality assessment is Material for the entity
However, this can also occur even when:
Materiality =
None/NoNo materiality parameters are set to “Yes”
Example:
Materiality Review completed with all parameters = None
Yet:
Maintenance journeys launched for related entities
Root Cause / Explanation
When a true match is identified, the Related Client Launchpad task initiates journeys for all impacted related clients listed in the Client Materiality section. This behavior applies regardless of each client’s current materiality status at the time of execution.
Although journey-level scoping conditions can be configured, materiality is evaluated at the aggregated client level. This means that if a client has ever been classified as Material, the aggregation logic will continue to treat that client as Material in subsequent evaluations.
As a result, historical materiality classifications persist and influence future journey triggering, even if the client’s materiality appears to have changed in later stages.
Frequently Asked Question
Q: Does this mean that if a client is marked as a Material PEP in one journey, the materiality flag will continue to be triggered in all subsequent journeys, even if it is later changed to Non-Material or None?
A: Yes, that is correct.
Due to the aggregation mechanism, once an aggregated field such as Material PEP is set to Material, it will continue to be treated as Material in future journeys. This persists even if the value is later updated at the journey level.
The only way to override this behavior is by directly updating the aggregated value at the entity level (for example, via EntityData APIs). However, this approach is generally recommended only in cases where incorrect data needs to be corrected.