The administrator at Cloud Kicks writes an assignment rule to send all cases created via email or the web to the Automated Cases Queue Any manually created cases should be owned by the agent creating them, however, the manually created cases now show the administrator as the owner.
What will the administrator find when troubleshooting this issue?
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
A Sales user is trying to manage Campaign Members for an upcoming networking event. The user can view the Campaign, but add new Campaign Members or update Member statuses.
How can an administrator troubleshoot this problem?
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
DreamHouse Realty requires that house showings be scheduled within the current year to prevent too many future showings from stacking up.
How can they make sure Showing Date is only populated with a date this years?
Lavera
7 days agoLeonardo
21 days agoAlethea
22 days agoBarb
2 months agoOren
2 months agoMargery
2 months agoShantay
3 months agoLynna
3 months ago