Review your Salesforce org to identify all active S-Controls. Then, select Where it is used option on each S-Control component to track its references across the org.
Last updated on
Feb 17, 2025
Salesforce deprecated S-Controls in 2010, and it will be fully removed from the Acrobat Sign for Salesforce Package by July 2025.
Starting in July, new versions of the Acrobat Sign for Salesforce package will no longer support S-Controls, which may break any custom functionality that relies on them. However, existing versions will remain unchanged and continue to include S-Controls.
The following S-Control components from the package have already been addressed and require no further action:
- AboutEchoSign
- Delete_Agreement
- EchoSignAdmin
- RefreshStatus
- SendReminder
- SendforSignature
If you currently use the extended or created S-Controls, follow these steps to migrate to the supported technologies for continued functionality.
-
-
Select one of the following migration paths based on the S-Control's functionality:
- Visualforce Pages: For custom user interfaces (UIs) in Salesforce Classic. Refer to the Visualforce Guide for details.
- Lightning Web Components (LWC): For modern, high-performance UIs in Salesforce Lightning. Refer to the LWC Guide for details.
- Apex Classes: For backend business logic. Refer to the Apex Guide.
-
Rewrite your existing S-Control logic to make it compatible with the chosen platform.
-
Test the new solution and deploy it to your production environment.
