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.

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.

We have now introduced Read Only Validation for Data Group Policy Requirements. This will allow users to display Data Group grids in Journeys 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.

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.

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'.

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.

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

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.

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.

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.