To enable users to add repeating tasks in Salesforce, the administrator needs to do two things: first, enable the creation of recurring tasks in activity settings under setup; second, add the create recurring series of tasks field on the page layouts for tasks. This will allow users to create a series of tasks that repeat based on a specified frequency and end date. References: https://help.salesforce.com/s/articleView?id=sf.tasks_repeating.htm &type=5

Email-to-Case allows you to create cases from incoming emails. You need to enable this feature and set up routing addresses and case creation settings.

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

Case escalation rules allow you to escalate cases based on certain criteria, such as time or priority.

References: https://help.salesforce.com/s/articleView?id=sf.customize_escalation.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

To track assigned licenses and permission sets in Salesforce instead of using a spreadsheet, an administrator should use User Report type on Report object. User Report type allows creating reports that show information about users such as their profile, role, license type, active status, login history etc. It also allows adding fields related to permission sets such as Permission Set Assignments or Permission Set License Assignments. For example, an administrator can create a User Report that shows user name, profile name, user license name, permission set assignments count etc. Login History, Lightning Usage App, or Permission Set Groups are not features that can be used to track assigned licenses and permission sets in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.reports_report_types_standard_user.htm &type=5

To surface important values based on stage of opportunity , an administrator should use Path Key fields feature on Opportunity object . This feature allows adding up to five fields that display key information about each stage along path . Users can edit these fields inline without leaving path . For example , an administrator can add Amount , Close Date , Next Step , Probability , and Stage fields as key fields for Opportunity path . Opportunity Processes , Dynamic Forms , and Workflow Rules are not tools for surfacing important values based on stage of opportunity . References : https :// help . salesforce . com / s / articleView ? id = sf . lex_path_setup_key_fields . htm & type = 5

Currency locale and default language are two of the company settings that an administrator can configure in Salesforce. Currency locale determines how currency amounts are formatted and displayed in reports and other places. Default language determines the language used for labels, buttons, tabs, and other elements in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_currencies.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_supported_languages.htm &type=5

Validation rules allow you to prevent users from changing an opportunity close date to a date in the past.

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

An external ID is a custom field that has the external ID attribute enabled, which means it can be used as an identifier when importing and updating records from an external system. It allows administrators to match records based on a unique ID value from another system instead of using Salesforce record IDs, which may not be available or consistent across systems. An auto-number field is a custom field that automatically assigns a unique numeric value to each record, but it cannot be used as an identifier when importing and updating records from an external system because it is generated by Salesforce and may not match with the external system’s IDs. A rich text field is a custom field that allows users to enter formatted text, images, and links, but it cannot be used as an identifier when importing and updating records from an external system because it is not unique or consistent across systems. A record ID is an internal ID assigned by Salesforce to each record, but it cannot be used as an identifier when importing and updating records from an external system because it may not be available or consistent across systems. References: https://help.salesforce.com/s/articleView?id=sf.custom_field_attributes.htm &type=5

Bucket column allows you to categorize report data into groups without creating a formula or custom field. You can create buckets for different ranges of values and assign labels to them.

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

A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to a purchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Opportunity object to display an error message if the Stage field is Closed lost and the Loss Reason field is blank. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

One scenario that could prevent an administrator from changing the relationship between work item and project custom objects from master-detail to lookup is that roll-up summary fields exist on the master object (project). Roll-up summary fields are fields that calculate values from related records in a master-detail relationship; they cannot be used in a lookup relationship. If roll-up summary fields exist on the project object, they would prevent the administrator from changing the relationship type unless they are deleted first. A junction object is not required to support a lookup relationship; it is only used when creating many-to-many relationships between two objects using two master-detail relationships. The lookup field in all the records containing a value or the lookup field being required for saving records are not scenarios that would prevent changing the relationship type; they are scenarios that would allow changing the relationship type without losing data or functionality. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Process Builder is a tool that can be used to automate business processes by creating record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can be used to create a flow that executes when an opportunity is closed won and creates a client welcome task and a welcome email for the primary contact. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5

To make sure the custom picklist field values are populated on contact when leads are converted, you need to create a custom picklist field on contact and map it to the corresponding field on lead.

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

To use Data Loader to mass import new records to a custom object from a new API, the administrator will need to append their security token at the end of their password to login. The security token is an alphanumeric code that is required for API access when logging in from an IP address that is not trusted by Salesforce. The security token can be obtained from the user’s personal settings or by resetting it via email. Adding a permission set, resetting the password and the security token, or using the Data Import Tool are not necessary for using Data Loader. References: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_token.htm &type=5

Lightning record page is a type of page that should be created to meet this requirement. Lightning record page allows an administrator to customize the layout and components for a specific object record page in Lightning Experience or the Salesforce mobile app. To create tabs for account details, related lists, and chatter feeds, use the Tabs component in the Lightning App Builder and drag the desired components to each tab. References: https://help.salesforce.com/s/articleView? id=sf.app_builder_record_page.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_tabs.htm &type=5

Two options that should be added to Lightning record pages to make sales reps aware when they are speaking with high-profile customers are:

• Custom Component, which can display a custom message or icon on the record page based on certain criteria such as account rating or industry. For example, an administrator can create a custom Lightning Web Component that shows a star icon on account record pages if account rating is Hot or Warm.
• Component Visibility Filter, which can control when a component is visible on a record page based on field values of that record. For example, an administrator can add a component visibility filter to an existing component such as Path or Highlights Panel that makes it visible only if account rating is Hot or Warm. Highlight Panel, Action and Recommendations, and Rich Text Area are not options that can be used to make sales reps aware when they are speaking with high-profile customers. References: https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.htm&type=5

A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts, etc., to different users based on their profile or role. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. In this case, since Universal Containers has three separate lines of business with specific fields for each line; and since sales team needs different fields than service team; the administrator should create three record types for each line of business; and create two page layouts for each record type - one for sales team and one for service team. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm &type=5

To make a tab hidden in the All App Launcher or visible in any app, but still allow a user to view records that would normally be found under this tab, the administrator should use Tab Settings on a profile. Tab Settings control the visibility and default behavior of tabs for each app in an org. The administrator can set a tab to Hidden, which means it will not appear in any app or in the All App Launcher, but users can still access records via other means such as search or reports. Object Permissions, App Permissions, and Org-Wide Defaults are not related to tab visibility. References: https://help.salesforce.com/s/articleView?id=sf.customize_tabs.htm &type=5

Record types allow you to update the options in a picklist based on the kind of opportunity.

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

To ensure extra steps only appear when creating open house records for condominiums, an administrator can use two methods: create two page layouts; and use business processes and record types to display appropriate picklist values. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. An administrator can create two page layouts for open house records - one for houses and one for condominiums - and include different fields or sections for each page layout based on their requirements. A business process is a feature that allows administrators to define and enforce stages that records must go through based on their record type such as lead status or opportunity stage. A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts etc., to different users based on their profile or role. An administrator can create two record types for open house records - one for houses and one for condominiums - and assign different business processes and picklist values for each record type based on their requirements. References: https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

To identify why a user is unable to log in to Salesforce, the administrator should review the login history for the user. The login history shows the date and time of each login attempt, the source IP address, the browser and platform used, the login type (such as username and password or single sign-on), and the status (such as success or failure). The login history can help troubleshoot common login issues such as incorrect username or password, invalid security token, IP restrictions, or login hours violations. Checking the attempted logins by running the setup audit trail, pulling the password history, or resetting the security token for the profile will not help identify why a user is unable to log in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

Account and contact are two records that can be created when using the lead conversion process. The lead conversion process converts a lead into an account, a contact, and optionally, an opportunity. References: https://help.salesforce.com/s/articleView?id=sf.convert_lead.htm &type=5

To make sure that all of the Salesforce users log in using the branded login URL after deploying my domain, and give them a grace period for updating their bookmarks, the administrator should set the Redirect policy to Redirect with a warning to the same page within the domain. This will redirect users who try to log in from https://login.salesforce.com or another domain to https://nto.my.salesforce.com, and show them a warning message that they need to update their bookmarks. Setting the Login policy or preventing login from https://login.salesforce.com will not redirect users or give them a warning. Filtering with Form Factor will not affect login URL. References: https://help.salesforce.com/s/articleView?id=sf.domain_mgmt_redirect.htm &type=5

Component visibility allows you to restrict the visibility of a related list based on a permission set.

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

Delegated approver is a feature that should be used to fulfill this requirement. Delegated approver allows users to delegate their approval authority to another user for a specified period of time, such as when they are out on vacation. Users can specify which approval requests they want to delegate and who they want to delegate them to. References: https://help.salesforce.com/s/articleView?id=sf.approvals_delegate.htm &type=5

The Knowledge Lightning component is a component that allows users to access articles from the Service Cloud Console app. However, if users want to access articles from a different app that does not use the console, they can use the Knowledge related list instead. The Knowledge related list shows articles related to a record based on data categories and shows article details such as title, summary, rating, and view count. To add the Knowledge related list to a record page, an administrator can use the page layout editor and drag and drop the Knowledge related list to the appropriate section on the page layout. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_lightning_component.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_related_list.htm &type=5

Lightning page allows you to customize a record page and add a screen flow as a component. You can use the Lightning App Builder to drag and drop the Flow component onto the page and select the screen flow you want to display.

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

A validation rule is a tool that allows administrators to enforce data quality and integrity by preventing users from saving records that do not meet certain criteria or conditions. For example, a validation rule can display an error message if a user enters an invalid value in a field. In this case, the administrator can create a validation rule on the account object that displays an error if the account annual revenue field is below 0 or greater than 100 billion. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

Case escalation rules are used to escalate cases that have not been resolved within a certain time frame by changing the case owner, sending email notifications, or triggering workflow actions. You can use these actions to alert the appropriate users or groups when a case needs urgent attention or escalation. References: https://help.salesforce.com/s/articleView?id=sf.customize_caseesc.htm &type=5

Validation rules are a way to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. They can be used to require users to follow the status values as they are on the path and prevent them from reverting the case back to a previous status by using formulas that compare the old and new values of the status field. Global value picklists are a way to create and maintain picklist values that can be shared across multiple fields, but they do not enforce any logic or order on the values. Predefined field values are a way to set default values for fields on path settings, but they do not prevent users from changing them later. Dependent picklists are a way to filter the values of one picklist based on the value of another picklist, but they do not prevent users from going back to a previous value. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

A roll-up summary field is a type of field that calculates values from related records, such as the count of child records or the sum of a field on child records. In this case, the administrator can add a roll-up summary field to the open house object to track the number of visitors by counting the child records on the visitors object. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

A lookup relationship is a type of relationship that links two objects together, but does not affect security or deletion. It can be used to create a relationship between shipments and accounts where shipments should have a lookup to accounts; this way, shipments can show related account information on their records, but when an account is deleted, the shipments remain. Accounts should have a lookup to shipments is not a valid option because it does not match the requirement of seeing all shipment items from an account page; it would show related account information on shipment records instead. Shipments should have a master-detail to accounts or accounts should have a master-detail to shipments are not valid options either because they do not match the requirement of keeping shipments when an account is deleted; they would delete shipments along with their master account records. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

The Stage Setup Flow is a tool that allows administrators to customize stages for leads and opportunities based on best practices from Salesforce experts. The Stage Setup Flow guides administrators through a series of questions about their sales process and then creates or updates stages for leads or opportunities accordingly. The Stage Setup Flow also provides tips and resources for each stage such as key fields, guidance for success, reports and dashboards, etc. References: https://help.salesforce.com/s/articleView?id=sf.stages_setup_flow_overview.htm &type=5

Path is a feature that can be used to visually see the sales stages on an opportunity page. Path can include guidance and key fields for each stage to help users move opportunities along the sales process. Guidance can provide tips, policy information, or best practices for each stage. Key fields can display important fields that users need to fill in or update for each stage. References: https://help.salesforce.com/s/articleView?id=sf.path_overview.htm &type=5

Recurring tasks are tasks that repeat at regular intervals, such as daily, weekly, monthly, etc. They can be created by users who have the permission to create recurring tasks, which can be enabled by administrators in the user profile settings. Flow, workflow rule, and recurring activities are not valid options for creating recurring tasks in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.tasks_recurring.htm &type=5

Contact, lead, and person account are three objects that will have the individual field available for tracking data privacy information when data protection and privacy is enabled for an org. The individual object is an object that stores data privacy preferences and requests for customers who are subject to privacy regulations such as GDPR; it can be linked to contact, lead, or person account records using the individual field. Case and opportunity, account and user, or individual, user, and account are not combinations of objects that will have the individual field available for tracking data privacy information; they either do not store customer data or do not support individual object relationships. References: https://help.salesforce.com/s/articleView?id=sf.individual_object.htm &type=5

To help agents fill in event details and request dates for open house events without double-booking them, the administrator should create an approval process on the Campaign object, which is used to manage marketing events in Salesforce. The approval process can define entry criteria based on campaign fields such as type or status, specify initial submission actions such as sending email alerts or updating fields, assign approvers who can review and approve event requests, and specify final approval actions such as creating tasks or updating fields. Creating a workflow rule, a sharing rule, or a campaign will not help agents request event dates or prevent double-booking. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

To make it easy for approvers to respond to approval requests, the administrator should configure three settings:

• Update the organization’s chatter setting to allow approvals, which enables approvers to approve or reject requests from chatter feeds or email notifications
• Enable the organization’s Email approval response setting, which allows approvers to reply to approval request emails with keywords such as APPROVE or REJECT
• Add the Items to approve component to the approvers home page, which shows a list of pending approval requests that can be acted upon with one click Specifying initial submission actions within the approval process will not affect how approvers respond to requests. Creating a flow to automatically approve all records will bypass the approval process altogether. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_email.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_one_click.htm&type=5

Campaign influence is a feature that allows users to track how campaigns have influenced opportunities and measure the return on investment (ROI) of marketing efforts. Users can see which campaigns have influenced an opportunity on the related list and assign different attribution models to calculate the campaign influence. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_influence.htm &type=5

Data Import Wizard allows you to import up to 50,000 records at a time.

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

Split views are a feature that allows users to view records as a split list on object home pages in Lightning Experience apps that use console navigation. Split views show records in two panes: a list view pane on the left and a record detail pane on the right. Users can switch between different list views and records without losing context or scrolling. However, split views are only available on standard objects such as accounts, contacts, leads, opportunities, cases, etc., and not on custom objects such as shipments. References: https://help.salesforce.com/s/articleView?id=sf.lex_split_view.htm &type=5

To access the account object in Salesforce, users need to have permission to the account object on their profile or permission set. Permission to an object determines what users can do with records of that object, such as create, read, edit, delete, view all, or modify all. If users do not have permission to an object, they will not be able to see or access that object in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.htm &type=5

Native debug feature is a tool that can be used to identify the problem with the new flow. Native debug feature allows users to test a flow by running it with different input values and inspecting the output values at each element. Users can also see error messages and warnings that indicate where the flow failed or might fail. References: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm &type=5

Flow Solutions are pre-built flows or templates that can be installed from AppExchange and customized to meet specific business needs. For example, Flow Solutions can provide common use cases such as lead generation, document generation, payment processing, and more. In this case, the administrator can use a Flow Solution that provides a mortgage calculator and generates leads for loans. Flow Solutions are easy to install and configure, and can help save time and budget for projects. References: https://help.salesforce.com/s/articleView?id=sf.flow_solutions.htm &type=5

Field update and email alert are two types of automated actions that can be added as part of the approval process. Field update allows you to change the value of a field on a record when it is submitted, approved, rejected, or recalled. Email alert allows you to send an email to one or more recipients when a record is submitted, approved, rejected, or recalled.

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

A dashboard filter is a feature that allows users to filter dashboard components by one or more field values without changing the underlying report data. For example, a dashboard filter can allow users to view cases by origin, status, or owner. A dashboard filter consists of a filter name, one or more source fields, and one or more filter values. Users can apply one or more filters to see different views of the dashboard data. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_filters.htm &type=5

Process Builder is an automation tool that allows you to create processes that perform actions based on criteria that you specify. You can use Process Builder to update fields on related records when a record is created or updated. To meet the requirement of updating the parent object Referral when the Referral Date field is updated on the custom object Referral Source, you need to create a process that triggers when a Referral Source record is updated, checks if the Referral Date field has changed, and updates the Referral Date field on the related Referral record. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

To advertise on TV, radio, print, and social under one banner called New Runners and aggregate total statistics for this marketing effort, an administrator should use Parent campaign field on Campaign object. This field allows creating hierarchical relationships between campaigns by specifying one campaign as parent of another campaign. Parent campaigns roll up statistics from child campaigns such as number of leads generated, amount of revenue won etc. For example, an administrator can create four child campaigns for TV, radio, print and social ads respectively and link them to one parent campaign called New Runners using Parent campaign field. Junction object, lookup relationship, and master-detail relationship are not features related to Campaign object or hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_parent.htm &type=5

A restricted picklist is a type of picklist that enforces the integrity of the picklist values by allowing only values defined in the picklist during data entry or import operations. If the restricted picklist checkbox is checked for a picklist field, then any records with values not defined in the picklist will cause errors during import operations. However, if the restricted picklist checkbox is unchecked for a picklist field, then any records with values not defined in the picklist will be imported without errors. References: https://help.salesforce.com/s/articleView?id=sf.picklist_limitations.htm &type=5

Lead assignment rule is a feature that can be used to route new leads to the correct sales person based on the lead address. Lead assignment rule can assign leads to users or queues based on certain criteria, such as lead source, industry, or location. Lead assignment rule can also send email notifications to the new lead owners or other recipients. References: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm &type=5

Flow Builder is a tool that can be used to create an automated way to delete records based on field values. Flow Builder can create flows that define the logic and actions for deleting records, such as finding records that match certain criteria and deleting them in bulk. Flows can be scheduled to run at regular intervals or triggered by other events or processes. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_delete.htm &type=5

To provide a summary of org’s security health, an administrator should run a Health Check that compares org’s settings against baseline settings defined by Salesforce Security Baseline Standard or industry standards such as CIS (Center for Internet Security) Benchmark Standard. Health Check generates an overall health score based on how org’s settings match with baseline settings for various security categories such as Password Policies, Network Access, Session Settings etc. Health Check also provides recommendations for improving org’s security health score by adjusting settings that do not match with baseline settings. Changing Org-Wide Default to private, turning on Event Monitoring, or downloading user login data will not provide a summary of org’s security health. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.htm &type=5

One of the possible reasons why an administrator is unable to add a new user in Salesforce is that the username is already in use by another user in any Salesforce org. Usernames must be globally unique across all Salesforce orgs, so the administrator needs to choose a different username for the new user. References: https://help.salesforce.com/s/articleView?id=sf.users_add.htm &type=5

To customize the campaign member status picklist values themselves, marketing users need two things: a marketing user feature license and edit permission for campaigns. A marketing user feature license enables users to create, edit, and delete campaigns; manage campaign members; and update campaign history via the import wizards or API. Edit permission for campaigns allows users to modify existing campaigns and their related records such as campaign members and campaign member statuses. References: https://help.salesforce.com/s/articleView? id=sf.campaigns_enable.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.htm &type=5

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can require users to select a product type or check a needs review box when saving an opportunity by using an OR function that evaluates both fields. If neither field is populated, then the validation rule will prevent users from saving records with an error message. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

Two-factor authentication requires users to verify their identity with two pieces of information when they log in to Salesforce. One piece is their username and password, and the other is a verification code from an authenticator app or email or SMS.

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

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can ensure that house showings are scheduled within the current year by comparing the showing date field with a formula that returns the current year. If the showing date field contains a date outside of the current year, then the validation rule will prevent users from saving or importing records with an error message. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

To transfer data from a lead custom field to an opportunity field upon lead conversion, an administrator needs to create a custom field on the opportunity object that matches the data type and length of the lead custom field, and then map the two fields using the lead field mapping tool under setup. This will ensure that the value of the product category field on the lead is copied to the corresponding field on the opportunity when the lead is converted. References: https://help.salesforce.com/s/articleView?id=sf.leads_customize_map.htm &type=5

Custom object and master detail field are two steps that should be configured to meet this requirement. Custom object can be used to create a new object for shoe design that can store information about different designs and stages. Master detail field can be used to create a relationship between Product and Shoe Design that prevents deletion of Shoe Design records and allows multiple designs for one product. References: https://help.salesforce.com/s/articleView?id=sf.customize_customobjects.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Conditional visibility is a feature that allows administrators to show or hide screen components in a flow based on certain conditions or criteria. For example, conditional visibility can show only one question on a screen depending on the value of another field or variable. Conditional visibility consists of one or more rules that define when to show or hide a component based on an expression that evaluates to true or false. In this case, the administrator can use conditional visibility to hide the unnecessary question on the screen flow based on the scenario. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp.htm &type=5

Master-detail lookup is a type of relationship field that can be used to create a relationship between Account and Shoe and prevent orphaned Shoe records. Master-detail lookup establishes a parent-child relationship between two objects, where the parent record controls certain behaviors of the child record, such as security, ownership, and deletion. If the parent record is deleted, all the child records are deleted as well. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

 Geolocation fields allow you to store the latitude and longitude coordinates of a location. They can be used to calculate distances between records and display maps of accounts, contacts, leads, or other custom objects. References: https://help.salesforce.com/s/articleView?id=sf.customize_geoloc.htm &type=5

To track all cases that reference the new product and give read/write access to the product’s two lead engineers, the administrator should create a queue and a criteria-based sharing rule. The queue will allow assigning cases that meet certain criteria, such as having a specific value in the Product field, to a group of users. The criteria-based sharing rule will grant read/write access to the queue members for cases that match the same criteria. References: https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.sharing_criteria.htm &type=5

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadrules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.htm &type=5

Campaign Status is a standard picklist field on the Campaign object that indicates whether a campaign is planned, in progress, completed, or aborted. Campaign Member Status is a custom picklist field on the Campaign Member object that indicates how a person responded to a campaign, such as sent, responded, registered, attended, etc. To add a new picklist value for Campaign Status, you need to edit the field in Object Manager. To add a new picklist value for Campaign Member Status, you need to modify the field on the Campaign Member Statuses related list on the Campaign page layout. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.htm &type=5

Support processes allow you to define different status values for different record types on cases.

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

One possible reason why a manager receives an error when trying to approve a record is that the user in the next approver step is inactive or missing, which means there is no valid user to assign the record to after approval. To troubleshoot this issue, an administrator should check if the user in the next approver step is active and exists in Salesforce; if not, they should activate or create the user or change the approval process to assign the record to another user. Adding a delegated approver for the next approver in the process does not solve this issue because delegated approvers are only used when approvers are unavailable; they do not replace approvers who are inactive or missing. Updating the field level security to view on fields that are updated in the process does not solve this issue because field level security does not affect approval processes; it only affects what fields users can see or edit on page layouts. Reviewing the page layout to ensure fields updated in the process are visible does not solve this issue because page layouts do not affect approval processes; they only affect what fields users can see or edit on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5