The list of Spring ’18 features below only apply to both Salesforce Classic and Lightning Experience.

There are additional Spring ’18 features available to Lightning Experience only and others in the Spring ’18 Release Highlights post.

Note: These features are not listed in any specific order.

1. Flow Enhancements:
   • Build slicker flow screens with help from Lightning Components. The component needs to reference the new lightning:availableForFlowScreens interface and has a corresponding design resource will be available as a Lightning component screen field. Note: Lightning flow runtime must be used.
   • Override the flow header and footer by deselecting “Show Header and Show Footer” when you configure a flow screen. Note: If you remove the footer, the screen’s navigation buttons don’t appear. Add a custom Lightning component to allow users to navigate screens. Note: Lightning flow runtime must be used.
   • (Beta) Indicate a user’s point in the flow using the new stage resource and two new system variables: {!$Flow.ActiveStages} and {!$Flow.CurrentStage}. For example, indicate where in a purchasing flow the user is with breadcrumbs or a progress indicator. Salesforce recommends creating a custom lightning component using the lightning:progressindicator component in your flow screen.
   • (Pilot) Call a JavaScript controller of an associated Lightning component directly from your flow with local actions. Note: Lightning flow runtime must be used.
   • Start flow dynamically from apex, no hardcoding the flow name. With createInterview(), you can write one method to start an interview for any flow.
   • (Critical Update) When flow interviews are invoked in bulk, they are now all executed, not just start and execute the first interview.
   • Get more information about paused interviews, using the new $Flow.InterviewGuid system variable. Then build a custom object that references the interview’s GUID, a unique identifier.
   • Associate paused flow interviews with a Record. A paused interview is associated with the record via the FlowRecordRelation object.
     To associate your flow with a record, set the {!$Flow.CurrentRecord} system variable to a valid record ID in an Assignment element. Then use a custom lightning component to display all interviews associated with a given record.
   • Other users can pick up someone else’s paused interview
2. (Beta) Track Time with the Time Field Type. You can use the TIMEVALUE and TIMENOW functions, as well as new HOUR, MINUTE, SECOND, and MILLISECOND functions. There are limitations you should be aware of.
3. When you convert a custom picklist to a multi-select picklist field, Salesforce will preserve the associated record type’s value settings for the field.
4. Generate leads from LinkedIn. Create up to 500 new leads daily in Salesforce via your LinkedIn Lead Gen advertisement. Leads exceeding the 500 daily limit will be emailed to the default lead creator.
5. Report on campaigns with influenced opportunities via a new standard report.
6. Sync person accounts with Microsoft contacts and Google contacts.
   • Google integration
   • Microsoft integration
7. Field Service enhancements
   • The customer or technician can initiate return orders
   • (Beta) Filter related lists on service reports
   • Add page numbers to service reports
   • (Beta) Route service cases to agents using Omni-Channel
   • Schedule service crews in the Field Service Lightning managed package.
   • Use the Field Service Admin Accelerator to create service territories, operating hours, define work types and skill sets, assigning agents, dispatchers, and service resources, and configure scheduling policies.
   • Delete chat transcripts that are over 24 hours old with a Waiting status.
   • (Beta) Use skills-based routing instead of queues in Omni-Channel. Contact Salesforce to enable.
   • Limits have been increased to 30,000 work items/hour and 100,000 total queued work items, from the previous limits of 15,000 work items/hour and 30,000 total queued items.
8. If Visualforce is embedded in your app with legacy click-to-dial, you can add clickable phone numbers.
9. Security & Identity Enhancements:
   • With dynamic branding, you can deliver a different login page based on certain user criteria.
   • Deliver a different registration process based on runtime circumstances to your community user and authentication provider for social sign-on.
   • Dynamically require users to reauthenticate or reapprove during a flow by adding the prompt parameter to your Auth. Provider URL. For example, after signing up for an account, require the user to log in with the newly established credentials.
   • Create login flows programmatically using Visualforce and Apex controllers.
   • Use an Apex trigger to require user identity verification for access to sensitive information.
   • Salesforce has optimized and improved performance with fewer HTTP redirects and by using subdomain and community-specific URLs when implementing social sign-on. Newly created auth. provider URLs will automatically take advantage of this. For already configured URLs, optimize the callback URL by selecting Use subdomain in callback URLs in the Auth. Provider configuration page.
   • (Beta) Extend the logins of external identity community sessions, beyond the 24hrs and logout when they close their browser. You can now allow users to stay logged in after they close their browser. They can also stay logged in for up to seven days of inactivity as well.
   • (Pilot) Create external identity users without contacts – gives you more flexibility and less maintenance. To use this feature, ask Salesforce to enable the org permission, Enable external identity user creation without contacts.
   • (Beta) BYOK for the Shield Key Management Service to use to encrypt and decrypt your data.
   • (GA) Encrypt more PII fields on Opportunities and Contracts. On opportunities, you can encrypt the Name, Description, and Next Step fields; on contracts, the Billing Address (Billing City and Billing Street).
   • With the various regulations around customer privacy, you can now store data privacy and protection preferences in a new Individual object. First, set up the data privacy records, then encrypt the Individual Name field with the type of tenant secret and encryption scheme of your choice.
   • (Pilot) Encrypt activities, email messages, email-to-case messages, and custom object name
   • (Beta) Filter encrypted data with deterministic encryption using exact, case-sensitive matching. To access this feature, contact Salesforce support.
   • (Pilot) Deterministic encryption using exact, case-insensitive matching
   • (GA) Include encrypted fields in skinny tables
   • (Beta) Include encrypted fields in duplicate management custom matching rules. Note: This will not return fuzzy matches. Contact Salesforce support to enable.
   • Mass decrypt a field data. Contact Salesforce support for help in decrypting custom and standard Long Text Area fields, files and attachments.
   • Event Monitoring enhancements:
     • To adhere with data protection regulations (Right to Erasure), you can delete event log files.
     • (Beta) Receive event log files hourly so you can be alerted to suspicious activity within hours of the event, along with event log files after 24 hours of activity. Note: Hourly files are available in the API but not in the Event Monitoring Analytics app, unless you contact Salesforce support.
   • Track insecure external assets with event log files
   • Get more visibility into what happened during a particular user session with LOGIN_KEY and SESSION_KEY fields in the Time-Based Workflow event type.
   • Health Check has new security settings
   • Alert user when they are about to be taken out of Salesforce with a warning message.
10. Development Enhancements:
    • Einstein Platform Services enhancements to image recognition and natural language processing
    • Action overrides using Lightning components for View, New, Edit, and Tab are now supported in Lightning console apps.
    • New and changed lightning components
    • The Lightning Experience Visualforce Report now gives more information and recommendations and estimates to help you migrate your pages ready for Lightning Experience. The report evaluates only the pages accessed in the past 90 days.
    • (Pilot) Custom Metadata: Easy-to-Use Referencing of Custom Metadata Type Records in Validation Rules (VRs)
    • Access more metadata types and data objects in API version 42.0.
    • Use Developer Hub (Dev Hub) to create, delete and manage scratch orgs.
    • Salesforce Connect: Debug logs now include details about requests and responses that occur when the platform or a user accesses external objects via the cross-org or OData adapters for Salesforce Connect.
    • For Web-to-Case or Web-to-Lead failures, emails no longer include personal identifying information (PII) that was inserted by third-party packages.
11. Snap-in for Web enhancements:
    • Use different chat buttons to route chats based on the customer’s pre-chat responses to the right agent skill or Omni-Channel queue.
    • Send an automated chat invitation to proactively invite customers to initiate chat with an agent.
    • Automatically populate pre-chat fields when customers request a chat.
    • Establish sensitive data rules to block specific pattern from displaying in the chat transcript
    • The post-chat URL now opens inside the snap-in, rather than in a new window as it did previously.
12. Delete stored credentials or Oauth tokens to remove access to external systems from your Personal Settings.
13. Use groups, group memberships, topics, and topic assignments with workflow rules and Process Builder.
14. Quickly access all your asset files from the view list of asset files.
15. Social Customer Service Enhancements:
    • Apex’s default behavior will now find existing cases based on Persona, rather than previously relying on threading replyToId.
    • Use clicks, not code to define how new social media cases are assigned and routed to agents.
16. Integrate Quip with Salesforce
17. The new View Roles and Role Hierarchy permission grants and revokes permissions to view roles and the role hierarchy in your org.
18. Assign different standard action overrides for Salesforce Classic, Lightning Experience, and mobile.
19. Prevent administrators and developers from creating custom settings list types by disabling this option in Setup. Salesforce recommends using custom metadata type instead.