Skip to main content

Lightning Experience Development : User Interface Development Consideration

Note: All credit goes to Salesforce, I am just a developer who enjoy playing trailhead and try to make note to myself.

Two models of developing web app
Page Centric web application model
  • great to serve basic functionality.
  • not offer great user interactive experience
  • server side generate user interaction

App Centric mode
  • great user experience
  • client side
Three options that offered by Salesforce

Classic Visualforce

  • UI Generation - Server-side
  • Data and Business Logic-Apex standard or custom controller
  • Workflow
    1. User requests a page
    2. The server executes the page’s underlying code and sends the resulting HTML to the browser
    3. The browser displays the HTML
    4. When the user interacts with the page, return to step one.
  • Pros
    • Tried and true model
    • Easy to implement for greater productivity
    • Naturally splits large applications into small, manageable page
    • Has built-in metadata integration
  • Caveats
    • Limited interactivity (aside from added JavaScript functionality)
    • Higher latency, which degrades mobile performance
Visualforce as a JavaScript Application Container
-Empty visualforce with javascript code.In other word, Visualforce just add as javascript container.
  • UI Generation -Client-side (mostly JavaScript)
  • Data and Business Logic- Remote Objects or JavaScript Remoting
  • Workflow
    1. The user requests the “empty” Visualforce page containing only JavaScript includes
    2. The page is returned to the browser
    3. The browser loads the JavaScript application
    4. The JavaScript application generates the UI
    5. When a user interacts with the application, the JavaScript modifies the user interface as needed (return to the previous step).
  • Pros
    • Enables highly interactive and immersive user experiences
  • Caveats
    • Complex
    • No built-in metadata integration
    • Lack of an integrated developer experience. The Force.com Developer Console doesn’t explicitly support these JavaScript applications. Need to store javascript library in Static Resource
Lightning Components
  • UI Generation-Client-side (JavaScript)
  • Data and Business Logic-Apex controller
  • Workflow
    1. The user requests an application or a component
    2. The application or component bundle is returned to the client
    3. The browser loads the bundle
    4. The JavaScript application generates the UI
    5. When the user interacts with the page, the JavaScript application modifies the user interface as needed (return to previous step)
  • Pros
    • Enables highly interactive and immersive user experiences
    • Aligns with Salesforce user interface strategy
    • Built on metadata from the foundation, accelerating development
    • The Developer Console supports Lightning components, so there’s an integrated developer experience
  • Caveats
    • Higher learning curve compared to Visualforce
    • Higher complexity than Visualforce—you’re building an application, not a page
    • Since Lightning components are new, there are still some features that aren’t supported
    • There are a limited number of out-of-the-box components
Salesforce Trailhead Link

Comments

Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {