Professional Documents
Culture Documents
• Functionality: If you’re seeking an app or component, what does it need to do? Which of these
features are “musthaves” and which are “nice-to-haves”?
• Budget: Are you looking for something free, or are you open to paying for the right solution?
• Stakeholder needs: Who will be using the offering? Make sure that you meet with these stakeholders to
understand their needs, expectations, and timelines
• Technical considerations: Does the offering need to be compatible with a particular Salesforce edition or
feature? What about Lightning Experience or the Salesforce1 app? Think about what’s unique to your
org, and take note of those items
• Provider tab (5): Tells you who built the offering and
how to contact them if you have questions or need
assistance.
• Free Trial: A free trial lets you experience the offering • Remember, it’s up to the provider to configure a test
in a writable Developer Edition org for a limited time drive or free trial, so you might not be able to try
period. every AppExchange offering
• The Application that you are looking for may be already in the AppExchange, and may also be Free
• For example, if you are required to implement an Advanced Quoting Tool, instead of starting from scratch, check
the AppExchange!
• Typically a package would contain Objects, Fields, Apex Code, Page Layouts, Reports, email template, etc…
• Packages can contain one component (e.g. an Apex Class) or hundreds of components
• Packages can be uninstalled at any point – causing all components installed as part of the package to be
deleted from the org
• The installer gets a copy of the components, and then can further customize as required
• Once an unmanaged package is distributed, the author of the code / package, will no longer have control over it
• Managed packages are typically for sale on the AppExchange and can be licensed
• The only requirement to create a managed package is that you’re using a Developer Edition organization
Once the Package components are installed, the Once the Package components are installed, editing the
components can be freely edited without any restriction components is not possible
Package components will count toward the Org. Limit Package components will not count toward the Org. Limit
Should not be used if the code being shared is intended Will preserve intellectual Property as it cannot be edited,
to be protected intellectual property or redistributed
Can be distributed via a link, but the distribution can’t be Distribution is controlled as package cannot be
controlled redistributed
• Applications, Components and Consulting Services are all available at the AppExchange
• Always check the AppExchange whenever you have a new Requirement within your Org.