1. @archladies archladies.com
PLATFORM DEVELOPER I Certification Study Group Week 3 Led by: Blanca V. Leon-Carter
#LBAjourneytoPD1

2. Study Group Member & Kelle Costa @clickclackcode
Guest Presenter
Business Analyst
6x Certified Salesforce Consultant
Vetforce Member
RAD Women Code Alumni
Study Group Member & Kelle

3. Week 2 Objectives Logic & Process Automation {part 1}
Describe how to programmatically access and utilize the object schema.
Describe the capabilities and use cases for formula fields.
Describe the capabilities and use cases for roll-up summary fields.
Describe the capabilities of the declarative process automation features.
Describe when to use declarative automation features vs. Apex classes and triggers.
Describe how to declare variables and constants in Apex and how to assign values using expressions.
Describe the primitive and complex Apex data types and when to use them.

4. Formula Fields
Formula field = field type that does calculation during page read view
Formula fields are read only
Formula fields are very similar to the formulas on a spreadsheet
Create Simple or Advance Formula
Simple
Advanced
Allows merge fields (reference fields in related object)
simple math operations such as Add, Subtract, Divide and others such as concatenate
Allow merge fields
Advance operations and range of functions such as if then conditions, adding image, hyperlinks.
Image Source: Salesforce, Understand Custom & Standard Objects

5. Formula Fields continue
Depending on the use case, formula fields can be use to perform various calculation using various data
Formula field can return various field types including checkbox, currency, date, percent, text, number
Fields are calculated from within the same objects and reference a parent object (not the other way)
Fields are calculated from within the same objects and reference a parent object (aka cross object formula)
Cross object formula = pulling info from the parent field into the child object
Formula field is NOT used to pull information from child into parent.
Parent can not get data from child using formula = roll-up summary field is used and the relationship = Master/Detail
Image Source: Salesforce, Understand Custom & Standard Objects

6. Validation Rule Use cases - data validation, clean data
Validation rules is not used to replace required field
Formulas are used in

7. Validation Rule
Validation rules are use to verify and enforce business logic before user SAVES
Can contain formula fields that evaluate the data and returns a T/F
If the validation is true/ invalid, and error message include error message.
Validations rules are case sensitives
Validations impact on API usage will have impact (data loader, web-to-lead)
Examples of Validation Rules
Use cases - data validation, clean data
Validation rules is not used to replace required field
Formulas are used in

8. Rules about Formula rules
Formula reference STANDARD, CUSTOM or other Formula fields
Formula can reference the Objects itself or fields from Parent Object
Formula fields CANNOT reference itself
Fields that are USED in formulas can not be deleted (Admin must remove formula first)
Cross-Object formula can reference field from object that are TEN relationship away
Cannot contain more than 3900 CHARACTERS (including spaces and line breaks)
Formula fields are calculated using SOQL on the backend
The SOQL CANNOT exceed 5000 CHARACTERS (including reference fields)
What it is, use case, what object can it be used

9. Roll-up Summary Fields
Roll up summary is ONLY available on Master/Detail relationship
Summarized selected field on a CHILD object
Information that it can gather are Min, Max, Count, Sum
The roll-up field on the Parent calculates when the reference on the child record is SAVED.
Example Opportunities amounts roll-up to Account the relationship is a look-up but salesforce treats this as a M/D

10. Roll-up Summary Fields
Create roll-ups on
Standard
Custom
Opportunities/Opportunity Products
Account with related Oppty
Campaign/ campaign members
Opportunities amounts roll-up to Account

11. Using look-up filters
Look-up filters narrow search and provide better return data values.
Administrators specify the restrictions by configuring filter criteria that compare fields and values on:
The current record (source)
The lookup object (target)
The user's record, permissions, and role
Records directly related to the target object
What it is, use case, what object can it be used

12. Look-Up Filters
Example Opportunities amounts roll-up to Account the relationship is a look-up but salesforce treats this as a M/D

13. Declarative Automation Tools
Workflow - if then, Process Builder - multiple workflows, Approval Process - , Visual Flow
Tools to automate your process and procedures and increase productivity

14. Workflow Rules
Workflow is the main container for a set of workflow instructions.
Set on ONE object at a time
Triggered when an event occurs (record change)
Actions can be immediate or TIME dependant
Automatically performs action

15. Workflow Rules Step in creating a workflow ID object
Specify rule when workflow is created
on creation
on creation & EVERY time it’s edit
on creation & ANY time edit to meet criteria
3. Specify rule criteria
4. Define Action
ACTIONS
Create Task
Send Alert
Update field on Record itself or Parent’s record
Send Outbound Message

16. Process Builder Another tool to help automate business process
Process builder is a user friendly graphical representation of your process as you build it.
Design an entire process in one place vs creating multiple workflows
Define more than one criteria
Actions can be immediate or TIME dependant
Triggered when an event occurs (record change) or Trigger by another process

17. Process Builder Criteria that determine when to execute action groups
Actions can be immediate or scheduled (not supported for invocable processes)

18. Process Builder Actions
Update any related record—not just the record or its parent
Send an
Create a record
Send outbound message using APEX
Use a quick action to create a record, update a record, or log a call
Invoke a process from another process
Launch a flow
Post to Chatter
Submit for approval

19. Approval Process
An approval process automates how records are approved in Salesforce.
Allows user to specify a sequence of steps that are required to approve a record.
An approval process specifies each step of approval, including who to request approval from and what to do at each point of the process.
Approval Examples:
Approve Status change in opportunities or cases
Approve a Leave Request Record
Approve Expense Request

20. Approval Process Actions
Create Task
Send Alert
Field Update on the Record itself, or Parent Record in a Master Detail relationship only
Send outbound Message for external systems
Lock / Unlock action

21. Lightning Flows
Flows can execute logic, interact with the Salesforce database, call Apex classes, and guide users through screens for collecting and updating data. Most often, flows are built by using the
Visual Workflow is the product that encompasses the process of designing, managing, and running flows.
Cloud Flow Designer is the point-and-click tool that you can use to design flows.
Flow is the application that automates a process by collecting, updating, editing, and creating Salesforce data.
Intro to Flow - Salesforce Ben
The best way to figure out whether you can start with the Process Builder is to ask yourself, “Do I need to get information from a user?”

22. Cloud Flow Designer
The Palette houses all the elements that you can add to your flow.
Resources tab houses all the resources that you can add to your flow.
Explorer shows all of the elements and resources that you’ve already added to this flow
The flow you create appears on the canvas
1. Elements represent actions that are executed in the flow; 2. Connectors define which path the flow takes; 3. Resources are the values that can be referenced anywhere in the flow.

23. Visual Flow Actions Update fields in any record Quick Action
Query Records
Loop Records
Multiple Decisions
Accept user input
Delete Records
Call Apex (can be used to send outbound message also)
Create Records
Post to Chatter
Send
Submit for Approval

24. Review of the Automation Tools
PVA

25. Use Apex when... Create Web services. Create email services.
Perform complex validation over multiple objects.
Create complex business processes that are not supported by workflow.
Create custom transactional logic (logic that occurs over the entire transaction, not just with a single record or object).
Attach custom logic to another operation, such as saving a record, so that it occurs whenever the operation is executed, regardless of whether it originates in the user interface, a Visualforce page, or from SOAP API.

26. Apex Variable
Variable - a place in your computer memory that is a given name and it is used to store data.
integer W %$idth = 6;
integer length;
integer squareFootage = width * length;
Apex variable is case in-sensitive and STRONGLY TYPED
5 steps in declaring a variable
Specify the Data Type
Give it a Name
Add the assignment “=”
Specify the Value
Cap with the “;”
Variable names NO NOs
white space
special characters *%$#
user reserved words

27. Constant Variable Expression
Constant is a variable whose value does NOT change after being initialized once.
Constant are defined using the keyword FINAL.
Example: Final Decimal pi = ;
Expression are the building block
Expressions are made up of
Variable
Operators
Methods invocation that evaluate a value
Expression can be literal, sObject, list, set, SOQL
Literal expression: 1 +1;
New sObject: new Case();
L-values: Integer i, myList();
SOQL or SOSL query surrounded by []

28. Apex Data Types PRIMITIVE COMPLEX Blob(Attachments) Integer(Number)
Boolean Long
Date Object
DateTime String
Decimal Time
Double(same as decimal but larger) ID
COMPLEX
List - (ON) Ordered Non-unique
Set - (UU) Unordered Unique
Map - Made of Keys(Set) and Values(List)
Enum
sObject
Class Object
Collections hold more than one element = List, Set and Map

29. Logic & Process Automation Testing Debug & Deployment Tools
Platform Developer I Certification Study Group
*Schedule: June 28 – September 6, 2018
Week 3 August 2
Week 4 August 16
Week 5 August 23
Week 6 August 30
Week 7 September 6
Logic & Process Automation
User Interface
Testing Debug & Deployment Tools
Review & Take the Exam
*Schedule was updated on 7/18/2018
Upcoming Events WIT Success: July Forcelandia: August 8 - 9*