A joined report is a type of report that allows you to create multiple report blocks that provide

different views of your data. Each report block can have its own fields, columns, sorting, and filtering.

A joined report can only be created from summary or matrix reports. You can use a joined report to

show data from different report types or data sources on a single report. In this case, you can use a

joined report to show Accounts with Open Cases by creating two report blocks: one for accounts and

one for cases with a filter for open status. You can then join the two blocks by a common field such as

Account

ID

or

Account

Name.

Reference:

https://help.salesforce.com/s/articleView?id=sf.reports_joined_format.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.reports_examples_joined.htm&type=5

Permission sets are collections of settings and permissions that give users access to various tools and

functions without changing their profile or requiring multiple profiles for users who perform different

tasks across apps in your org. By assigning a permission set that has View All on Leads to the

contractor, Cloud Kicks can grant them view access to all lead records without modifying their profile

or

creating

a

new

one.

Reference:

https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5

Process Builder and Flow Builder are tools that allow administrators to automate business processes

in Salesforce without writing code. Process Builder and Flow Builder can perform actions such as

creating records, updating fields, sending emails, posting to Chatter, invoking Apex classes, calling

flows, etc.

To automate several updates to lead records and update unrelated records at Cloud Kicks, an

administrator can use two options:

B) Create a Process Builder that runs when a record is changed

Process Builder is a tool that allows administrators to create processes that consist of criteria nodes

and action groups. Criteria nodes define the conditions that trigger the process and action groups

define the actions that the process performs. Processes can run when a record is created or when a

record is created or edited.

By creating a Process Builder that runs when a record is changed, an administrator can automate

updates to lead records based on certain criteria and perform actions such as updating fields,

sending emails, posting to Chatter, invoking Apex classes, calling flows, etc. Reference:

https://help.salesforce.com/s/articleView?id=sf.process_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.process_considerations.htm&type=5

C) Create a flow that runs when a record is created or updated

Flow Builder is a tool that allows administrators to create flows that consist of elements such as

screens, assignments, decisions, loops, etc. Elements define the logic and user interface of the flow.

Flows can run in different ways such as when a user clicks a button, when a record is updated by

Process Builder, when an event occurs in the system (such as record creation), etc.

Debugging a flow allows administrators to test how a flow behaves before activating it or making

changes to it. Debugging a flow runs it in real time using test data provided by the administrator or

default values from the flow. However, debugging a flow also performs any actions defined in the

flow, such as creating, updating, or deleting records. Therefore, if a flow has a delete element that

deletes a record based on certain criteria, debugging the flow will delete the test record even if the

flow is inactive. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm&type=5

change sets are tools that allow administrators to move customizations from one Salesforce org to

another. However, change sets do not track dependencies or conflicts between components in

different orgs, so administrators need to manually verify that all required components are included

in the change set and that they do not overwrite existing customizations in the target org. To avoid

losing changes in production due to deploying an incomplete or incorrect change set, administrators

should push the change set to another sandbox first and test it there before deploying it to

production.

Reference:

https://help.salesforce.com/s/articleView?id=sf.changesets_considerations.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.changesets_best_practices.htm&type=5

Planning deployments around maintenance schedules ensures that there are no interruptions or

delays in the deployment process. Deploying all dependent components ensures that there are no

missing metadata or

that could cause errors or failures in the deployment. Limiting

change sets to 10,000 files ensures that the deployment does not exceed the maximum size limit for

change sets

Product schedules allow users to track revenue or quantity over time for products in opportunities or

orders by creating schedules manually or automatically based on predefined criteria such as start

date, end date, frequency etc. However, product schedules have some limitations that administrators

should consider before enabling this feature. One of these limitations is that line item schedules are

unavailable in Process Builder and Workflow rules; only revenue schedules are available. Reference:

https://help.salesforce.com/s/articleView?id=sf.products_schedules_def.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.products_schedules_considerations.htm&type=5

Sharing rules are automatic exceptions to organization-wide sharing settings that grant additional

access to records based on record ownership or criteria. By creating a sharing rule on the Account

object for all members of the account services role to have Read/Write access, the administrator can

allow users in that role to edit and change ownership of Accounts owned by any of their team

members,

regardless

of

the

organization-wide

sharing

setting

for

Account.

Reference:

https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.htm&type=5

Password Policies on the System Administrator profile is a feature that allows administrators to set

different password requirements for users with different profiles. Password Policies can specify the

minimum length, complexity, expiration period, history enforcement, lockout interval, and warning

message for passwords. Password Policies can be used to enforce stricter password requirements for

system administrators than for other users

Flows deployed with change sets are inactive by default and need to be manually activated in the

destination org before they can run. Deploying or redeploying a flow with change sets creates a new

version of the flow in the destination org, which preserves the previous versions and allows for

rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are

automatically added to the change set when a flow is added