The Comments feature in Salesforce allows users to leave notes on Journeys, accessible via the Comments Button. Users can create primary comments, reply to them, and delete any comment or reply. The feature supports @ mentions to notify specific Fen-X users, enhancing collaboration and communication within the platform.

Conditional values for fields within Data Groups are now supported in Salesforce. When these fields are configured in Fen-X and triggered during a Salesforce journey, the conditional values will appear in the Salesforce UI if the specified conditions are met. This feature allows dynamic, context-specific information to be displayed, enhancing the user experience with more relevant data.

The Portal Quick Link task in Salesforce allows users to link or unlink new or existing users to a Portal account directly from a Journey, provided they have the necessary permissions. Users can add or remove users by entering their email addresses, with verification steps for unverified emails and error messages for invalid or mismatched emails.

The following enhancements are now available in Salesforce:

• Uplift Entity Data Policy from v2 to v3 API - There was a bug with conditional fields in Salesforce due to a change in Fen X. The app worked correctly with v2
• Add success message when saving Data and Product tasks
• Display error messages: Labels instead of datakeys
• Display Tab name in console app as [JourneyName] | Journey
• Task Status refresh on Journeys - Extend updates to 60 seconds instead of 10
• New Request: Display Conditional fields in Search results

The following validations are now available for fields within Data Groups in Salesforce (Data Task) as configured in Fen-X: Mandatory, Regex, noFutureDates, noPastDates

Support Default Values for fields within Data Groups in Salesforce (Data Task) as configured in the Fenergo SaaS Platform.

If a document requirement for the task cannot be met, a user with the Document Management Defer or Waive permission has the option to: Defer the requirement - indicate in the system that the document cannot be collected right now but will be available at a future date. The user must specify this future date when marking the requirement as Deferred. Waive the requirement - indicate that this document will never be collected.

If a document requirement for the task cannot be met, a user with the Document Management Defer or Waive permission has the option to:

1. Defer the requirement: Indicate in the system that the document cannot be collected right now but will be available at a future date. The user must specify this future date when marking the requirement as Deferred.

2. Waive the requirement: Indicate that this document will never be collected.

If necessary, users have the flexibility to waive or defer mandatory or optional document requirements.

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.