Summary
We have updated the Elements for Salesforce managed package (v6.24) to Salesforce's second-generation packaging model (2GP). This change affects only the packaging model itself — no functionality, data, configuration, or metadata is altered.
What is changing
The Elements managed package currently uses Salesforce's first-generation packaging model. We are moving it to the second-generation model.
After the upgrade, the package appears as a second-generation package in Setup → Installed Packages. Future updates and fixes are delivered through the second-generation model.
The package version does not change during this upgrade — you remain on 6.24.
What is not changing
The upgrade does not:
Remove any metadata.
Remove any dependencies.
Change any functionality — the package works exactly as it does today.
Change your data, configuration, or permissions.
Change the package namespace or component API names, so your integrations and any references to package components continue to work.
The only difference is the packaging model underneath. There is no functional change for your users.
⚠ Known Issue: Upgrade Fails with "DeactivationDependentException"
A small number of orgs are hitting an upgrade failure. During the 1GP → 2GP migration, Salesforce attempts to deactivate the old Package License Manager system user associated with the 1GP package. Salesforce will not allow a user to be deactivated while that user is still referenced as a recipient on an active Email Alert.
In orgs that have been using Elements for some time, you may still have two components that were deprecated and removed from the package in later releases:
A Workflow Rule named
EvaluateDiagramId(Object: Elements Map)An Email Alert named
Is workflow rule fired, which lists the Elements for Salesforce user as a recipient
Because the Email Alert still references the Elements for Salesforce user, Salesforce blocks the user deactivation step and the entire package upgrade fails.
Please check for and remove these components before 21 Aug 2026 6pm PDT
Before running the upgrade link (sandbox or production), please check whether your org has these components and remove them:
Log in to the org you're about to upgrade (sandbox first, then production).
Go to Setup > Workflow Rules.
If present, locate the Workflow Rule EvaluateDiagramId (Object: Elements Map). Deactivate it, then delete it.
Go to Setup > Email Alerts.
If present, locate the Email Alert Is workflow rule fired.
Delete this Email Alert. This component was removed from the managed package in a later release (it will show a yellow "removed from managed package" banner in Setup), so it is safe to delete.
Alternatively, if you'd prefer not to delete it, you can instead edit the Is workflow rule fired Email Alert and simply remove the Elements for Salesforce user from its Recipients list.
Why we are making this change
Second-generation packaging gives us access to Salesforce capabilities that are not available on the first-generation model. Upgrading now is what allows us to deliver upcoming improvements, including:
More secure authentication for background jobs (using Salesforce Named Credentials). This resolves an issue where orgs with enforced session settings could see jobs not run or data not process. This fix is delivered in a later version (6.25) that requires the second-generation package.
Alignment with Salesforce's move from Connected Apps to External Client Apps, which Salesforce requires and which is only supported on second-generation packages.
The upgrade itself introduces no visible change. It is the foundation for the improvements above.
Timeline
Now – 21 August 2026: Remove the Workflow Rule and Email Alert described above if they exist in your org.
22 August 2026 – 6 September 2026: Elements will migrate all orgs after business hours during this two-week period.
Support for the first-generation package is ending
Once this migration begins, we can no longer publish updates or fixes on the first-generation package. To continue receiving support, fixes, and new features, your org needs to be on the second-generation package.
If you report an issue while still on the first-generation package, the resolution will require upgrading to the second-generation package first.
Is the upgrade reversible?
No. Once your org is upgraded to the second-generation package, it cannot be reverted to the first-generation package, and all future updates are delivered on the second-generation model. This is why we ask you to validate in a sandbox before upgrading production.
Frequently asked questions
Will I lose any data or configuration? No. Nothing in your org changes except the packaging model.
Do I need to reinstall the package? No. This is an in-place upgrade. You keep the same version (6.24).
Does the version number change? No. You stay on 6.24. The next version (6.25) will be released later and adds the improvements described above.
Will my integrations or customizations break? No. The namespace and component API names are unchanged, so references and integrations continue to work.
Do I have to upgrade? Yes. Continued support, fixes, and new features require the second-generation package.
Need help?
If you have questions or run into any errors during the upgrade, contact us at support@elements.cloud before upgrading your production org.