General

S-Controls are coming back to Salesforce!

Salesforce has announced that S-Controls are coming back to Salesforce classic. For those who don’t know what S-Controls are, they were the technology before VisualForce and allowed you to create webpages and use the Salesforce JavaScript APIs to communicate with Salesforce (hence the S in S-Controls). Around 10 years ago Salesforce stopped Salesforce customers from creating new S-Controls as VisualForce had replaced the need for S-Controls, but I still find S-Controls in customers orgs. You can still edit and make changes too… well that was until this announcement!

Why are Salesforce re-enabling S-Controls?

It’s all due to Lighting! Lightning is a JavaScript framework and by bringing back S-Controls, Salesforce will allow developers to develop JavaScript based Lightning apps directly in Salesforce classic without the need of VisualForce. S-Controls are much lighter than VisualForce so you can illuminate the need for an Apex controller or even VisualForce markup! It also means new developers coming to the platform with a client who is still using the Classic UI can skip learning VisualForce/Apex and jump straight into the JavaScript world that is Lightning & S-Controls.

New ‘Add Lightning Component’ Button

New ‘Add Lightning Component’ Button

So Salesforce as expanded the S-Control functionality to allow you to easily add Lightning Components into your S-Control using the ‘Add Lightning Component’ Button (see pic).

Adoption, Adoption, Adoption

I think also another reason for re-enabling S-Controls is to allow developers & businesses a softer introduction into Lightning components & development. Lightning components/apps can be created directly in the Classic UI using S-Controls or just using regular old JavaScript. It also means that those orgs still using S-Controls can refactor the controls into Lightning components/apps more quickly without the need for VisualForce.

Click here for some AWESOME examples!!

+

Yes, well I couldn’t resist! 🙂 S-Controls have been consigned to history and now with Lightning replacing VisualForce there is NO CHANCE S-Controls will see the light of day again.

So in conclusion, I think it makes a lot of sense it. Let’s make S-Controls great again! 😉

Apex, Development

Create Lightning with Lightning & IoT

If you came along to my talk “Create Lightning from Lightning & IoT”, thanks a lot! Here is my follow up post. Unfortunately in the time I couldn’t get through everything, so as promised I’ve included in the presentation slides for the Process builder code and how to expose your Apex code functionality to Process Builder.

Process Builder allows admins or click developers to build quickly processes based on their particular logic. For example, we could hook up the Lamp to flash when a high priority Case comes in. We don’t need to worry about when they need to flash the light, we are just exposing the ability for them to plug it into their process whenever they want it to fire.  Read more

Apex, Development, General
  • Salesforce Lightning UI and what it means for developers!
  • Salesforce Lightning UI and what it means for developers!
  • Salesforce Lightning UI and what it means for developers!
  • Salesforce Lightning UI and what it means for developers!
  • Salesforce Lightning UI and what it means for developers!

Salesforce Lightning UI and what it means for developers!

It can be summed up in one word. Javascript. It’s a hell of a tide change for Salesforce. So long Visualforce, hello lightning components! They are coming mainstream!

So, what does this mean for developers? Is Salesforce switching off the old UI? No… well not yet, too many companies have invested too much in it and VisualForce. Are they switching off Visualforce? will you still be able to develop VisualForce? Yes of course.

The Lightning UI is still a little way off from being complete. One of the reasons is that it doesn’t have a vast amount of components that VisualForce has, but this is defiantly going to change! With Lightning Components your creating a whole application rather than just a page in VisualForce, so the complexity is higher than regular VisualForce. Read more