Difference between revisions of "Package Items"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 1: Line 1:
The following platform elements can be selected for inclusion in a [[Package]] as ''package items''. When selected, the dependent elements shown in the table are automatically included. (Things that are ''not'' dependent are shown as excluded.)
Platform elements can be selected for inclusion in a [[Package]] as ''package items''. When selected, dependent elements are automatically included. Items that are related, but upon which the selected item does not actually ''depend'' are excluded by default--although they can generally be selected manually, if desired.


====Standard Dependencies====
====Standard Dependencies====

Revision as of 03:20, 4 March 2015

Platform elements can be selected for inclusion in a Package as package items. When selected, dependent elements are automatically included. Items that are related, but upon which the selected item does not actually depend are excluded by default--although they can generally be selected manually, if desired.

Standard Dependencies

Platform Element Dependent Elements
  • Application
  • Excludes Reports and Web Forms
    Reports can be individually selected. Reports on an object are not automatically included.
  • Excludes data
    Data is not included automatically. Java code can be written to create Package Data classes that add selected records during packaging, and that take the records out when the package is installed.
  • Classes (includes
    user-created classes)
  • The Business Hours Calendar used in processes.
    (A calendar modified by the installer is never overwritten, so installers are free to modify the calendar to suit their purposes.)
  • Teams and Roles used in Process tasks
  • Sites
  • Includes Teams and Roles involved
  • Includes Child Teams if the Include Child Teams option is selected for that team
  • Includes localized labels and items


  • Web Tabs

Special Dependencies

When the following elements are added to a package, the listed items are added as dependencies:

Team Data Sharing Policies
Roles and Teams included as dependencies
  • If the Include Child Teams checkbox is enabled, the child teams of the selected teams in the Data Sharing Policy are added as dependencies
Objects in a Master-Detail relationship

Notepad.png

Note:
The "Master-Detail relationship" option on a Lookup field has been deprecated. This section is provided for legacy objects that have a Lookup field for which that option has been selected.
Learn more: Master-Detail relationships

  • If a Detail object is added to a Package, the Master object is added (automatically) as a dependent object
  • If a Master object is added to a Package and if that Master object includes any Rollup Summary Fields, then the Detail object is added (automatically) as a dependent object
  • When a Tenant installs a Package, the Rollup Summary Fields limit defined in Manage Tenant Capabilities is honored
  • If the limit is exceeded, the installation process will stop and cannot proceed
  • In order to complete the installation, delete existing Rollup Summary Fields to reduce the total number to within the defined limit
  • After packaging, do not add or remove any Master-Detail relationships; doing so may cause unexpected results and/or loss of data

Items that are Never Packaged

These platform elements are never added to a package. Customizations made by the subscriber remain intact.

How Package Elements are Applied to the Subscriber's System

These principles describe the behavior of a package at installation time. A detailed table of elements follows.

  • New items in the Package are added to the subscriber's system.
  • If the subscriber created a new platform element with the same name as an item included in the package, the subscriber gets an error. (The error occurs immediately after they select the package. Installation is not allowed to proceed.)
  • With few exceptions, modified items in the Package replace the versions that came from a previous Package.
    The exceptions are:
  • Global Picklists -- Subscribers are expected to have added items and modified labels, so they are left intact.
  • Email Templates -- Subscribers are expected to have customized email templates with their return address, signature text, and possibly logo images, so they are left intact.
  • Roles -- During installation, the subscriber has the option of merging or overwriting roles that are included in the package.
  • __TBD: Confirm that Web Services are not part of this list.__
  • Items deleted from the packager's application are never deleted from the subscriber's system unless the Overwrite Previous Package option has been enabled by the Service Provider, and the packager has chosen the Overwrite option. (Then, and then only, items deleted from the Service Provider's system are deleted from the subscriber's system when the package is installed.)
Platform Element Added if New Replaced if Modified Deleted if Old
Application settings
Objects and Object Aspects
Business Rules
Custom Form Actions
Document Templates
External Data Source definitions
Fields
Field Scripts
Forms
Form Scripts
Indexes
Layout Rules
Macros
Processes
Record Locators
Validations
Web Forms
Access Profiles not included
Business Hours Calendars not included
Classes
Dashboards
Global Picklists
Mapping Profiles
Pages
Processes
Reports
Roles
Sites
SLAs not included
Static Resources
Tab Preferences
Team definitions
Team Data Sharing Policies
Translation Workbench
View Preferences
Web Services __TBD__
Web Tabs