Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Salesforce CRM Administration

You're reading from   Mastering Salesforce CRM Administration An Advanced Administration Certification Handbook

Arrow left icon
Product type Paperback
Published in Mar 2017
Publisher
ISBN-13 9781786463180
Length 412 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Rakesh Gupta Rakesh Gupta
Author Profile Icon Rakesh Gupta
Rakesh Gupta
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. A Deep Dive into the Salesforce Lightning Experience FREE CHAPTER 2. Security Settings in Salesforce 3. Territory Management 4. Extending Salesforce with Custom Objects and Applications 5. Getting More Value from Sales Cloud 6. Increasing Service Agent Productivity by Using Service Cloud 7. Optimizing Business Processes with Visual Workflow and Approval Processes 8. Automating Complex Business Processes 9. Analyzing Productivity with Reports and Dashboards 10. E-mail and Mobile Administration 11. Different Ways of Deploying an Application between Environments 12. Basics of Apex and Visualforce Page

Deploying using packages

Packages are containers that can hold metadata components, either one component or a group of components. They are mainly used to distribute an app; the best example of this is Salesforce AppExchange. Packages are also used to deploy the metadata components between any orgs, for example, Salesforce Developer Edition to one of your Sandboxes. There are two types of Packages available and they are as follows:

Unmanaged Packages

Managed Packages

Developers can view and modify the Apex code of components included in an unmanaged package.

It is not possible to view the code of components, for example, Apex class or Apex trigger, in this package.

Components can be edited in the organization after the installation.

Components cannot be edited in the organization after the installation.

The source organization has no control over the package once it is installed in the customer org; this is because the code can be altered in the target organization.

The code...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime