Spring 16 - New features

-

Spring 16 new features :


Health Check :

Do you know how secure your org is? Are you following the best security practices recommended by Salesforce? With the new Health check feature introduced in Spring 16, you can visually see how Salesforce has rated your org as per the current implementation present in it. If you are a security administrator, this tool will make your life much more easier.
To check the health score, click on Setup and type Health check is the Quick Search Bar. Click on Health Check and a report is displayed which lists out the health score of your org and the potential risk factors. The risk factors are classified as :
1) High Risk Security Settings
2) Medium Risk Security Settings
3) Low Risk Security Settings
Most of the security breaches are around the password requirements and password policies.


Global Picklist : 

Ever felt a need to share common picklist values across multiple objects? Tired of recreating the same picklist values on every object? With Spring 16, Salesforce has made it possible to define a global(universal) picklist which can be resued across multiple objects. Unlike a custom picklist which is tied to a specific object, a global picklist it defined at the organization level. Only a Salesforce admin can add to or modify its values; users can’t add unapproved values, even through the API.

Offline for Mobile (Android): 

This is the most exciting feature and I am sure many customers were looking for this. With Salesforce1 mobile app, you can now access and edit records even when you are not connected to the Internet.
Salesforce1 will automatically download the users first 5 most used object's records (30 most recent records from 5 most used objects). Records that have been previously accessed in Salesforce1 will remain available in offline mode irrespective of recent records criteria.
Alternatively, you can cache the records before going offline/airplane mode and those records will be available for you to edit. Once you are connected to the internet, your updates would be synced to the server. Server side operations such as workflow, trigger, validation rules, apex are not supported in offline mode.
Now you be might be thinking how lookup values will show up in offline mode. For example, if I am creating a contact and I need to populate account lookup. I will just type the name of Account and the value will be stored as lookup text. Lookup values will be resolved when records will be synced with server. The user will be notified if the exact match for lookup value is not found.
Also there maybe be a conflict while updating the record. For example, if I am updating the account lookup on contact in offline mode and another user has updated the same field at the same time in online mode, then what will be the output? So when the records will be synced through Salesforce1 app, Salesforce1 will notify the user with the updated value present on server and the user can make a decision to force his value or keep the updated value on the record.

Customizable left navigation menu in Lightning Experience : 

Lightning is growing at a supersonic speed and they have introuced some pretty cool features in this release. One of them is the customizable left nav menu. Earlier it was not possible to customize the left nav menu, but now you can configure the options you need to see in the left nav menu. You can create navigation menus and assign it to required profiles.

Comments

Post a Comment

Popular posts from this blog

Salesforce Lightning: Countdown timer

-
Image
Today we will have a look at how to create a lightning component for countdown timer which can be used on pages where an operation needs to be completed within a specific time period. Example, an online exam or a banking transaction which expires after a specific time period. The component contains a datetime field which represents the end time. Once the user selects the date and time and clicks on Start Timer button, the countdown timer will start. Below is the lightning component: CountdownTimer.cmp <aura:component implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId" access="global" >       <aura:attribute name="endTime" type="String"/>       <aura:attribute name="timeLeft" type="String"/>       <lightning:tile label="Time Left" class="slds-page-header">         {!v.timeLeft}     </lightning:tile>
Read more

Salesforce Hacks: System.LimitException: Too many queueable jobs added to the queue: 2

-
Queueable classes are great to use and provides a wide range of advantages when compared to future methods. But there are some undocumented limitations which you will come across if you are using Queueable classes extensively inside your batch classes. Lets take an example of badly written trigger on Account.  trigger AccountTrigger on Account (before insert) {     for(Account acc: Trigger.new){         Database.executeBatch(new CreateContactBatch(), 2);     } }   The above trigger calls a batch class for every account record that gets inserted in database. So if you insert N accounts in a single transaction via dataloader or anonymous block or through any other means, the trigger will execute the batch class N number of times. Below is the code for batch class: global class CreateContactBatch implements Database.Batchable<sObject> {          global Database.QueryLocator start(Database.BatchableContext BC) {         String query = 'SELECT Id FROM Account'
Read more

Building an Org Role Hierarchy component in LWC

-
Image
You might have observed that the role hierarchy which gets displayed in the org (Setup > Users > Roles) is still displayed using a VF component. Today, we will see how to create the same role hierarchy using LWC and Apex. LWC provides us with a component called lightning-tree which displays a nested tree. We will make use of this component to display the role hierarchy in a tree structure. In Apex, we will query all the user roles and form a JSON structure which will be fed to the lightning-tree component. Let's first see the LWC component - roleHierarchy: roleHierarchy.html <template> <div class="slds-p-around_medium lgc-bg"> <lightning-tree items={roles} header="Roles"> </lightning-tree> </div> </template> Here we have used the lightning-tree component which will display the data in a tree structure. The items attribute is of type Object which has nested i
Read more