Takeaways (Week 3) Flashcards

1
Q

What is a Workflow Rules?

A

A workflow rule performs automated action when certain condition(s) are met.

Can be Immediate or Scheduled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

When can Workflow Rules be invoked?

A

Three ways it can be invoked

  1. when a record is created,
  2. created and every time it’s edited,
  3. when a record is created and subsequently edited to meet criteria.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What actions can the Workflow Rules take?

A

Create a task - unlike Process builder, Workflow can only create objects of the “Task” object

Update Records - limited to updating the record that invoked them OR the parent record, but only if that parent record is the master in a master-detail

Send email

Send Outbound Message

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the definition of approval process?

A

Approval Process is a combination of steps for a record to be approved/rejected. An approval process also specifies the actions to take when a record is approved, rejected, recalled, or first submitted for approval.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What actions can an Approval Process take?

A

Task

Email Alert

Field Update

Outbound Message

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the types of actions in the Approval Process?

A

Initial Submission Action - what happens when a record is submitted for approval?

Step Definition - who should records be routed to?

Final Rejection Actions - what happens when a record is rejected?

Final Approval Actions - what happens when a record is approved?

Final Recall - What happens if a record is recalled from the process?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Who can edit a record that’s locked by an approval process?

A

Asides from the Salesforce admin, depending on your settings, an assigned approver can also edit locked records.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a Process Builder?

A

A Process Builder is a tool provided by Salesforce to help you automate your process by updating or creating a record.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the three actions that can invoke a process?

A

Process can be invoked by:

  1. Record changes,
  2. platform event,
  3. invoked by another process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Examples of actions that a process can take

A
  • Create a Record
  • Update Record
  • Email Alerts
  • Post to Chatter
  • Quick Actions
  • Submit for Approval
  • Flows
  • Processes
  • Quip
  • Apex
  • Send Custom Notification
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are duplicate rules, matching rules, and fuzzy matching?

A

Duplicate Rules: warn or stop creation of duplicates

Matching Rules: determine if a record will be a duplicate. Matches fields through exact or fuzzy matching

Fuzzy Matching - similar, but not exact matches

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a formula field?

A

A formula field is a field that derives its value from other fields, expressions, or values.

NOTE: a formula field is calculated each time a user views a record or report but runs in system context. It is never saved to the database.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is a Cross-Object Formula?

A

Formula that involves at least one field from a parent object.

You can create a cross-object formula on a child object up to 10 relationships away.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is a Roll-Up Summary Field?

A

Roll up summary field is a field on a master record that summarizes date or numerical data from detail records.

It is recalculated whenever any referenced detail record is saved or deleted. (and is saved in the database)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are Validation Rules? And what do we use them for?

A

Validation Rules verifies that the data a user enters in a record meets the standards you specify before the user can save the record.

We use to them to:

  • improve data integrity
  • make a field conditionally required
  • prevent the entry of invalid data values directly by users or by other systems
  • enforce role-specific, profile-specific, or user-specific constraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the different types of flows?

A

Screen Flow,
Autolaunched Flow
Platform Event-Triggered Flow
Scheduled-Triggered Flow
Record-Triggered Flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What is Screen Flow (“Wizard”)?

A

With Screen Flow, we can create a “Wizard” that walks a user through a process by breaking it down into a series of steps, each with their own screen.

It is the only flow that can use the screen element. The screen element is used to receive inputs from the users.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What is Autolaunched Flow (No Trigger)?

A

Autolaunched Flow are flows that can be launched automatically based on certain conditions or situations. (i.e. can be invoked by custom actions, process, another flow).

It’s unique in that it does not require user interaction during execution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is Platform Event-Triggered Flow?

A

Platform Event-Triggered Flow evaluate specific platform event messages.

20
Q

What is Scheduled-Triggered Flow?

A

Scheduled-Trigger Flow allow us to set actions to run at a particular time.

21
Q

What is Record-Triggered Flow?

A

Record-Trigger Flow are used to perform operations on record that are currently undergoing a save operation.

22
Q

What is Field History Tracking?

A
  • Allows us to select certain fields to track and display in the field history of an object.
  • Up to 20 fields per object to track
  • Data retained for up to 18 months.
23
Q

What is the Setup Audit Trail?

A
  • Setup Audit Trail shows changes made to an Org’s configuration.
  • Up to 20 changes are displayed. To see more need to download .csv file.
  • Tracked for 180 days.
24
Q

What is a Debug Log?

A
  • Debug Log records database operations, system processes, and errors for a specified user every time that user executes a transaction.
25
Q

What are the different categories of Debug Log?

A

Log category determines what information is logged

  • Database - relates to operations on our records (creating/updating records)
  • Workflow - relates to all of our declarative process automation tools (process, approval process, flows, workflow rules)
  • Validation - information about validation rules
  • Callouts - external apex code
  • Apex Code - local apex code
  • Apex Profiling - where we are in terms of adhering to our governor limits
  • Visualforce - relates to visualforce pages if they’re involved
  • System - includes info such as our duplicate and matching rules. It is also primary way that we will have output from our code (think console dialog log statement in javascript)
26
Q

What are the different Debug Log Levels?

A

The log level determines the amount of info that is logged for each category.

  • NONE
  • ERROR
  • WARN
  • INFO
  • DEBUG
  • FINE
  • FINER
  • FINEST
27
Q

What are the different places Debug Logs can be viewed?

A
  1. In Setup under Debug Logs
  2. Developer Console
  3. Download log and open with local text editor like Notepad
28
Q

What is a Sandbox?

A

A Sandbox is a replica of your production organization that allows you to develop code, test, and train without risking or compromising data.

29
Q

What are the different types of Sandboxes and what differentiates them?

A
  • *Full Sandbox**
  • *Purpose**: Performance and load testing, staging
  • *Capacity**: based on it’s production organization
  • *Refresh Timeframe**: 29 Days
  • *Partial Copy Sandbox**
  • *Purpose**: testing environment
  • *Capacity**: Limit of 5GB of data and 10,000 records per selected object
  • *Refresh Timeframe**: 5 Days
  • *Developer Pro Sandbox**
  • *Purpose**: dev and testing in isolated environment with more data
  • *Capacity**: does not copy data, but can load up to 1GB of data separately
  • *Refresh Timeframe**: Daily
  • *Developer Sandbox**
  • *Purpose**: dev and testing in isolated environment, and user training
  • *Capacity**: does not copy data, but can load up to 200MB of data separately
  • *Refresh Timeframe**: Daily
30
Q

What are Managed Packages and Unmanaged Packages?

A

Unmanaged - Typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application

Managed - Typically used by Salesforce partners to distribute and sell applications to customers

Managed can be upgraded whereas Unmanaged isn’t.
Unmanaged can be customized (components can be edited).

31
Q

What are Change Sets?

A

Change Sets is a declarative tool that we can use to migrate change between related organizations.

32
Q

What are some things to consider for Change Sets?

A

Apex code must pass unit test (75%)

All or nothing deployment

Some meta data type is not supported so we need to manually make those changes

33
Q

What are the best practices for Change Sets?

A

The best practice is to develop and test changes in a sandbox before moving them into production.

34
Q

What are ANT Migration Tool?

A

Java based command line tool that we can use to pull down source locally from one salesforce org and then deploy it to another. Unlike Change Sets, it’s NOT limited between related Orgs..

35
Q

What are the six factors of quality data? What tools do we use to enforce them?

A
  1. Completeness - have all the information we need
    * *Tools**: required fields, validation rules
  2. Consistency - want all of our info to be filled out in a consistent way
    * *Tools**: validation rules
  3. Currency - want our data to be up to date
    * *Tools**: Workflows, Processes, and Flows
  4. Uniqueness - don’t want duplicate data
    * *Tools**: Duplicate rules
  5. Accuracy - want values in our records are correct
    * *Tools**: Processes, Paths, Flows, DB Optimizer
  6. Validity - want to make sure what we’re tracking makes sense to be tracking
    * *Tools**: no tools, just something we ask ourselves beforehand
36
Q

What is the difference between Data Loader and Data Import Wizard?

A

Import

Data Loader: for complex imports of data

Data Import Wizard: for simple imports of data

Load

Data Loader: up to 5 million records

Data Import Wizard: up to 50,000 records

Object Support

Data Loader: All custom and standard object

Data Import Wizard: All custom, some standard

Scheduled Export

Data Loader: supported

Data Import Wizard: not supported

Delete

Data Loader: supported

Data Import Wizard: not supported

Duplicates

Data Loader: not ignored on import

Data Import Wizard: ignored on import

Installation

Data Loader: requires installation

Data Import Wizard: not required

37
Q

What is the difference between Export and Export All operations?

A

Both export all records present in the system for that object to .csv file. The difference is that

  • Export - excludes records present in Recycle Bin
  • Export All - includes records present in Recycle Bin
38
Q

What is the difference between Delete and Hard Delete Operations?

A
  • Normal Delete stores record in Recycle Bin.
  • Hard Delete do not store records in Recycle Bin.
39
Q

What are the different report types?

A

Standard report types are automatically included with standard objects and cannot be customized.

Custom report types are added by an administrator. Within a custom report type, you can specify which objects and fields are included in the report.

They allow you to modify how fields will appear in the Fields pane of the report builder.

You can:

  • Create, remove, rename, and reorder sections
  • Remove, reorder, and rename fields
  • Add fields related via lookup
  • Select which fields appear as columns by default
40
Q

What are the different Report Formats?

A
  • Tabular - simplest way to look at data, tabular reports are an ordered set of fields in columns, which each row representing a record
  • Summary - allow you to group rows of data, view subtotals, and create charts
  • Matrix - allow you to group data by both rows and columns. Good for comparing related totals or comparing values in several fields.
  • Joined - allow you to create multiple report blocks, each block acting as its own “sub-report” with its own report type, fields, columns, sorting, and filtering.
41
Q

What are Dashboards?

A

Dashboards allow you to present multiple reports side-by-side using components.

42
Q

What are Dashboard Components?

A

Components are a combination of a source report and a chart type. Each component can only have one source report, but the source report can be used for multiple different components.

43
Q

How many components can be included on a single dashboard?

A

20 different components can be included on a single dashboard.

44
Q

What are the different access levels for report and dashboard folders?

A
  • View - see the report or dashboard within that folder
  • Edit - see and edit the contents of that folder
  • Manage - ability to view and edit the folder contents as well as share the contents of the folder with other users within our Orgs
45
Q

Give me the streamlined version of the order of execution

A
  1. Before-Save Record-Triggered Flows
  2. Before Triggers
  3. Most system validation rules are rerun and custom validation rules are run for the first time. (excludes page layout specific validation)
  4. Save (this is a soft-save, not a commit - if any errors happen before the Commit step in the Order of Execution, our entire operation will fail and be rolled back).
  5. After Triggers
  6. Workflow Rules
    1. If a Workflow Rule changes a field value
      1. Before Update Triggers
      2. Most system validation is rerun (NO validation rules are executed at this time)
      3. Save
      4. After Update Triggers
  7. Processes and the Autolaunched Flows they invoke.
    1. If one of these changes a field value
      1. Before Update Triggers
      2. Most system validation and custom validation rules are rerun
      3. Save
      4. After Update Triggers
  8. After-Save Flows
    1. If an After-Save Flow changes a field value
      1. Before Update Triggers
      2. Most system validation and custom validation rules are rerun
      3. Save
      4. After Update Triggers
  9. Roll-Up Summaries and Cross-Object Workflows (these cause another Order of Execution to run on the parent record, which includes every step except for the Commit and Post-Commit Logic steps).
  10. Commit
  11. Post-Commit Logic