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
Winifred
3 months agoNatalie
3 months agoBarbra
1 months agoSylvie
2 months agoTy
3 months agoKrissy
3 months agoRene
3 months agoCasandra
2 months agoLavera
2 months agoKarrie
3 months agoAlline
3 months agoSantos
3 months agoMose
3 months ago