The list of Winter ’18 features below only apply to both Salesforce Classic and Lightning Experience.
There are additional Winter ’18 features available to Lightning Experience only and Salesforce Classic only. Visit the Winter ’18 Release Highlights post.
1. Orgs with Person Accounts enabled can now define contact sharing rules and manually share business contacts in Org Wide Default Settings.
2. Omni-channel enhancements:
- The maximum queued work items from 5,000 per hour to 15,000 per hour.
- Delete user presence statuses using version 41.0 of the SOAP API.
- (Beta) Omni-channel supervisors can filter agent views to show the appropriate groups of agents.
- Your agents can stop spammers by blocking their the IP address, just like in Live Agent. To do so, enable visitor blocking in your Live Agent configuration.
- Records created from the snap-in pre-chat form are automatically attached to the chat transcript.
4. For those orgs using Chatter, you can set your out of office on your user record. Go to Chatter Settings and enable the Out of Office. You can set the out of office start/end date and message.
5. Create and collaborate on Quip documents in Chatter, Files Home and Files related lists.
6. Visual flow enhancements:
- Use Translation Workbench to translate flows and maintain translations across flow versions. No need to copy flows anymore.
- (Beta) You can pick from a list of available active screen flows when creating a flow action instead of providing the flow URL.
- Configure flow to wait for a platform event to occur, inside or outside of your Salesforce org, in a Wait flow element.
- Maximize your flow game. You can now add flows to custom components and apps, using the lightning:flow Lightning component. Invoke flow from a visualforce page with the Lightning skin by using a flow lightning component.
- Embed flows in your community!
- Pass picklist and multi-picklist values in a flow URL so you can use the same flow URL regardless of whether it’s used in Classic or Lightning.
- You can now reference encrypted fields, in flows, excluding filters and sorting.
7. Process Builder enhancements:
- Trigger processes with platform events. Create a process that starts when A platform event occurs. Then, select a platform event and match the event to a record. Continue to configure the process as usual.
- Select User and Queue by name, not just ID. Note: For any user/queue used in a criteria now or immediate/scheduled action created before Winter ’18 that you would like to update to reference the name, you will need to delete the row and create a new one.
- You can now reference encrypted fields in your processes, except in filters in the Update Records action.
8. Collaborative forecasting is available in Sales Console.
9. Salesforce Connect enhancements:
- Use Database.QueryLocator to access external objects from batch Apex, Note: several actions need to happen to use this.
- Use the Salesforce Connect Validator app, available from Salesforce Labs on AppExchange, to test out your org’s interaction with external object data.
- (Pilot) Audit historical activity of your org’s access to external object data with event log files
10. (Beta) Create a custom field using the time field type to track time that is not specific to a single date. In addition to the use of TIMEVALUE and TIMENOW functions in your formulas, you can also use the new HOUR, MINUTE, SECOND and MILLISECOND functions.
11. Limit increase for hourly scheduled workflow triggers. New orgs can use up to 1,000 workflow time triggers per hour. For orgs created prior to Winter 18, contact your Salesforce representative to update the limit.
13. Salesforce Developer Experience (Salesforce DX) will be generally available in mid-October 2017. Salesforce DX provides an integrated, end-to-end life cycle designed for high-performance agile development, moving the source of truth from the org to a version controlled system. For more information on what Salesforce DX can provide, access the release notes.
14. Security and Authentication enhancements:
- Logout of all apps with a single logout (SLO). For example, a user is logged out from all connected apps (service providers or relying parties) when they log out of the identity provider; or they log out of an app, they are logged out of the identity provider and all registered connected apps.
- Update your login screens to the Lightning runtime by selecting “Render Flow in Lightning Runtime.”
- Named Credentials: You can now deploy named credentials via change sets, packages or Metadata API. Additionally, Named credentials authenticating to external systems must have a URL that begin with https://.
- Enable additional security measures such as content sniffing protection, cross-site scripting protection and referrer URL protection on visual force pages, Force.com sites and communities.
- HSTS (HTTP Strict Transport Security) will redirect browsers to HTTPs on all visualforce pages (cannot be disabled). Administrators can enable HSTS for communities and Force.com sites.
15. Encryption enhancements:
- You can encrypt more standard fields on accounts, contacts and leads.
- (Beta) You can encrypt the Opportunity Description and Next Step fields by contacting Salesforce.
- (Pilot) You can encrypt the Opportunity Name field sandbox and developer edition environments by contacting Salesforce to participate in the pilot.
- Mass encryption and decryption of Chatter data is now generally available.. The following are encrypted: feed posts and comments, feed questions and answers, link labels and URLs, feed polls and poll choices and content from your custom Rich Publisher Apps.
- (Pilot) Salesforce uses a new deterministic encryption scheme with Platform encryption so you can filter encrypted data in reports, list views, and WHERE clauses in SOQL queries.
- (Beta) The Encryption Statistics feature shows how much of data is encrypted with an active tenant secret.
- (Beta) Require high assurance session for key management activities: Ease your security concerns by setting up 2FA for those performing key management tasks like generating, rotating, or uploading keys and certificates.
- Track encryption key management tasks in event monitoring logs.
- Using the EventLogFile event monitoring log, track which user provided search terms and search results users click on. Note: These events are available in the API, but not in the Event Monitoring Analytics app.
- Use the Knowledge Article View event type in the EventLogFile standard object to track user Knowledge article views.
- The UI tracking event type is retired. To track web clicks, performance, and errors in Lightning Experience and Salesforce1, use the Lightning Experience event types.
16. Development enhancements:
- Debug logs: The 50 MB limit has been removed and there is now a 7-day storage limit.
- Custom big objects (generally available) gives you the ability to to store and manage huge amounts of data (up to 1 billion records). Access the release notes for more information.
- 30 new base lightning components are available!
- Use Lightning Data Service (LDS) to load, create, edit, or delete a record in your component, without using Apex code. LDS is similar to the Visualforce standard controller, providing access to the data displayed on a page. The cool thing about LDS is that it finds requests for same record data and only sends a single shared data request that updates all relevant components..
- The client payload data limit Increased to 4 MB from 1MB.
- To style your Visualforce page to match the Lightning Experience UI when viewed in Lightning Experience or the Salesforce1 app, set lightningStylesheets=”true” in the <apex:page> tag. When the page is viewed in Salesforce Classic, it doesn’t get Lightning Experience styling.
- To run test classes in parallel and remove the default limit for concurrent tests, use the @isTest(isParallel=true) annotation.
17. Field Service enhancements:
- Check out general release notes.
- Field Service Managed Package enhancements
2 thoughts on “Winter ’18 Salesforce Classic & Lightning Experience Highlights”
This is a great summary Jen. Thanks for all your efforts in putting it together.
Thank you. I’m happy that I’m able to give this information to those in the ecosystem.