Universal Containers wants to give sales managers the ability to quickly provide sign off on an Opportunity via the Opportunity record page when a sales rep
has discounted a deal by 20% to 30%.
Which two features should be used for this requirement?
Choose 2 answers
To facilitate quick managerial sign-off on discounted opportunities:
B . Dynamic Actions: Allows the display of specific actions on the Opportunity record page based on certain conditions, like the discount percentage.
D . Approval Process: Configures a formal sign-off process for records meeting specific criteria, such as discount ranges between 20% to 30%.
Steps to set up:
Configure an approval process for opportunities where the discount is between 20% and 30%.
Use Dynamic Actions to conditionally show the approval action directly on the Opportunity record page based on the discount percentage.
This setup allows sales managers to efficiently review and approve discounted deals directly from the Opportunity record page.
Universal Container's sales reps can modify fields on an opportunity until it is closed.
The sales operations team has access to modify the Post-Close Follow-up Date and Post-Close Follow-up Comments fields after the opportunity is closed. After the
opportunity is closed, the rest of the fields are read only.
How should these requirements be met?
To manage field editability based on the opportunity status:
C . Use field-level security on page layouts with record types to restrict editing fields. This combination allows for different layouts and editable fields based on the status of the record (e.g., closed or open).
Steps to implement:
Create or adjust record types for open and closed opportunities.
For each record type, create a specific page layout.
On the page layout for closed opportunities, set the majority of fields to read-only using field-level security, except for the 'Post-Close Follow-up Date' and 'Post-Close Follow-up Comments' fields.
Assign the appropriate page layouts to the respective record types.
Update profiles or permission sets to use these record types and page layouts accordingly.
This setup ensures that sales reps can modify fields only when the opportunity is open, and the sales operations team can edit specific fields after closure.
Universal Containers wants to give sales managers the ability to quickly provide sign off on an Opportunity via the Opportunity record page when a sales rep
has discounted a deal by 20% to 30%.
Which two features should be used for this requirement?
Choose 2 answers
To facilitate quick managerial sign-off on discounted opportunities:
B . Dynamic Actions: Allows the display of specific actions on the Opportunity record page based on certain conditions, like the discount percentage.
D . Approval Process: Configures a formal sign-off process for records meeting specific criteria, such as discount ranges between 20% to 30%.
Steps to set up:
Configure an approval process for opportunities where the discount is between 20% and 30%.
Use Dynamic Actions to conditionally show the approval action directly on the Opportunity record page based on the discount percentage.
This setup allows sales managers to efficiently review and approve discounted deals directly from the Opportunity record page.
At Ursa Solar Major, only users with the Outer Planets profile need to see
the Jupiter field on the Solar System object.
How should the app builder satisfy this requirement?
To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:
C . Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.
Steps to set up field-level security:
Navigate to Setup Object Manager Solar System.
Select Fields & Relationships Jupiter field.
Click Field-Level Security.
For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.
For the Outer Planets profile, check Visible to grant access.
This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.
For more information on field-level security, check Salesforce's guide on Field-Level Security.
The VP of sales at AW Computing would like a Roll-Up Summary field on the Account object to aggregate the amount of opportunities related to an Account. The app builder is unable to implement this change.
Why is the app builder unable to fulfill the request?
The inability to create a Roll-Up Summary field in this context can be attributed to:
B . The organization has Advanced Currency Management enabled. When Advanced Currency Management (ACM) is enabled, it affects how currency data is managed and aggregated, impacting the functionality of roll-up summary fields that involve currency amounts across different records.
To address this limitation, consider using custom reporting or a custom solution like a trigger or a scheduled batch class to manually calculate and update the total.
Veronika
20 days agoElliot
23 days agoCristy
2 months agoLucia
4 months ago