Package Items

From AgileApps Support Wiki
Revision as of 18:22, 26 March 2015 by imported>Aeric (→‎Object Aspects)

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
    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.
    (An installed calendar 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 Items are Applied

The principles that follow summarize the behavior of package items at installation time. Detailed tables list the behavior for individual items, following the summary.

Principles
  • New items in the Package are added to the subscriber's system, while items with the same ID are replaced, or updated.
Note:
All aspects of an object (fields and forms, validations, and so on) are given a Globally Unique ID or GUID. Those IDs are preserved when the package is installed, which allows existing items to be replaced while new items are added. (When the overwrite option is chosen, items on the target system that do not have a matching GUID in the package are deleted.)
  • 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.
  • 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.)
Object Aspects

This table describes the behavior of individual Object Aspects.

Object Aspect Installed when...
Added if New Updated Deleted if Old
Business Rules Packaging option
Custom Form Actions Packaging option
Document Templates Packaging option
Email Templates N N
External Data Source definitions Packaging option
Fields Packaging option
Field Audit Log Settings n/a
Field Scripts Packaging option
Forms Packaging option
Form Scripts Packaging option
Indexes Y
Layout Rules Packaging option
Macros Packaging option
Processes N
Quick Text (Cases Objects only) N N
Record Locators n/a n/a
Subforms Packaging option
Validations Packaging option
View definitions * Packaging option
Web Forms N
* View definitions are included only when they are visible to all, or to an included Role. Private views are not included.
Application Elements

This table describes the behavior of other platform elements that go into an application.

Application Element Included when Installed when
Selected or if Referenced by Added if New Updated Deleted if Old
Application Package Dependency N
Classes Business Rule
Macro
N
Customer Satisfaction Surveys ServiceDesk N n/a
Case Analytics Dashboard ServiceDesk n/a Packaging option
Dashboards if visible to all, a Role, or a Team Packaging option
Global Picklists Object Field N
Global Template Variables Custom Form Action (JavaScript)
Email Template
Document Template
N N
Knowledge Base articles not included
Knowledge Base categories not included
Mapping Profiles Packaging option
Object definitions Lookup field
Rollup Summary Field
Packaging option
Object records Package Data class as defined by the class
Pages Custom Form Action
Dashboard
Site
Web Tab
Packaging option
Reports Dashboard Packaging option
Roles Application
Process
Team Data Sharing Policy
Subscriber choice N
Sites Application Packaging option
SLAs not included
Static Resources Packaging option
Tab Preferences Role Packaging option
Team definitions Business Rule
Macro
Process
Team Data Sharing Policy
N N
Team-object Business Rules Team Packaging option
Team Data Sharing Policies Packaging option
Translation Workbench n/a
Users Object * n/a
User-object Business Rules Users Object Packaging option
User-object Fields Users Object Packaging option
View Preferences Role Packaging option
Web Services ** Business Rule
External Data Source
External Lookup
Process
N
Web Tabs Application Packaging option
* The Users Object should be included to the package whenever fields or business rules have been added that the application references.
** When a Web Service is updated, the service end-point URL is left alone. (It is expected that a development environment, test environment, and production environment will be using different services.)
System Elements

This section describes important system-object and system-configuration items:

System Element Included when Installed when
Selected or if Referenced by Added if New Updated Deleted if Old
Access Profiles not included
Business Hours Calendars Process N N
Email Channel settings not included
Facebook Channel settings not included
LDAP Configuration not included
Marketplace listings not included
Service Portal settings not included
Scheduled Jobs * not included
Single Sign-On settings not included
Twitter settings not included
* Scheduled Rules, on the other hand, are included, along with other Business Rules.