Medallia for Salesforce 3.0 release notes

Released starting 13 February 2024

Medallia recommends that Customers upgrade to this release of Medallia for Salesforce to take advantage of enhancements and bug resolutions.

Customers with versions prior to 3.0 may log a Support case or contact their Medallia Services partner to obtain an upgrade URL or request a push upgrade.

Release highlights

  • Deprecated fields — Updated the labels on Medallia Feedback Header fields and removed access to deprecated fields from Medallia permission sets. Fields that have been deprecated now appear as:

    • Medallia_Feedback_Header__c (object)

      • Completed Survey Count (deprecated field)

      • Detractor Count (deprecated field)

      • Promoter Count (deprecated field)

      • Sum of Scores (deprecated field)

      • NPS (deprecated field)

        Note: SFDC permissions granted to admins allow system administrator profiles to view and access these fields. However, standard users and other non-admin users can no longer access or view them.

  • Queueing — Updated the Queueing service to leverage SFDC platform features. For information, see Configuring the Queueing service.

    • Queueing components updated to SFDC API v60.0.

    • Added Minimum Queueable Delay in Minutes custom setting — which sets the minimum delay between queueable transactions — to Medallia settings. Its default value is 1, which means that the Queueing service executes 1 item per minute.

    • Implemented retry mechanism logic in Queueing service.

    • Updated the Queueing service to leverage configurable queue sizes.

  • Logging — Updated the Logging service to leverage Platform Events. For information, see Configuring the Logging service.

    • Toggleable Logging service — Enable or disable Medallia Logging.
    • Configurable Log Pruning — Set the maximum number of logs to retain, the Logging service automatically deletes log records when the maximum number of logs is exceeded.
    • Log to System Debug — When you select this option, information generated by the Logging service is recorded in debug logs.
    • Bypass Platform Events — The Logging service can bypass Platform Events when creating log records. However, this reduces the quality and level of detail of generated logs.

Resolved issues

  • Fixed bug that allowed duplicate queueable jobs to be enqueued.