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.

Salesforce now supports virtual documents. Virtual Documents represent a file that can be linked to entities, journeys, and document requirements within Salesforce. Unlike standard documents, virtual documents are not stored in Salesforce but instead point to a file hosted externally via a URL.

Allows users to add and maintain detailed notes on client records from the Entity Profile Page in Salesforce, without creating a journey. Narratives have role-based permissions, ensuring that only authorised users can view, create, edit or delete them.

This button allows users to refresh the journey list. The button is located on the journey component, next to the Launch New Journey button.

• Salesforce Custom Journey Wrapper: Allows the client to hide the Launch New Journey button if they want to handle the journey launching via a custom solution.
  • Global Apex endpoint to create a Journey from Backend: Allows the client to programmatically launch journeys without relying on our Salesforce UI to create new journeys.
  • Expose Journey Component for Client Use: Previously, the journey component that renders detailed journey view including task interaction was not publicly exposed. Now, the client can embed the component in an area of their choice in Salesforce.

Enables read-only Text Area fields in Data Tasks to automatically expand to show their full content.

Ensures Salesforce users complete all mandatory Ownership & Control requirements in the Related Party task by enforcing rules through the use of toggles. The mandatory requirements and error messages are configurable to fit specific needs.

Conditional triggers from Datagroups are now supported.

Allows user to manually cancel a Journey, populate a reason for the Journey cancellation and add any additional notes/comments for context on why the Journey was cancelled.

Users can assign a Journey Owner, who will act as the sole user responsible for the successful completion of a Journey.