22 posts tagged with "Journey"

The Journey Audit Drawer now includes a Journey Data Changes tab, showing the audit record for journey level data captured in this specific journey. Journey level data is captured by data tasks in the journey rather than against the entity record, and is typically used for gathering field inputs that will drive other journey behaviours or capturing data that is only pertinent to each specific journey instance.

Previously, changes to journey level data were not part of the audit record and were not visible to reviewers. The new 'Journey Data Changes' tab lists each journey level data field that has been populated within the journey along with its current value, who last updated it and when, and expanding a field reveals its full history of changes within that journey. It follows the same layout as the 'Entity Data Changes' and 'Product Data Changes' tabs, and requires no additional permissions to view.

User Guide Reference: Audit in Fenergo -> Journey Level Audit

The Product Related Party Checkpoint is a new system-managed task that blocks a parent journey from advancing until all Product RP child journeys launched by the Product Related Party Launchpad have reached a terminal state. This ensures that the Merge Product Related Party Drafts and Verify tasks only execute against fully completed due diligence data.

Administrators can now configure the Orbis integration to exclude indirect shareholder associations from returned ownership hierarchies. When enabled, shareholder associations without a direct ownership percentage are removed, providing a cleaner view of direct ownership structures.

The Orbis external data integration now returns inactive companies alongside active entities. KYC analysts can search for a company by name or identifier and receive a match from Orbis regardless of whether the entity's status is active or inactive.

The Product Related Party Launchpad is a new task type that allows due diligence journeys to be triggered for related parties associated with products in a journey. It operates within a Product Connected Journey, mirroring the behaviour of the Related Party Journey Launchpad V2 in a product relationship context.

Users with the Unassign Journey or Task Owner permission can now clear a Journey Owner or Task Owner assignment without needing to immediately assign a replacement, returning the owner field to an unassigned state while preserving the team assignment.

Journey-level comments are now accessible from within a Task. Users can open the Comments shelf whilst working inside any Task in a Journey, without needing to navigate back to the Journey Hub.

User Guide Reference: Comments on LE and Journey

Custom External Adapters can now validate multiple Data Group fields in a single external call, and validation is enforced consistently across both the journey UI and API updates — ensuring data quality rules are applied whether fields are entered manually or submitted programmatically.

The Journey Audit Drawer now includes tabs to show audit records for Entity and Product data changes made in this specific journey. Alongside the existing journey lifecycle events under the Journey tab, reviewers can see entity field-level draft changes made within the journey on a new Entity Data Changes tab, and product field-level draft changes on a Product Data Changes tab (available where the Product domain is enabled in the tenant). An Only show edited fields toggle keeps the view focused on changes that matter, hiding fields that have only their initial draft state.

Fenergo SaaS now publishes two new event notifications — SLA Approaching Due and SLA Past Due — so that downstream systems can react in real time when Tasks, Stages, or Journeys are at risk of or have breached their committed SLAs. The notifications use the existing Webhook (push) and Polling (pull) Event Notifications mechanics and require no new APIs.

Both events apply to Journey-, Stage-, and Task-level SLAs and include the affected entity identifiers, due date-time, approaching threshold, current SLA status, and the Journey/Stage channels. For Task-level events, the payload also carries the configurator-defined TaskKey to make routing in high-volume consumers straightforward.

SLA Event Notifications are opt-in via a new Enable SLA Event Notifications toggle on the Journey Configuration modal in Journey Builder, gated by the existing Journey Configuration Edit permission. The toggle is off by default to preserve existing behaviour.

User Guide Reference: Configuring Journeys → Enabling SLA Event Notifications

Developer Guide Reference: Event Registry → SLA approaching due / SLA past due