SalesforceBusiness Rules Engine - Intro & Demo.pdf

Salesforce BRE description

1. Business Rules
Engine
Enable agile & automated decisions in digital
processes for every industry
Introduction, Demo

2. Forward-Looking Statement
Statement under the Private Securities Litigation Reform Act of 1995:
This presentation contains forward-looking statements about the company’s financial and operating results, which may include expected GAAP and non-GAAP financial and other operating
and non-operating results, including revenue, net income, diluted earnings per share, operating cash flow growth, operating margin improvement, expected revenue growth, expected
current remaining performance obligation growth, expected tax rates, the one-time accounting non-cash charge that was incurred in connection with the Salesforce.org combination;
stock-based compensation expenses, amortization of purchased intangibles, shares outstanding, market growth and sustainability goals. The achievement or success of the matters covered
by such forward-looking statements involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, the company’s
results could differ materially from the results expressed or implied by the forward-looking statements we make.
The risks and uncertainties referred to above include -- but are not limited to -- risks associated with the effect of general economic and market conditions; the impact of geopolitical events;
the impact of foreign currency exchange rate and interest rate fluctuations on our results; our business strategy and our plan to build our business, including our strategy to be the leading
provider of enterprise cloud computing applications and platforms; the pace of change and innovation in enterprise cloud computing services; the seasonal nature of our sales cycles; the
competitive nature of the market in which we participate; our international expansion strategy; the demands on our personnel and infrastructure resulting from significant growth in our
customer base and operations, including as a result of acquisitions; our service performance and security, including the resources and costs required to avoid unanticipated downtime and
prevent, detect and remediate potential security breaches; the expenses associated with new data centers and third-party infrastructure providers; additional data center capacity; real
estate and office facilities space; our operating results and cash flows; new services and product features, including any efforts to expand our services beyond the CRM market; our strategy
of acquiring or making investments in complementary businesses, joint ventures, services, technologies and intellectual property rights; the performance and fair value of our investments in
complementary businesses through our strategic investment portfolio; our ability to realize the benefits from strategic partnerships, joint ventures and investments; the impact of future gains
or losses from our strategic investment portfolio, including gains or losses from overall market conditions that may affect the publicly traded companies within the company's strategic
investment portfolio; our ability to execute our business plans; our ability to successfully integrate acquired businesses and technologies, including delays related to the integration of
Tableau due to regulatory review by the United Kingdom Competition and Markets Authority; our ability to continue to grow unearned revenue and remaining performance obligation; our
ability to protect our intellectual property rights; our ability to develop our brands; our reliance on third-party hardware, software and platform providers; our dependency on the
development and maintenance of the infrastructure of the Internet; the
effect of evolving domestic and foreign government regulations, including those related to the provision of services on the Internet, those related to accessing the Internet, and those
addressing data privacy, cross-border data transfers and import and export controls; the valuation of our deferred tax assets and the release of related valuation allowances; the potential
availability of additional tax assets in the future; the impact of new accounting pronouncements and tax laws; uncertainties affecting our ability to estimate our tax
rate; the impact of expensing stock options and other equity awards; the sufficiency of our capital resources; factors related to our outstanding debt, revolving credit facility, term loan and
loan associated with 50 Fremont; compliance with our debt covenants and lease obligations; current and potential litigation involving us; and the impact of climate change.
Further information on these and other factors that could affect the company’s financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings it makes with the
Securities and Exchange Commission from time to time. These documents are available on the SEC Filings section of the Investor Information section of the company’s website at
www.salesforce.com/investor.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements, except as required by law.

3. Introducing
Business Rules Engine
Enable agile, automated decisions for every industry
Build rules using a visual designer
Enable business users to design automated
decisions
Embed rules in any workflow process
Use Rules in guided interactions (Omniscript),
workflows (Flow), and via API
Operate at B2C scale
Maintain thousands of rules, automate millions
of decisions

4. Business Rules Engine Benefits
Intuitive
Business users design via no-code builder
Easy to Integrate
Embed in any digital interaction or process
Transparent
Use Decision Explainer to audit & describe rules
Agile
Business Users maintain & extend decisions
Rich Functionality
Conditions, Calculations, Lookup Tables, Sub Rules
Highly Performant
Scalable to meet B2C needs

5. Using Business Rules Engine
1.Compose “Rules” in Rules Builder tool
2.Embed “Rules” in any Omniscript, Flow, or any custom workflow
3.Serve transparent decisions in digital processes
1 2 3

6. A short primer, before
the demo
Key Features

7. Business Rules Engine - The Key Modules
Expression Sets contain sequences of
calculations, rules, lookup tables and
more types of steps.
Expression Sets
Decision Matrices, Decision Tables
These are lookup tables, with specified
input & output columns. These can be
used inside Expression Sets as well as
standalone.
BRE includes visual designers for both Expression Sets and Lookup Tables.
History & Continuity

●Business Rules Engine (BRE) replaces the Calculation Procedures and Calculation Matrices modules that
were previously available in Vlocity OmniStudio Package.
●BRE modules carry over all the features of Calculation Procedures & Calculation Matrices. **
●BRE is in Core and offers same integrations with Omniscript & Integration Procedures as before.
●BRE went GA in Spring ‘22 (236 release).
** With some exceptions

8. Expression Sets
Overview
An Expression Set is an
orchestration of calculations,
evaluations, lookups and more.
Expression Sets are created
using the Expression Set
Builder, sometimes also called
as the Rules Builder

9. Expression Sets
Key features
Numerical formula
based expressions
Boolean evaluations
Lookup tables
Reuse one expression
set in another
Condition triggered
calculation units
Branching logic
Aggregate results from
batch runs

10. Expression Sets
More features
Access Control
Versioning, with
active date range
Live Simulation Copy and reuse

11. Decision Matrices
Overview
Input
columns
Output
columns
Versioning
support
CSV export &
import
Inline editing in
table interface
Pre-wired for usage inside
Expression Sets

12. Decision Matrices
Pre-integrated with Expression Sets
Add Lookup Table element Select a Decision Matrix
Use Decision Matrix output as a variable in the
Expression Set

13. Decision Tables
Lookup Tables With Complex Logic and Connection to sObjects
Connect to sObjects
Rich Operators
Custom Matching Logic

14. Simulation
To test rules
Visual Simulator to help test
rules during design time.

15. Decision Explanation
For Transparency and audits
Rule runs can be logged, and
presented to end users for
transparency, or used for audits.

16. SObject access inside Expression Sets
Designers get pre-created variables that are mapped to SObject fields
Pre-created variables that are mapped to
SObject fields, available to Rule Designers
Object Aliases
created by Admins
NEW in Winter ‘23

17. Architecture
Automated Decisions in Digital Processes
Omniscript Flow
Any workflow, via
Connect API
End Users
(Consumers, Partners, Internal)
Rules Runtime
Business Rules
Rules Designtime
Business Users
Visual Rules
Builder
Design, Simulate, Create new version,
Activate/Deactivate, Set effective date
range & Deploy Business Rules
Expression Sets are like RuleSets and
contain a sequence of condition based
actions, branches, calculations and
lookups.
Decision Matrix / Decision Tables#
are Rules in more compact lookup
table form, with specified input &
output columns.
2 constructs available to
design Business Rules
Make decisions on Eligibility,
Qualification; Calculate
Offers, Price; Implement best
practice etc.
Invoke Rules with inputs
Take actions like approve
application, qualify user,
update cart, notify user,
show offer, etc.
Consume Rule output
Decision Explanation Service
Run logs
(Hbase)
Each rule run is logged. Logs
are used to explain
decisions to end users, or for
historial audits.

18. Product Architecture
All of this is in Core
BRE BPOs
BRE Design Time
BRE Designers
Business Users
OmniStudio
Integration
BRE Runtime
Flow
Integration
Connect API
Workflows consuming BRE
End Users
APIs to design
simulate &
maintain Rules
Expression Set
Builder, Decision
Matrix Designer

19. Demo
Industry process example, from Public Sector

20. Business License Application Fee
Public Sector
As part of their “ease of
doing business” initiative,
Govt. of Genovia has
simplified the Business
License Application
process.
The process contains a
guided interaction for the
applicant to determine
the applicable License
Application Fee.
Business Rules Engine
enables automated
determination of License
Application Fee in this
interaction.

21. People Involved
ALEX PARK
Technical Staff

JESSICA
Program Manager

DONISHA SMITH
Business Owner

Alex has built the License
Fee interaction using
Omniscript. His Omniscript
uses a Rule to determine
the application fee.
Jessica has composed the
Rule that determines the
License Application fee.

Donisha wants to know the
License Application Fee
amount for her business.


Government of Genovia employees A citizen of Genovia

22. Donisha finds the apply
button on government’s
business portal.

23. Donisha fills in the
required information.

24. No more waiting to hear
back! She is instantly
shown the applicable
Total Application Fee,
calculated by Business
Rules Engine!

25. Creating the Rule that determined
Donisha’s Application Fee

26. Right inside OmniStudio,
Jessica creates a new
“Rule” aka Expression Set.





Alex has created rest of
the digital interaction. He
will integrate the Rule
from here once it is ready.

27. Jessica fills in the basic
information to create the
Rule.

28. The first version of
Application Fee Rule is
ready to be composed.
The Rule is composed in
“Expression Set Builder”.

29. The “Expression Set
Builder” aka Rules Builder
tool.
Jessica would first create
the variables and
constants that would be
used in the calculations.

Click on “Add Resource”
button brings up the
dialog to define a variable
or constant.

30. The variable that will hold
the Base Fee

31. Jessica adds all other
variables and constants as
required.
Ex: “Additional_Fee”
variable holds a part of the
Total Fee.
Ex: “Inspection_Fee”
variable holds another
part of the Total Fee.

32. Time to to compose the
Rule using available
elements!
Jessica starts with a
Decision Matrix to
determine the Base Fee.

33. Jessica had used an excel
sheet to create a lookup
table aka Decision Matrix.
She searches for it.
“Base Application Fee” is
the lookup table she had
created to determine the
base fee amount.

34. Quick summary of input
and output column(s) of
the lookup table help
Jessica feel assured that
she is using the right
lookup table

35. Next, Jessica adds a
calculation to compute an
additional fee that is based
on seating capacity

36. Typeahead support for
variable names and
pre-built functions help
Jessica enter the formula.
“Seating capacity base
fee” is a constant that
Jessica has defined earlier,
and is using here.

37. Next, Jessica adds a
conditional group to
calculate an inspection fee
for large establishments. In
this group, she will add a
condition to check if an
inspection fee would
apply.

38. This condition checks if the
establishment area is large
enough to require an
inspection fee.
Jessica is using a constant
to hold the minimum area
value that needs to be
checked.

39. Prior steps of the Rule can
be collapsed for better
readability.

40. Jessica remembers that
recently, she composed a
rule to determine
additional inspection based
on the area of
establishment.
She wants to re-use that
same rule. She can do that
via the “Sub Expression”
element.

41. Existing Rule called
“Inspection Fee” is being
reused to determine
inspection fee based on
establishment area.

42. Now, Jessica needs to add
up all the fees to arrive at
the total application fee.
She adds a “Calculation”
element to do this.

43. The calculation to arrive at
the total Application Fee,
stored in “Total_Fee”
variable.

44. Jessica saves the Rule, and
clicks on “Simulate” button
to test it.

45. Jessica needs to fill in the
input values. Once done,
she clicks on “Simulate”
button.
During the actual
interaction, Omniscript will
pass these values to the
Rule.

46. Yay, Jessica sees that her
Rule works exactly as
designed!
She can see the output of
each step.
She can see the final
output value.

47. Jessica can expand each
step to view more details.
This helps to test & fix the
Rule while it is being
composed.
“View JSON Results” can
also be expanded to see
more technical details.

48. THANK YOU