{"id":6298,"date":"2017-10-04T03:53:56","date_gmt":"2017-10-04T03:53:56","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=6298"},"modified":"2017-10-04T03:57:04","modified_gmt":"2017-10-04T03:57:04","slug":"salesforce-winter-18-release-my-favorite-features","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/salesforce-winter-18-release-my-favorite-features\/","title":{"rendered":"Salesforce Winter 18 Release \u2013 My Favorite Features"},"content":{"rendered":"

There are many cool features features in Winter 18, however I would be listing only my favorite top picks from 589 pages<\/a> of release notes. Would suggest to through this post<\/a> to understand Sandbox readiness dates for Winter 18.<\/p>\n

You can check materials of this meetup as well organized by Amit<\/a>, where I shared my favorite Winter 18 feature with sample code.<\/p>\n

    \n
  1. \n
    New Lightning Base Components<\/h5>\n<\/li>\n<\/ol>\n

    Lightning Base components are out of the box component created with Salesforce Lightning Design System CSS. If there are no Lightning Base components, You would need to use aura or HTML components and write custom CSS to make look and feel similar to Lightning Experience. Base component starts with\u00a0lightning:\u00a0<\/strong>namespace. There are many new Base components introduced like\u00a0lightning:datatable ,\u00a0 lightning:checkboxGroup ,\u00a0lightning:dualListbox ,\u00a0 lightning:progressIndicator ,\u00a0lightning:progressBar,\u00a0 lightning:slider.\u00a0<\/strong>Recently only I blogged about Read only Chevron Component<\/a> with mountains of code. Even though we are using this component for last 6 months however If my project could have waited, then all I had to use is 5-6 lines of code using\u00a0lightning:progressIndicator.<\/strong><\/p>\n

    2. Component Library (Beta)<\/h5>\n

    We can already see all standard and custom component information using https:\/\/<myDomain>.lightning.force.com\/auradocs<\/span><\/em> URL. However, as part of Winter 18 release, Salesforce came up with revamped website just like Lightning Design System<\/a> to show code snippets on how to use Lightning Components. You can navigate to Component Library using https:\/\/<myDomain>.lightning.force.com\/componentReference\/suite.app<\/span><\/em> URL.<\/p>\n

    3. Lightning Data Services (GA)<\/h5>\n

    We are hearing about Lightning Data Services<\/strong> from almost last one year and finally its generally available for use. You can check this blog post<\/a> on how to use it.<\/p>\n

    4. Conditional Rendering of\u00a0Lightning Component\u00a0in App Builder<\/h5>\n

    One of my favorite feature. From Winter 18 on wards, we can add a condition in Lightning Page builder to decide when to render Lightning Component. More power to point and clicks and easy to manage rendering of components without any code change or deployment.<\/p>\n

    \"Winter
    Winter 18 – Conditional Lightning Component Render – App Builder<\/figcaption><\/figure>\n
    5. Lightning Component Payload Increased from 1 MB to 4 MB<\/h5>\n

    Lightning Component batches multiple Apex calls into single queue to avoid multiple Server trips. This payload includes all data serialized into JSON, previously only 1 MB of data could be serialized which is increased to 4 MB. Request payload limit of\u00a0Javascript Remoting\u00a0<\/strong>is also increased from 1 MB to 4 MB.<\/p>\n

    6. Automatic Styling of Visualforce Pages (Beta)<\/h5>\n

    Using\u00a0lightningStylesheet\u00a0<\/strong>attribute in apex:page, now we can easily convert old classic Salesforce pages to Lightning design System. Right now this feature is in Beta. If existing Visualforce has custom CSS then it may conflict with Salesforce Lightning Design System CSS and may not work properly, word of caution. You can see it in action here<\/a>.<\/p>\n

    7. Debug Logs<\/h5>\n

    Before Winter 18, We could have only 50 MB of debug logs for infinite time. Winter 18 on wards, we can generate logs of 250 MB every 15 minute. Only catch is, Logs would be available for 7 days. Still its great feature in complex customized organization to troubleshoot issues on basis of debug logs.<\/p>\n

    8. Flow as Object Specific Action (Beta)<\/h5>\n

    We can invoke flow directly from record page using Lightning Action. This is in Beta right now. Previously after creation of flow, we had to wrap up flow in Visualforce page and then use it anywhere else. I think, this feature will for sure increase adoption of flows between Salesforce admins.<\/p>\n

    9. Embed Flow directly in App builder and set variables<\/h5>\n

    We can embed any flow directly in App builder using\u00a0Flow component.\u00a0<\/strong>We can also decide One vs two column layout. We are able to set variable values as well in Flow as shown in below image<\/p>\n

    \"Flow
    Flow in Salesforce App Builder<\/figcaption><\/figure>\n
    10. Add Flow in Lightning Component<\/h5>\n

    New Lightning Base Component\u00a0lightning:flow<\/strong> has been introduced in Winter 18 which can be used to embed flow anywhere in Lightning Application.<\/p>\n

    11. Custom Template<\/h5>\n

    Now we can define custom templates using Lightning Component for record, app or home pages. There are new interfaces and tags introduced for .cmp and .design bundles of Lightning to achieve custom template. You can watch recorded video shared on meetup<\/a> or read more here<\/a>.<\/p>\n

    \u00a012. Deterministic Encryption in Shield (Pilot)<\/h5>\n

    Deterministic encryption\u00a0lets you filter encrypted data in reports, list views, and WHERE clauses in SOQL queries. It\u2019s also compatible with Unique and External ID fields and custom indexes. Right now its in pilot mode and to enroll, we need to contact Salesforce Account executive. You can read this post to know more about capabilities of Shield as a beginner<\/a>.<\/p>\n

    13. Shield Improvements<\/h5>\n

    Below major Improvements are made in Shield<\/p>\n