When an opportunity has a closed date that is pushed more than 30 days, manager approval is require An approval process is in place but Reps frequently forget to submit for approval to run the process. How can an app builder ensure that these opportunities are submitted into the approval process?
The correct answer is C. Submit the record for approval from an automated process.
The issue is not the approval process itself. The issue is that sales reps forget to manually submit the Opportunity. Salesforce supports submitting records for approval from automation, including Flow's Submit for Approval action. Salesforce also documents using an after-save record-triggered flow to automatically submit records into an approval process.
A does not solve the problem because changing approval entry criteria does not automatically submit the record. B only reminds the manager and does not run the approval process. D is unrelated to automatic submission.
===========
An app builder wants to add the option to 'Send New Email' from Leads, Contacts, and Accounts for users on mobile. What is the benefit of using global actions to accomplish this?
Global actions are designed to be available broadly, not only from one object's record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.
This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.
Why others are incorrect: A is incorrect because a global action layout does not automatically clone the default page layout. B is incorrect because the Lightning Component Library is not the reason to use global actions. C is incorrect because global actions are not record-specific; object-specific actions are record-specific.
===========
When a sales rep submits an account for approval, Universal Containers Wants the user to answer additional questions via a popup window to populate Additional record fields. What should an app builder use to achieve the desired result?
A Screen Flow is the best declarative tool when the user must answer questions through a guided UI and use those answers to update record fields. Salesforce documents that screen flows provide a UI that guides users through a business process, and they can be launched from quick actions or Lightning pages.
A custom button or action can launch the flow, collect the extra approval-related information, update the Account fields, and then continue the approval submission logic.
Why not others: A. Custom object only stores data; it does not provide the popup/question flow. B. Visualforce could be custom-coded, but Flow is the declarative App Builder solution. D. Custom Lightning component requires development and is not the best declarative answer.
===========
An app builder has created a new report type but users are unable to select It from the Report Type list when making a new report for records they own. What could be causing this issue?
If a new report type is created but users cannot select it, it is usually because the report type status is ''In Development''. Salesforce only makes report types available in the Report Type list once they are deployed. (Salesforce Help)
B . Access to objects could prevent report creation, but the question assumes the user can create reports on records they own.
C . Deploye is the correct deployed state, which would make the report type selectable.
D . Create and Customize Reports permission is required, but the question specifies users are trying to create the report.
===========
AW Computing has a custom object for service plans. A service plan needs to be associated to one and only one contact. The support manager noticed if the wrong contact is associated, the reps are unable to Change the contact. The app builder already confirmed the user has correct access to the field and there are no validations associated with the service Plans. What could be causing the issue?
The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.
A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.
Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.
A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.
===========
James Davis
1 month agoElizabeth Garcia
2 months agoWilliam Nguyen
2 months agoRebecca Turner
3 months agoHeather White
3 months agoBetty Collins
4 months agoKaren Bell
4 months agoRebecca Martinez
5 months agoDonna Perez
5 months agoBrian Evans
6 months agoJames Bell
6 months agoDavid Wright
6 months agoRebecca King
6 months agoElizabeth Lewis
6 months agoJohn Green
6 months agoHollis
7 months agoEmeline
7 months agoEmmett
7 months agoCaren
8 months agoMarsha
8 months agoChaya
8 months agoGlendora
8 months agoTrina
9 months agoAliza
9 months agoWillard
9 months agoShannon
9 months agoPaulene
10 months agoJamal
10 months agoNa
10 months agoFloyd
10 months agoNaomi
11 months agoShizue
11 months agoMalinda
11 months ago