The Opportunity Stage Duration report is a standard report that shows how long opportunities spend in each stage before they are closed. It can be used to measure the average stage duration for all closed opportunities by grouping and summarizing the data by stage name and duration fields. Using process builder to capture the daily average on each opportunity is not feasible because it would require creating multiple fields and formulas on the opportunity object and updating them every day. Adding formula fields to track stages on each opportunity is also not practical because it would require creating multiple fields and formulas on the opportunity object and maintaining them every time a stage changes. Refreshing weekly reporting snapshots for closed opportunities is not necessary because the report can run on real-time data without snapshots. Reference: https://help.salesforce.com/s/articleView?id=sf.reports_opportunity_stage_duration_report.htm&type=5

To automate applying discounts on opportunity products when an opportunity is won, the administrator should use Flow Builder, which is a tool that allows creating complex business processes with clicks. The administrator can create an autolaunched flow that runs when an opportunity is updated, checks if its stage is "Closed Won", and updates its related opportunity products with discounts from a formula or variable. Approval Process, Prebuilt Macro, and Formula Field are not able to update related records based on criteria. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_build_overview.htm&type=5

To re-assign cases that meet the 24 hour SLA to the next tier queue, the administrator should use a case escalation rule that defines the criteria for escalating cases, such as age or priority, and the actions to perform when those criteria are met, such as changing owner or sending email alerts. Case escalation rules can help ensure that cases are handled in a timely manner and escalated to appropriate users or queues. Einstein Case Routing, Auto-response rule, and Case assignment rule are not able to re-assign cases based on SLA or age. Reference: https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm&type=5

To debug a screen flow that creates contacts, one of the possible causes for a variable missing on the debug screen is that the available for input checkbox was unchecked for that variable. This means that variable cannot be set by external sources such as debug inputs or URL parameters. To fix this issue, check this checkbox for any variable that needs to be set externally. The flow version or field type does not affect variable availability for input. The available for output checkbox only affects whether variables can be passed out of flows or subflows. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_ref_variables.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.flow_debugging.htm&type=5

A permission set group is a collection of permission sets that can be assigned to users as one unit; it simplifies permission management by reducing the number of permission assignments needed for users who require multiple permission sets. A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce; it can be used to extend users' access beyond their profile without changing their profile. Creating permission sets and assigning permission set groups can help Cloud Kicks give access to new custom object with custom fields to more than one user by creating permission sets that include access to new custom object with custom fields and assigning permission set groups that contain those permission sets to users who need them. Adding users to manual sharing list or editing organization-wide defaults are not options for giving access to new custom object with custom fields to more than one user; they either do not apply to custom objects or do not grant object-level access. Reference: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.perm_set_groups_overview.htm&type=5