Skip to main content

The AngularJS angle to Visualforce

If someone had mentioned that I would be working on AngularJS a couple of months back, I would have laughed of with that idea. I am a platofrm purist and can work wonders on the platform. Perhaps use jquery for the little magic tricks here and there but thats there. However, as it happened a few weeks back I was introduced to the AngularJS and I cannot be more excited about the technology. A couple of nights in the past I have been deep diving into EggHead to learn AngularJS and have seen in wonder the possibility of Angular $Scope powered with visualforce platform.

After dabbing myself into a bit of Angular, here is first thought on the technology.

The easiest way to implement angular is to include the ng-app on the Apex:page

<apex:page applyhtmltag="false" showheader="false" sidebar="false" standardstylesheets="false">
<html lang="en" ng-app="myApp" ng-controller="AngularController">

There are two major things you need to handle while using Angular:

  1. The template/ CSS/ JS
    • Most Angular template are not single page document and hence you will have to put in a bit of a effort in converting them into Visualforce by using static resources
    • You could also use Apex:composition to create a composition template.
  2. The Apex code/Database handling
    • The best way to work with Angular data is visualforce remoting. You can call Apex methods using Visualforce Remoting and store the values in JSON objects. 
    • Another way to call Apex method is using rest based Api. You can return values and store them in JSON objects for processing.

Where does it go from here? Why use Angular?

There are various scenarios when you will use Angular. If you are keen on building a webpage with mimimum effort. The future expansion of angular code is easy. If you wish to use bootstrap-angular elements like the ever elite DataTables or you are a nerdy person (like me) who does not want simple things out of life.


There some planned updates by Salesforce on Angular front but for now all is safe harbor. Angular is easy to use as visualforce component and you can leard a lot of

Code Samples?

I am still dabbing into the thing for a project and have no time to prepare separate code samples but ill do other post to create samples on Angular. You can however have a look at other community authored pages for code Samples

There are some dreamforce updates related to Angular, if I come across the post will be updated.


Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…