Quick actions allow you to initiate expense reports from Salesforce to an external HR system. Approval processes allow you to review the expense reports by managers and directors.
References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.quick_actions_overview.htm&type=5

Campaign hierarchy is a feature that allows administrators to organize campaigns into a parent-child relationship, where the parent campaign represents a larger initiative and the child campaigns represent smaller or more specific activities within that initiative. Using campaign hierarchy can help Ursa Major Solar report on campaign ROI by month and series by creating a parent campaign for the series of networking events and creating individual child campaigns for each monthly event. The parent campaign can show the aggregated metrics and ROI for the entire series, while the child campaigns can show the metrics and ROI for each month. Adding different record types for the monthly event types, creating individual campaigns that all have the same name, or configuring campaign member statuses to record which event members attended are not solutions for reporting on campaign ROI by month and series; they either do not group campaigns into a hierarchy or do not track campaign metrics or ROI. References: https://help.salesforce.com/s/articleView?
id=sf.campaigns_hierarchy.htm&type=5

To show different picklist values for sales and marketing users, you can either use record types or profiles.
Record types allow you to have different picklist values for different page layouts assigned to different profiles. Profiles allow you to restrict picklist values based on user permissions.
References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5 https://help.
salesforce.com/s/articleView?id=sf.admin_profile_picklists.htm&type=5

Flow Builder supports creating a scheduled flow that can run at specified intervals and perform actions on a set of records that meet certain criteria.
References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm&type=5 https://help.
salesforce.com/s/articleView?id=sf.flow_concepts_scheduled_start.htm&type=5

Two considerations when installing a managed package in a sandbox are:
* The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
* The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References: https://help.salesforce.com/s
/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s
/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5