ETL now supports the bulk deletion of existing association records using the new Delete Associations data type. Combined with the existing Associations data type, this also enables a net update to an association's relationship type in a single ETL project — deleting the old relationship and creating the new one in the same load.
Search Text Fields are now supported within Product Requirement Sets and linked Data Groups. Now, when configured within products, users can retrieve values from an external or (Flows simulated) data source via a Policy Custom Search Provider. This facilitates ensuring that a correct value is selected from a trusted source (for example email address or external identifiers).
The Matching Tab in the Investment Account Document Requirements workflow now also surfaces acceptable-type documents held at the related investor entity level, not just those linked to the investment account itself. Users can link a matched investor entity document directly to the investment account requirement without creating a duplicate document record.
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.
Document Generation now supports investment account data as a set of configurable data sources in the Component Library. Clients with the Accounts Service ID enabled can build document components from investment account records linked to the main entity, including related bank accounts, related investment accounts, and the fund, share class, bank account, and related party data associated with those investment accounts.
This extends the existing Document Generation capability which already supports Entity Data, Related Parties, Associations, Products, Deals, and Collateral — to cover the full breadth of investor data required to generate subscription and onboarding documents.
A set of editor enhancements are now available in Template Configuration, reducing configuration effort and improving the template authoring experience.
The Automated Document Generation task now supports up to 500 direct related party associations, up from the previous limit of 50.
The Document Auto Link feature in Journey Builder enables documents stored on the Entity Profile Page to be automatically linked to matching document requirements when a task opens, eliminating the need for manual linking. Configurators can enable this via a toggle on the Documents V2, Data & Documents (Doc V2), Hierarchy Capture, and Related Party Data & Documents task types. When enabled, the system evaluates all available documents against the acceptable document types of each requirement during task pre-processing, after Document Persistence has run. See the user guide for exclusionary rules.
User Guide Reference: Document Management->Document Requirement Autolinking
We are introducing enhanced search capabilities for the Multi-Field External Search Provider as it exists for data groups. This builds upon the existing single-field search behaviour. In the first iteration, only a free-text search phrase was sent to the external adapter. This enhancement extends that capability so that additional fields from the relevant data group can also be selected as search criteria and included in the API request.
On the end user side within a journey, if data group fields are added to the search request then we will change the view in the data group. The search modal will show a two-tab layout: a Search tab presenting the search box alongside any configured data group fields, and a Details tab where the selected result is populated for review and saving. Where multiple providers are configured for the same data group, results are aggregated into a combined grid.