Marketing users at Cloud Kicks should be able to view and edit converted leads. The administrator has assigned them permission set with the View and edit Converted Leads permission.
Which two ways can the marketing users now access converted leads for editing?
Choose 2 answers
Two ways that marketing users can now access converted leads for editing are:
Find them in the global search result, by entering the lead name or other keywords in the global search box and selecting Leads from the drop-down menu. Converted leads will appear in the search result with a check mark icon next to them.
Utilize a list view where lead status equals Qualified, by creating or modifying a list view on the Leads tab and adding a filter for Lead Status equals Qualified. Converted leads will have Qualified as their lead status and will be visible in the list view. Searching the Recent Records component on the homepage or using Data Import Wizard will not allow users to access converted leads for editing. Reference: https://help.salesforce.com/s/articleView?id=sf.leads_view_converted.htm&type=5
Customer service accesses articles with the Knowledge Lightning component on the Service Cloud Console. Billing department users would like similar functionality on the case record without using the console.
How should the administrator configure this request?
An administrator at Ursa Major Solar just learned about the AppExchange and how helpful it can be to the company's business.
Which two actions can be accomplished via the AppExchange?
'Choose 2 answers
Support reps at Cloud Kicks (CK) are reporting that when they try to close a case, the Closed option in the Case Status picklist is missing. CK has asked the administrator to find a solution.
Why are the support reps unable to see the Closed option in the specified piclist?
Cloud Kicks (CK) needs a new sales application. The administrator there is an application package on the AppExchange and wants to begin testing it in a sandbox to see If it addresses CK's needs.
What are two considerations when installing a managed package in a sandbox?
Choose 2 answers.
Two considerations when installing a managed package in a sandbox are:
The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. Reference: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5
Submit Cancel
Currently there are no comments in this discussion, be the first to comment!