Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Salesforce Integration Changelog

This changelog tracks sanctions.io Salesforce app updates, including new features, bug fixes, and security changes. Releases are listed newest first.

To request installation links, please email your account manager directly or contact our team at help@sanctions.io.

v1.28 - (Latest)

Release date: November 3, 2026

Bug fixes

  • Fixed an issue where long API response values were trimmed before reaching the maximum field length set in Salesforce. Response values are now captured up to the maximum length for each field, which varies by field.

v1.27

Release date: October 6, 2026

New features

  • Admins can select an alternative field to use as the name for business-account screening. If that field is empty, screening falls back to the standard account name field.

v1.25 and v1.26: Adverse media screening

Release date: September 23, 2026

New features

  • Added adverse media screening added to Salesforce Integration. This includes:
    • New settings pages and a one-click adverse media screening button.
    • Two new fields on leads, contacts, and accounts for the date/time and status of the last screening.
    • A new Adverse Media Alert object and related list to store alert records.
    • A new flow action, triggers, and batch type for adverse media screening.

Changes to sanctions screening

  • Threshold minimum: Now 0.8. Previously, values below 0.8 were accepted. Values below 0.8 now return an HTTP 400 error.
  • Additional Info field: Added to sanctions screening alerts. It takes information from the API response, strips the JSON formatting, and displays key-value pairs as plain text. Response formats can vary.
  • Sanctions lists and tab labels: Added more lists and standardized tab labels to match the Watchlist coverage page. HRJ lists now have their own section and no longer need to be added as custom lists.
  • Additional response fields: Regime, Positions, Positions Start Date, and Passport are now populated when present in the sanctions response.

Upgrade notes

  • Upgrades don't automatically update the page layout for existing customers. Add the Additional Info field to the sanctions alert page layout manually.

v1.23

Release date: August 27, 2026

Security

  • Passed the Salesforce AppExchange security review. Functionality is the same as v1.22, with added security hardening.

v1.22

Release date: June 22, 2026

Bug fixes

  • Fixed a permission issue for standard users using trigger-based screening. The issue was found during v1.21 testing and was not present in earlier versions.

v1.21 (Not released)

  • Not distributed.

v1.19 and v1.20

Release date: May 29, 2026

Security

  • v1.20 includes security changes for the Salesforce security review. It was the originally intended security-review version and was iterated on from v1.19.

v1.17 to v1.19

Release date: May 19, 2026

Bug fixes

  • Fixed an issue where the entity clear email could be sent on the "no new alerts" path, not just the "no results" path, after alerts were already populated.
  • Fixed customer-reported bugs.

Changes

  • Email sending now uses the user by default instead of the org-wide email address. The org-wide address remains the fallback.

v1.13

Release date: April 17, 2026; updated May 8, 2026 as V10.5

New features

  • Person Account support: Accounts are screened automatically as individuals or entities, depending on whether they are Person Accounts or standard Accounts. Person Accounts have additional screening parameters: date of birth and year of birth.
  • Save error notifications: The screening popup shows Salesforce configuration errors that block saving a record and prompts users to contact their Salesforce admin.
  • Single-name screening: Leads, contacts, and Person Accounts can be screened with only a single name. Screening is no longer limited to records with both a first and last name.
  • Exposed Apex class method: Custom Apex classes and code can now call the full screening logic, the same logic used in Salesforce flows. Pass a List<Id> into Sanctions.sanctionsScreening.screenRecords(List<Id>). The list can contain a mix of lead, contact, and account record IDs. Screening and downstream behaviors, such as creating screening alerts, are handled automatically.

Changes

  • Batch screening query: Removed the 50,000-record limit on batch screening queries.
  • Record data refresh: The component fetches fresh data from the record each time the screening button is clicked, so name changes and other updates are captured without refreshing the page.
  • UI labels:
    • "Person Name" is now "Name" on the screening alert object.
    • "Cancel" is now "OK" on the popup when there are no results or no new results.

Bug fixes

  • Fixed an error with complex batch query inputs.
  • Fixed query change detection when the batch query is modified manually.
  • Popup error display: For both the “no result” and “result” scenarios, the popup waits to display results until the save error check is complete. The save button is usable immediately on load, and “No Results” no longer appears before a validation or save error.
  • Duplicate emails: Changed the trigger point for popup emails to prevent an edge case that could send duplicate entity clear emails.

v1.7

Release date: April 7, 2026

New features

  • Added handling to prevent screening of leads and contacts that don't have a full name. Users see a clear in-app notification when this happens.

Bug fixes

  • Fixed an issue where adding custom data sources failed with a 400 error introduced in a recent change.

Changes

  • Improved insertion triggers to handle concurrent insertions more reliably, using a queueable and batch structure depending on load.
  • Non-functional changes for Salesforce AppExchange security review compliance.

v0.37

Release date: March 24, 2026

Changes

  • Significantly increased the number of concurrent trigger-based screenings the app can handle.
  • Added support for sanctions sandbox tokens.