Skip to main content

Summer'20 release of Field Service Lightning

About Us
Published by admin
20 July 2020
68

We have prepared an overview of the most interesting Field Service Lightning features from the Summer'20 release in our opinion.

1. Optimization Insights feature (Beta)

That new feature allows to see results of global optimization. Optimization insights is a set of components that can be added to Optimization request page in Lightning App Builder.

summer-20-release-1

 

 

There are three components available: metrics (1), key performance indicators (2), and summary (3).

summer-20-release-2

 

Summary

That component shows details about the optimization request, such as status, horizon, and territories.

Metrics

Metrics provide an overview of scheduling information, such as how many appointments were scheduled from the pool of optimizable appointments.

KPI

The KPI component displays key performance indicators by territory before and after the optimization. Insights are available for global optimization requests that complete successfully. They aren’t supported for in-day or resource schedule optimization.

2. Count Work Rule type

With the use of Count work rule type in scheduling policy it is possible to restrict appointment scheduling based on assignments, hours worked, or a custom value. It allows you to prevent the overloading of workers or their vehicles. You can assign light workloads to new-hires, or track item quantities that fit in each worker’s vehicle.

summer-20-release-3


 

3. Enhanced optimization

Enhanced Optimization provides a range of scheduling features that help you address last-minute scheduling challenges, make more informed scheduling decisions, and minimize surprises for your team. Previously, to access in-day optimization, predictive travel, and scheduling recipes, you activated enhanced optimization. That type of optimization is going to become a default method.

4. Opportunity to track Team's Expenses

Expenses let your service resources track costs and associate them to work orders.

summer-20-release-4


 

5. Use Criteria-Based Sharing Rules for Time Sheets

Previously Timesheets could be shared only based on the record owner. Now criteria-based sharing rules are available.

summer-20-release-5


 

Thanks for reading, if you need any help with the new Salesforce Summer’20 release contact us. We’d be happy to discuss how we can help you maximize the value of Salesforce.

Contact JET BI expert


Ekaterina Rusakovich
Business Analyst
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026