Following are few important highlights of Salesforce Summer'19 release
Note : Beta features may not be available in actual release
➤ Enhanced Related List
Cool feature from Salesforce. When Enabled, Related list for a particular record can be sorted by its columns, sized and can show upto 10 columns at a time. You can also perform some mass actions within it like within contact enhanced related list on account, you can select few contacts and add them all to a campaign.
How to enable: From the related lists component in the Lightning App Builder, select Enhanced List from the Related List Type dropdown (1). You can customize how many records to display at once, and choose whether to show the list view action bar.
➤ Quick filters for Related List
Use quick filters in your related lists to find the data that you’re looking for. Related list quick filters are different from regular list view filters in that they aren’t saved, persist only throughout your current session, and can’t be shared.
➤ Search Picklist values in List Views
This new update will make Picklist values searchable in list view.
➤ Salesforce Surveys: Free Sending, Customized Email Invitations, and an Improved User Experience
1. Send Surveys for free
Sending survey from salesforce become free. Any user with following profile can send unlimited surveys without any additional cost.
- Contract manager
- Marketing user
- Standard user
- System administrator
2. 300 Survey Responses free per org. For receiving more than 300, You need to purchase Survey responses add-on pack.
3. Send customized emails that contain a link to a survey question or to launch a survey. You can send email invitations to leads, contacts, and users in your org. To email a survey invitation, in the active version of the survey, click Open. On the Send tab, click Send Email.
4. You can now generate a unique survey invitation for a lead directly from the record by clicking Get Survey Invitation.
➤ (Beta) Access Lightning Experience from Safari on iPad Devices
With this setting enabled, Salesforce users will be able to browse using full desktop version of Salesforce from their iPad devices.
Recommended browser in iPad will be Safari.
How to enable: In Setup, enter Lightning Experience in the Quick Find box, and then select Lightning Experience on iPad Browsers
Recommended browser in iPad will be Safari.
How to enable: In Setup, enter Lightning Experience in the Quick Find box, and then select Lightning Experience on iPad Browsers
➤ Record Page View Setting
1. Full View for Record pages
A new type of record layout has been added which is similar to Classic. In this, all the record details and related list will be displayed on same page. You can select this layout by searching Record Page Settings in setup.
2. Default Activities View
Now you can decide which type of layout will be default for Activities weather it is Related list type or Timeline type. Go to Record Page setting in Quick find box in Setup.
➤ Easily Add Images in Email from Salesforce.
Whenever you send email from record pages, New image icon has been added with which you can easily add images in Email Message. The images file can be on the web, Salesforce files or your computer.
➤ Merge Cases into a Single Record (Beta)
If you have duplicate cases or cases that you want to merge into a single case, you can now merge two or three cases into one master record. When you merge cases, the master record is updated with your chosen field values. Most related lists, feed items, and child records are merged into the master record. The master record keeps the Chatter feeds, your values for read-only and hidden fields (except Created Date and Created By), related items, and security.
➤ Set Up Skills-Based Routing Without Code Using Attribute-Based Routing (Beta)
Now use a setup flow to associate an object’s field values with the skills needed to route a work item to the right agent. It’s not quite as flexible as using the API, but it’s easy to set up and very powerful.
How: To route work by skills, define the mappings between work-item field values and skills. Create one attribute mapping set for each object. For example, for the Case object, you could create a mapping set that includes the Case Reason, Case Type, and Escalated fields. Then map the field values to skills so that the work item is routed to the agent with the right skills to handle the case. You can also specify skill levels and whether a skill is additional and can be dropped if necessary to route the work item more quickly.
➤ New Salesforce CMS (Beta)
CMS for Community Cloud has evolved into something bigger and better: Salesforce CMS. Share content across communities more easily, and collaborate with local and regional teams on projects. Create content outside of your communities in CMS workspaces. And take advantage of role-based access to control content authoring and settings access in Salesforce CMS. Salesforce CMS app is available automatically to all Communities Cloud customers.
Why:
1. With Salesforce CMS, authoring can be done outside communities, which has some nice perks.
2. Assign content access with new contributor roles that don’t require administrative access to your communities.
3. Create one or more CMS workspaces to organize your content and share it across multiple communities at once.
4. Within your individual communities, customize the experience for your users.
5. Reuse content published from one or more CMS workspaces.
6. Curate content into collections that automatically refresh as content changes.
7. Reuse your existing CRM data, such as inventory, to help users find what they need.
8. Connect to an external CMS to reuse content you already host elsewhere with CMS Connect.
How: To see Salesforce CMS in the App Launcher, Communities must be enabled in your org and users must have Salesforce CMS enabled in the Custom App Settings of their profile in Setup.
2. Assign content access with new contributor roles that don’t require administrative access to your communities.
3. Create one or more CMS workspaces to organize your content and share it across multiple communities at once.
4. Within your individual communities, customize the experience for your users.
5. Reuse content published from one or more CMS workspaces.
6. Curate content into collections that automatically refresh as content changes.
7. Reuse your existing CRM data, such as inventory, to help users find what they need.
8. Connect to an external CMS to reuse content you already host elsewhere with CMS Connect.
How: To see Salesforce CMS in the App Launcher, Communities must be enabled in your org and users must have Salesforce CMS enabled in the Custom App Settings of their profile in Setup.
➤ Require TLS 1.2 for HTTPS Connections (Critical Update)
To maintain the highest security standards and promote the safety of your data, Salesforce is disabling the older Transport Layer Security (TLS) 1.1 encryption protocol. Starting in October 2019, all inbound connections to or outbound connections from your Salesforce org must use TLS 1.2. Verify that your browser access, API integrations, and other Salesforce features are compliant with TLS 1.2.
➤ Prevent Creation of Function Expressions in Dynamically Created Aura Components (Critical Update)
To improve security and stability, this update prevents attribute values passed to $A.createComponent() or $A.createComponents() from being interpreted as Aura function expressions.
Where: This change applies to orgs with Aura components in Lightning Experience, Salesforce Classic, and all versions of the Salesforce app.
Where: This change applies to orgs with Aura components in Lightning Experience, Salesforce Classic, and all versions of the Salesforce app.
Why: When the critical update is activated, using the key-value pair {"exprType": "FUNCTION"} in an object passed as an attribute value to $A.createComponent() or $A.createComponents() throws an error instead of triggering unpredictable behavior.
➤ Reference Custom Metadata Type Records in Process Builder
Reference custom metadata type records from a Process Builder formula to automate your business processes, reusing functionality that you define. To change a value, you can update it in the custom metadata type instead of in your process and any hard-coded formulas that your process uses.
Why: Let’s say that you want to send an email or trigger some other action when the amount in the Account object’s Annual Revenue field is greater than $100,000.
1. Create a custom metadata type.
2. Create a custom field for your type named Minimum Revenue.
3. Create a record for your type, and name it FY20.
4. From System Variables, reference the custom metadata record in Process Builder.
$CustomMetadata.CustomMetadataTypeAPIName.RecordAPIName.FieldAPIName
1. Create a custom metadata type.
2. Create a custom field for your type named Minimum Revenue.
3. Create a record for your type, and name it FY20.
4. From System Variables, reference the custom metadata record in Process Builder.
$CustomMetadata.CustomMetadataTypeAPIName.RecordAPIName.FieldAPIName
➤ Require TLS 1.2 for HTTPS Connections (Critical Update)
To maintain the highest security standards and promote the safety of your data, Salesforce is disabling the older Transport Layer Security (TLS) 1.1 encryption protocol. Starting in October 2019, all inbound connections to or outbound connections from your Salesforce org must use TLS 1.2. Verify that your browser access, API integrations, and other Salesforce features are compliant with TLS 1.2.
No comments:
Post a Comment