Overview:
In Fenergo, policies play a crucial role in shaping the compliance and data requirements throughout a journey. This article outlines the behavior of policies and data groups during the lifecycle of a journey, including how they are scoped in, applied, and updated.
Global Policies:
Initial Scoping: At the start of a journey, the latest published version of a Global Policy is scoped in. This version of the policy is "rubberstamped," meaning it is locked in and will remain unchanged throughout the journey.
No Version Changes: There is no scenario in which a different version of the Global Policy will come into scope during the journey. The version that was active at the journey's start will continue to apply until the journey is completed.
Other Policies (e.g., Global Full, Jurisdictional):
Initial Scoping: For policies that are scoped in at the creation of the journey (e.g., Global Full, Jurisdictional), the latest active version of the policy at the time of the journey's start is applied. This means the most recently published version of Policy X as of the journey's start date is used.
Newly Scoped Policies: If a new policy is scoped in during the journey, the latest version of that new policy at the time of scoping is applied.
Re-open Scenarios: Re-open scenarios do not trigger updates to the policy versions used in the journey. The policy versions remain as they were at the time of the journey's initial scoping.
Data Groups and Look-Up Fields:
Policy Requirements and Look-Up Lists: Policies may include requirements that reference lookup lists (e.g., dropdowns, linked lookups). When the Config Baseline feature is enabled:
Lookup Lists: The policy requirement is bound to the lookup list available at the time of the journey’s creation. The active version of the lookup list (latest published version) is used, and this version remains fixed throughout the journey.
Linked Lookups: Similarly, linked lookups are bound to the version available when the journey was created. These versions will not change throughout the journey.
For more details on Config Baselines, refer to Config Baselines Reference Data | Fenergo Document Portal.
Data Groups: Data groups reference specific groups such as Addresses. Unlike lookup lists, a field requirement in a journey will always use the latest active version of a data group.
Version Updates: The version of the data group used in the journey can update if a newer version is published while the journey is still open. This ensures that the journey reflects the most current data group requirements.