Versions and Support
Propper for Salesforce uses semantic versioning. Support is tracked per
minor line, the 1.2 in a version like 1.2.0, so guidance about a version applies to the
whole 1.2 line.
Version numbers here are specific to the Salesforce package and are unrelated to the dated version
numbers on the Propper platform release notes, which use a
calendar scheme such as 2026.08. The two move independently, so a platform update does not change
which Salesforce package version you are running, and a package upgrade does not change your platform
version.
Current version
| Version | Status | Available |
|---|---|---|
| 1.2.x | Beta | Propper for Salesforce beta |
Propper for Salesforce is not yet listed on Salesforce AppExchange. The current version is a beta, installed from the link above into sandbox, Developer Edition, and scratch orgs only, not a production org. As a beta it is not yet covered by the support commitment below.
Support commitment
Our 12-month support commitment for each minor version takes effect from a named future version. Until then, fixes ship on the current version, and we recommend staying current.
When the commitment takes effect, each minor line will be supported for at least 12 months from the date it is published on the Salesforce AppExchange listing. A line remains supported while it is the current version.
What a supported version receives
- Security fixes
- Data-integrity fixes
- Correctness fixes for issues that block a core task
New features ship on the current version only. If you need a fix that is not in one of the categories above, upgrading to the current version is the route to it.
Upgrading
Installing a newer version over an existing one is normally a managed upgrade that keeps your configuration, Send Configurations, and agreement records in place. See Setup and administration for the install and upgrade steps.
For what changed in each version, see the release notes.