Product Updates

Added new endpoint to retrieve grouped lookup options for fields Affected Endpoints​ POST /policyquery/api/v2/requirement-set/fields/grouped-lookup-options Request example - all parameters are optional: { "draftRequirementSetVersionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "targetEntity": "Client", "entityType": "Individual", "journeyLevelDataOnly": false}

Onboarding diverse products in a single Journey can delay activation for simpler items. With Product Connected Journeys you can launch dedicated, parallel journeys for specific products or groups of products, using configurable Product Scoping Rules to define which products qualify based on your criteria. The progress of these parallel journeys can be held against gates configured in the parent journey to ensure due-diligence requirements have been satisfied before they are activated. This creates a path for simpler products or those with already-satisfied due-diligence requirements to be actiaved much faster, without being blocked by unrelated parent journey activities. This approach enables you to: - Configure journeys that support Product Orchestration activities (Product specific Approvals, gather additional product data and documents, trigger activities with legal and tax teams, integrate with other systems using Integration Hub and Flow Studio) - Streamline Parent Journey activities by outsourcing product-specific or jurisdiction specific tasks to the Product Journey - Use Product Journeys to activate products as soon as their specific due-diligence threshold has been met. User and Configuration Guide Reference: Product Enablement User Guide - Product Connected Journeys

Portal Emails now have a v2 Template with enhanced layout and styling, available via Jira service request. This update introduces rich formatting options - bold, italic, underline, line breaks, and paragraph tags - for greater customization and improved readability. Note: Emails sent from Auth0 won't be changed to V2 until Portal Configuration is updated from FenX UI. User Guide Reference: Using the Fenergo Portal > V2 Email Templates

By default, the email sender on email templates is INFO. Now, this is configurable and can be updated through a service request via Jira. The Requested Change: Update Email Sender Name. Note: Emails sent from Auth0 won't be changed to V2 until Portal Configuration is updated from FenX UI. User Guide Reference: Using the Fenergo Portal > V2 Email Templates

Portal users can now view Rich Text Editor (RTE) content in a read-only format, ensuring they can review information provided by Fenergo users without the ability to edit. User Guide Reference: Using the Fenergo Portal > Rich Text Editor

Salesforce now supports dynamic validations for data requirements in Global Policy, allowing Salesforce Admins to apply conditional validations (e.g., mandatory, read-only etc.) to various data field types. This is supported on the Data task and the Related Party task. User Guide Reference: Salesforce User Guide > Conditional Validation Support

Salesforce now supports Related Product Trigger Conditions. User Guide Reference: Salesforce User Guide > Related Product Trigger Conditions

Salesforce now supports Related Client Trigger Conditions on the Related Party task. User Guide Reference: Salesforce User Guide > Related Client Trigger Conditions

Automatically removes outreach request links when journeys are cancelled or referred, and applies a 90-day TTL to stale links - ensuring cleaner data and improved handling of unactioned or outdated outreach requests across cancellation, expiry, and referral scenarios. User Guide Reference: Using the Fenergo Portal > Outreach Requests Dashboard

This feature allows for the supporting of Related Party datagroups within Salesforce. It introduces this functionality for both Company and Individual Related Parties. Users will be able to add, edit, and delete these related party datagroups within Salesforce. User Guide Reference: Salesforce User Guide > Related Party Datagroups

Integration Flows has added the following capabilities... Configuration Exchange to support promoting Flows between environments Policy Adapter Initiators. Implement your own policy adapters like Custom Search Providers, Custom Validation Providers, and Custom Task Providers using Integration Flows Added a new endpoint to allow Custom Authentication schemes for API-initiated Flows for outside systems that are unable to support Fenergo's default endpoint using OAuth. Includes support for IP Whitelisting, shared secret, and HMAC authentication Added support for ASync flows to enable new integration patters such as HTTP Long-Polling and HTTP Callbacks (see task enhancements) Enhanced Schemas. Schemas can now be generated from OpenAPI specification docs and can be leveraged from Transformer code New and Enhanced Tasks Wait - Pauses Flow Execution for a configurable amount of time (1s – 5m). Use this when polling an API until some condition met. Flow Invoker - Use this to trigger another flow to run in parallel or wait for completion End - Formally return response data from a Flow Execution. Used in External Data Adapter, Policy Adapter, and Flow Invoker triggered Flows Supergraph - Added support for Entity-based queries HTTP Invoker - Added support for Callback pattern. HTTP Task will pause the flow and wait for a callback from outside system before resuming. Trasformer - Added support for schemas, encrypting/decrypting functions. User Guide Reference: Integration Flows Overview

DataImport event extended with the following capabilities Reonboarding Journeys (Partial and Full Jurisdictions) Update multiple inflight journeys with single event Products – Initial support for importing Product Data. Supports Create, Update, Delete/Offboard operations for Products. Product ID and status available in Event details via IntegrationHub. Support for Product Related Parties, Product to Product Relationships, and Product Datasources planned for a subsequent release. Support for Journey Level Data which allows clients to configure entity attributes that exist only in a journey and will not be verified. Useful for storing temporary data like Integration Statuses. Enforcing Request Validations - previously request validations were only logged in Integration Hub. Now error-severity issues will force the event to fail fast. User Guide Reference: DataImport Overview

VerifiedImport brand new event for bulk updating entity data directly to the verified record. Offers similar enhancements over V1 events as DataImport: Stateless Integrations - Calling system does not need to know an Entity's state in Fenergo. There is an option to provide a unique identifier (e.g. centralized MDM) if available to decide if entity should be created or updated. Multiple Entities per event - VerifiedImport allows for multiple entities per message. Lookups Resolver - Lookup values can be provided as value, id, or custom column from the reference list definition. Message Simplicity - External Systems need only provide incoming datakey and value. Fenergo will use internal policy configuration to determine data types and validations User Guide Reference: DataImport Overview

GET /portaltenantquery/api/portal-users/userdetails/{id}/nolinks - Gets Portal User details without linked entities (returns details of portal user without linked entities)

ID&V is now enforced within the Portal, blocking the user from progressing until they complete the necessary verification steps. User Guide Reference: Using the Fenergo Portal > ID&V

The existing Entity Grouping functionality means that every Child Entity is eligible for a Journey when an Entity Group Journey is ran. Selective Journey Launching delivers the ability to trigger Journeys for Child Entities only when required, giving greater flexibility and control over the Child Entity Journeys created from the context of the Entity Group. Please note this feature is currently enabled everywhere except live production tenants. User Guide Reference: Using Legal Entity Groups User Guide > Selective Journey Launching

Gives the ability to selectively share data and related parties to designated Child Entities from within the context of the Group Journey. These actions can be performed on multiple Child Entities, allowing for the sharing of specific information to a subsection of your Child Entities. Please note this feature is currently enabled everywhere except live production tenants. User Guide Reference: [Using Shared Data User Guide > Bulk Entity Management](/user-guides

Users can now save tasks without completing all mandatory fields on Data tasks and Data & Documents tasks, allowing users to return to fill in the rest of the fields at a later time. User Guide Reference: Using the Fenergo Portal > Journeys and Tasks

Clodagh from Fenergo demonstrates how fields can now be triggered on the document upload modal and create virtual document modal in a documents task and on the entity profile using entity data.

This feature will allow users to trigger fields and drive validations via entity data on the Document Upload Modal and Create Virtual Document Modal in a Documents task and on the Entity Profile. User Guide Reference: Managing Documents -> Document Management

JourneyInstanceProcess.tasksV2, JourneyInstance.taskV2 and JourneySchemaProcess.tasks to return Journey Tasks in a polymorphic manner (e.g PolicyTaskDto, ProductTaskDto etc.) exposing type-specific properties fragment PolymorphicTaskProps on JourneyTaskDto { id taskType ... on PolicyTaskDto { policyTarget policyCategory policyRequirementType } ... on ProductTaskDto { productActions productScopingRuleSet }}

The ability to transfer and update association data is available for clients to try out in beta mode. User Guide Reference: ETL Extract Transform Load User Guide for Associations

Beta tag is removed and tool is ready for use in production for entity data. User Guide Reference: ETL Extract Transform Load User Guide

Padraig Buckley, a product owner for the Fenergo portal, demonstrates a variety of new features within the Portal.

Roscha from Fenergo introduces new functionality that allows users with different roles to complete different outreach stages/tasks in a journey.