Product Updates

Screening scoping has been extended to include an entities investment accounts and their related parties (RPs). Investment accounts and their RPs are treated in the same manner as any other entity that is included in screening. If the RP of the investment account itself has RPs, these entities will be included in the screening scope. Screening scoping may be utilized to filter out investment accounts from screening. User Guide Reference: Investment Account Configuration Guide

Previously, cloning a product required manaully adding Related Parties to the cloned product. It's now possiblet to include up to 50 Product-Related Party Connections with the cloned product. If there are greater than 50, the user will be alerted that the Products Related Parties will not be included if they proceed. User and Configuration Guide Reference: Product User Guide - Product Enablement User Guide

Ability to define rules to trigger data, documents and ownership and control requirements, on an entity, based on the data of a related fund that is linked to an investment account for that entity. User Guide Reference: Investment Account Configuration Guide

Flag investment accounts for offboarding so that they no longer trigger scoping and follow data retention periods. Full Offboarding of the Investor: If an investor is offboarded in full, all investment accounts will be automatically offboarded. Offboarding of a Single Investment Account: A button will be added to the investment account task that will allow for offboarding of a single investment account. Data Deletion: A data deletion process will be set against the investment account. A data deletion journey will be automatically triggered for the account dependent on the deletion process. User Guide Reference: Investment Account Configuration Guide

Aligning with Policy, it's now possible to configure data groups as read-only within Product Requirement Sets. This allows data groups to be configured as read-only, which can benefit review contexts or where the integrity of data populated by external systems needs to be preserved. To configure a read-only data group, simply select the 'Validations' tab when configuring a Product Requirement Set with a Data Group type requirement and toggle on 'Read Only'.

Orbis users can now enable Automatic Import of Related Parties under certain conditions. The system will duplicate check against the unique Orbis ID, or a combination of LE fields to determine if the entity is new, or exists already in Fenergo. User Guide Reference: External Data Functional Configuration Guide:

To speed up the processing of multiple documents being uploaded at once in the DocumentsV2 task, it is possible to apply all selections, except the Document Name, in the Document Upload modal to the current and subsequent documents to be processed. The APPLY TO ALL button will take the selections and apply to the current and remaining documents. User Guide Reference: Document Management V2 User Guide->Bulk Upload using Apply to All

A new permission has been introduced that applies to the Related Parties task. This new permission "Association Edit & Link Only" will allow Clients to control scenarios where specific users require the ability to add associations, but only link to existing entities. New entities cannot be created as part of the process. User Guide Reference: Access & Permissions Permissions Catalogue

Orbis users can now enable Automatic Import of Related Parties under certain conditions. The system will duplicate check against the unique Orbis ID, or a combination of LE fields to determine if the entity is new, or exists already in Fenergo. User Guide Reference: External Data Functional Configuration Guide:

This feature will allow users to configure multi-level linked lookup fields where a Parent in one Linked Lookup field may be a child in another Linked Lookup field, creating a cascading flow of filtered Lookups. User Guide Reference: Reference Data User Guide

Affected Endpoints​ GET /policyquery/api/requirement-set/{versionId:guid}/requirements - Added new endpoint GetRequirementsByVersionIdPaged to retrieve version requirements with paging GET /policyquery/api/requirement-set/{setId:guid}/version/{versionNumber:int}/light - Added excludeRequirements parameter to GetRequirementSetVersionLightById

Changed the endpoint EvaluateAllRequirements to include IsMaterialData property in the response Affected Endpoints​ POST /policylogicengine/api/v3/engine/evaluate-all-requirements

Added multi-tenant support for users in the SCIM API, allowing clients to create, update and delete users with the same email in multiple tenants. Endpoints affected: POST {{identityDomain}}/scim/Users DELETE {{identityDomain}}/scim/Users/{id} PUT {{identityDomain}}/scim/Users/{id} PATCH {{identityDomain}}/scim/Users/{id}

Documents V2 is now available in a Journey, requiring new permissions including access, create, edit, delete, and waive and defer. Users can upload files via browsing or drag-and-drop, update metadata, and see uploaded documents as labeled chips. Future updates will add waive and defer, bulk upload, matching requirements linking, and intelligent document processing in Salesforce. User Guide Reference: Salesforce User Guide

This feature allows clients to perform a free text filter based on additional configured columns allowing users to easily search and find the information they need. Configurators can also specify the column order as part of the dashboard setup. Future enhancements will deliver the capabilities to filter based on a select dropdown value. User Guide Reference: Portal Configuration User Guide > Portal Dashboards

Niamh introduces the new feature in the deals task that restricts related party searches and the ability to create new related parties. He demonstrates how this feature is useful for clients who have their entities mastered in another application and want to control how related parties are maintained. He shows how the related party model lets you create a new related party, and how this functionality can be removed through configuration. He also demonstrates the ability to restrict search to the main entity, which is useful for clients with complex relationship structures.

The financial analysis task has been enhanced to have the maximum limit extended to accommodate up to 30 entities +15 Joint + 15 Deals within the task. Furthermore, enhancements have been made with how the credit scoping rule function with financial analysis to ensure up to 80 entities are "in-scope" before have the scoping rules applied. Previously, the system would only apply the scoping rules to the first 20 entities and disregard the other entities. User Guide Reference: Financial Analysis User Guide

Enhanced configuration of webhooks to support batching in webhook delivery. New properties: type and batchSize. GET /webhooks/v1/webhooks GET /webhooks/v1/webhooks/\{webhookId\} POST /webhooks/v1/webhooks PUT /webhooks/v1/webhooks/\{webhookId\}

The latest version of the Documents task type (Documents V2) is now available as a selectable task within a Journey. Given the user has the correct permissions, they will be able to access the Documents V2 task. Please refer to the Document Management V2 User Guide for detailed information on the new permissions that Documents V2 introduces. User Guide Reference: Salesforce User Guide

This configuration option restricts searches to the Entity Group or Main Entity in the Related Parties modal within the context of the products in the Deals Task, ensuring users link only appropriate and pre-approved entities. User Guide Reference: Deals Configuration Guide

Restrict the creation of related parties from within the product modal in the context of the Deals Task to ensure that users only link existing entities. User Guide Reference: Deals Configuration Guide

Introduction of Read Only Validation for Data Groups in Deals Requirements. This will allow users to display Data Group grids in the deals details tab of the deals task in a Read Only format. The purpose behind this is to allow users to capture Data Group Entries in one task, and expose them in a Read Only / Review format in another task. User Guide Reference: Data Group User Guide

Arthur from Fenergo demonstrates how to trigger requirements on an investor record based on related funds of investment accounts. This feature, part of their asset servicing solution, allows for the capture and management of the relationship between an investor and a fund. The video steps through the configuration process and shows the feature in action within a journey. This helps streamline user interaction during investor onboarding or maintenance.

Georgina from Fenergo introduces a new feature in their asset servicing solution that allows users to capture additional related parties for investment accounts. This feature enhances the management of relationships between an investor and a fund, providing a deeper understanding of investor investment accounts.

To provide a deeper understanding of the Investment Account it is now possible to capture related parties and their relationship to the Investment Account within the Investment Account task. User Guide Reference: Investment Account Management->Investment Account Management Configuration Guide and Investment Account Management Configuration Guide