If the Organization-Wide Settings (OWD) in your Salesforce Org is set to anything other than “Public Read/Write” for any of the standard or custom objects then it is more than likely that you will need to setup some sharing rules to share these records with other users. So what are the different ways to share records? Here is a checklist of all the different ways (21 that I could think of) in which you can share records in Salesforce. You can use this as a quick reference guide to help you determine which of these options will be most appropriate to meet your business requirements.
Dynamic Forms was announced in Dreamforce 2019 as one of the features in UI enhancements roadmap in Admin & Lightning Keynotes. It is now available as Non-GA Preview in Salesforce Summer ’20 release
This is going to be a game-changing feature that will give admins and consultants the ability to have granular control on the record pages. You can now declaratively customize sections and fields of the page as per the business requirements. e.g. Show a particular section when a picklist field has a certain value, Opportunity has reached a certain stage, display a section with relevant fields to a particular user profile, etc. So, there are fewer page layouts to maintain.
Give a Boost to Your Users’ Productivity
A Mass Quick Action is a type of Quick Action. Once the action is created you add that action to an object’s search layout i.e. List View. Once it is set up, you can select a maximum of 100 records in a list view and perform create or update functions. It was introduced in Summer ’18 release. Mass Quick Action is available to use with the following objects:
Use a diagramming tool to draw architecture diagram, system landscape, process flows, flowchart, entity-relationship diagram (ERD), sequence diagram, data flow diagram, etc. These tools are indispensable at every stage of your Salesforce implementation.
How to deploy metadata components between unrelated Salesforce Orgs
If you are familiar with change sets in Salesforce, you know that it can be used to transfer metadata between related orgs. For example, transfer the objects, fields, apex classes, etc. from sandbox to production, production to sandbox, and sandbox to sandbox.
But what if you need to transfer metadata between unrelated orgs or completely different orgs? There are a couple of options, one of which is the ANT Migration Tool provided by Salesforce. (If you are not yet familiar with ANT Migration Tool, you may want to make a note to refer to my another blog post
Step-by-Step Guide on Getting Started with Salesforce ANT Migration Tool)
The other option for moving metadata from one org to another org is using Packages.