Salesforce Spiff Release Notes for June 26, 2026

Quota Types Now Available in New Salesforce Spiff Sandboxes

Where: This change applies to Salesforce Spiff.

Why: Previously, sandboxes didn't include Quota Types from the parent environment. Quota Types weren't in the sandbox, so formulas that referenced Quota Types by ID couldn't resolve correctly. Quota Type IDs also weren't guaranteed to match between the sandbox and production, so deploying commission logic that depended on Quota Types produced errors in production. Now, when you create a sandbox, Spiff automatically copies all Quota Types from the parent environment. Cloned Quota Types have matching IDs in the parent environment, so commission logic that references a cloned Quota Type resolves correctly in production after deployment. Quota Types don't count against the sandbox transaction record limit, which frees up capacity for other transactional test data.

For sandboxes created before this update, Quota Types are removed from the record limit count the next time a Quota Type is created or deleted in that sandbox.

How: This change is automatic when you create a new sandbox—no setup is required. Quota Types aren't managed by change sets, so keep Quota Type names synchronized between the sandbox and the parent environment to avoid formula reference errors after deployment. If you rename a Quota Type in a sandbox, Spiff automatically updates formulas in that sandbox—but that rename isn't deployed to production. Quota Types created directly in the sandbox don't have a matching ID in the parent environment and you can't deploy them via change sets.

Improved Change Set Filtering and Workflow History for Compliance

Where: This change applies to Salesforce Spiff.

Why: Previously, the Inbound and Outbound Change Sets tables had no filtering options, which made it harder to find specific change sets in orgs with large deployment histories. To audit a change set's workflow activity, users consulted the System Activity Log separately. Now, two new filters help you narrow the change set list quickly, and the new History tab brings the full workflow trail into the change set modal, so you can verify submissions, validations, approvals, and deployments without leaving the page.

How: To filter the change set table by date, use the Submitted Date filter on the Inbound or Outbound Change Sets page. To filter by workflow status—for example, to show only change sets with the status Ready for Deploy—use the Status filter. To review the workflow history for a change set, click the change set name to open the modal, then select the History tab.

Track Report Processing Status in Obligation and Statement Reports

Where: This change applies to Salesforce Spiff.

Why: Previously, there was no way to tell from a report whether its data had been successfully processed or when it last ran. Admins and managers had no visibility into whether a report was current, still pending, or failing due to a data change—making it harder to trust report data or investigate discrepancies. Two new optional columns, Processing State and Last Successful Run, are now available for obligation and statement reports. Processing State shows the current calculation status of the report. Last Successful Run shows a timestamp of the last time that the report completed successfully, so you can tell at a glance whether the data reflects a recent successful run or an earlier one. Processing State has four possible values. Successful means the report ran and completed without errors. Failed means that the report previously ran successfully but is now failing, likely because of a change in the underlying data after the last successful run. Pending means that the report is queued but Spiff hasn't run the report yet. Never Calculated means that the report has never been run, and Spiff shows no timestamp.

How: On the Reporting tab, open or create an obligation or statement report. Click the columns icon next to Run & Save, search for Processing State or Last Successful Run, and click the + icon to add the column. Click Apply, then click Run & Save.