A business user wants a quick way to edit a record's status and enter a custom due date field from the record's feed in Salesforce Mobile App.
What should be used to accomplish this?
To allow quick editing of a record's status and entering a due date from the record's feed in the Salesforce Mobile App:
A . Custom action. This option enables users to perform specific tasks directly from the record page in the Salesforce Mobile App, such as editing fields.
Steps to create a custom action:
Navigate to Setup Object Manager select the relevant object.
Click Buttons, Links, and Actions New Action.
Set Action Type to 'Update a Record'.
Configure the action layout to include the Status and Custom Due Date fields.
Add the action to the Salesforce Mobile layout.
This setup provides an efficient way for users to update key fields without navigating away from the record feed.
For detailed setup instructions, see Salesforce's documentation on Creating Quick Actions.
Cloud Kicks wants to summarize the number of open Cases related to an Account, as well as the number of closed Cases to indicate whether customer support utilization is high, medium, or low. Two number fields have been created: NUM_Open_Cases__c and NUM_Closed_Cases_c
Which two automation solutions would meet these business requirements?
Choose 2 answers
Process Builder and Apex are two automation solutions that can meet the business requirements of summarizing the number of open and closed Cases related to an Account. Process Builder can create a process that updates the custom fields on Account based on changes in related Cases. Apex can write a trigger that performs the same logic using code. AppExchange and Workflow are not automation solutions for this requirement, but sources of apps or components and tools for creating workflow rules respectively.
Ursa Major Solar (UMS) is looking to hire some new employees. UMS wants to allow the same applicant to apply for multiple open positions using a single application.
What should an app builder recommend to meet these requirements?
Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.
An app builder wants to use Process Builder to automate some of the work being done by the sales team.
What are three capabilities ofProcess Builder that can improve productivity?
Choose 3 answers
Send an email alert, update a related record, and create a child record are three capabilities of Process Builder that can improve productivity for the sales team. Process Builder can automate these actions based on criteria or events that occur on records or objects. Send an outbound message and delete a related record are not capabilities of Process Builder, but of other tools such as Workflow Rules or Apex.
Universal Containers uses a custom object called Reviews to capture information generated by interviewers during the candidate process. The Review records are visible to any user that has access to the related custom Candidate record. The VP of Human Resources wants the comment field on the Review to be private to anyone outside of the MR department
How should the app builder meet this requirement?
Create a page layout with the field and use field-level security to hide the field from all other users is how the app builder should meet the requirement of making the comment field on Review private to anyone outside of HR department. Field-level security can control which profiles can view or edit a field on a record. Create an Apex sharing rule, create a sharing rule to share the field with VP of HR with Role and Subordinates, and create a page layout with the field for HR users and another page layout without the field for all other users are not valid or feasible solutions for this requirement.
Currently there are no comments in this discussion, be the first to comment!