-
Why did Salesforce get rid of S-controls?
Why did Salesforce get rid of S-controls?
-
1 Reply
-
Salesforce got rid of s-controls in favor of two new technologies, Apex Code and VisualForce. We prefer these technologies because they provide a well-defined API where we can maintain backward compatibility as we make regular changes to our UI, schema, and API. The API is versioned so even if we make changes to it, older versions continue to work just as well. S-controls may have had more flexibility as they were free to do what they wanted on the client-side, but they also frequently broke as we made simple changes to the platform.
Log In to reply.
Popular Salesforce Blogs
Agentic AI in Software Development: What’s Changing?
It seems like just yesterday when enterprises had started to embrace AI agents in full swing. Yet the fact remains these agents are quickly being…
Why Duplicate Data Is a Problem | Salesforce Guide
In the event that you follow the Optimize Sales Features for Lightning Experience trail, you know the Salesforce administrator, Maria Jimenez, at Ursa Major. She…
Handle Events in LWC | All You Need to Know
A robust framework called Lightning Web Components (LWC) enables programmers to create web apps utilising current web standards like HTML, CSS, and JavaScript. Event management,…
Popular Salesforce Videos
Learn DML Statements in Salesforce Development
In this video, We'll be learning about DML (Data Manipulation Language) in Salesforce development: We will be discussing the following things in this video: 1.…
Dynamic Action in Salesforce | Salesforce Tutorial
In this video, we are going to talk all about dynamic actions in Salesforce. 00:00 Introduction 00:57 Work with Dynamic Action 05:05 Dynamic Actions in…
Integration: MuleSoft Composer for Salesforce
What you can do with MuleSoft Composer for Salesforce Enrich your 360-degree customer view by empowering your Salesforce admins with a no-code solution for quickly…