Salesforce now supports the Document collection aspect of Fenergo’s Related Party Data and Documents Task. This feature allows all documents to be captured directly within Salesforce for in scope related parties. These document V2 capabilities allow Salesforce users to upload, waive or defer documents

Fenergo’s Service Level Agreements (SLAs) are now supported in Salesforce, allowing users to view and track journey deadlines directly within Salesforce. This ensures consistent visibility of SLA commitments across Fenergo and Salesforce, improving efficiency and oversight.

Salesforce now supports the Unsubscribe from Ongoing Screening task, allowing users to remove entities currently enrolled in ongoing screening.

This feature introduces Mandatory Search Parameters which ensure that entity searches in the Salesforce Plugin cannot be executed unless all mandatory fields are completed. This aligns with the behaviour in Fenergo's “New Request” screen.

As part of the Docs V2 Task in Salesforce, Acceptable Document Types and Document Descriptions are now supported. This will allow Admin to input acceptable document type descriptions, allowing Salesforce users like Relationship Managers to know what documents they need to prepare.

This feature introduces the ability to connect multiple Fenergo tenants to a single Salesforce instance.

This feature introduces Client Offboarding and Client Reonboarding functionality to Salesforce, matching the capabilities in FenX. It includes journey types, modal updates, jurisdiction selection logic, and system tasks needed to facilitate full and partial client lifecycle transitions.

VLookup functionality for Datagroup fields is now supported in Salesforce during entity creation. This ensures datagroup values such as Country or State are matched and translated when sent from Salesforce to FenX.

This enhancement ensures conditional fields in the Basic Details section are correctly mapped when initiating a new request in Salesforce. If a parent condition is met, the related field is displayed and pre-filled as expected.

This feature allows for the configuration of Product Requirement Set scoping conditions that support the Related Entity as a condition. It also enables the conditional displaying of Product Data (datagroups and data fields) based on scoping conditions related to both the Current Product and Related Entity.