A flow is an automation tool that allows you to create processes that perform actions based on user input or record changes. A flow can be triggered by a user who launches it from a button, link, or Lightning page, or by the system when a record is created or updated. A flow has different versions that can be active or inactive. An active version is the one that runs when the flow is triggered, while an inactive version is the one that is saved but not running. When you deploy a flow to production with a change set, the flow version is deployed as inactive by default. This means that you need to activate the flow manually after deployment if you want it to run in production. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_changesets.htm&type=5

When creating a new custom object, administrators can choose to mark it as deployed or in development. If an object is marked as in development, it is not visible to users or available in tools such as Data Loader, even if they have access to it through their profile or permission set. To make the object available for data import, the administrator needs to mark it as deployed. Reference: https://help.salesforce.com/s/articleView?id=sf.customize_deployment_status.htm&type=5

The resume event is recalculated and the email goes out to the account owner immediately because the flow uses a scheduled path that evaluates the expiration date field every time it changes. When the expiration date is changed to yesterday, the flow resumes immediately and executes the action of sending the email

Omni-Channel is a feature that allows service reps to receive work assignments based on their availability, capacity, and skills. It also allows administrators to define routing rules and priorities for different types of work items, such as cases, chats, or leads. Omni-Channel can help reduce the wait time for customers and improve the efficiency of service reps.

Role hierarchy is a sharing mechanism that should be used to open up opportunity sharing to directors who oversee regional managers so they can access records to assist regional managers. Role hierarchy is a way to grant access to records based on the user's position in an organization's hierarchy of roles. Role hierarchy can grant users access to records owned by or shared with users below them in the hierarchy for objects that have organization-wide defaults set to Private or Public Read Only. By using role hierarchy, the administrator can ensure that directors can access opportunities owned by or shared with regional managers who report to them