Difference between revisions of "Package Items"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 274: Line 274:
|-
|-
| [[Service Portal]] settings    || colspan="3" align="center"|''not included''
| [[Service Portal]] settings    || colspan="3" align="center"|''not included''
|-
| [[Scheduled Jobs]]<br>(But note that [[Scheduled Rules]] are included, along with other [[Business Rules]])  || colspan="3" align="center"|''not included''
|-
|-
| [[Single Sign-On]] settings    || colspan="3" align="center"|''not included''
| [[Single Sign-On]] settings    || colspan="3" align="center"|''not included''

Revision as of 22:09, 9 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
    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 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.
  • __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.)
Object Aspects

This table describes the behavior of individual Object Aspects.

Object Aspect Added if New Updated Deleted if Old
Business Rules Y Y Packaging option
Custom Form Actions Y Y Packaging option
Document Templates Y Y Packaging option
Email Templates Y N N
External Data Source definitions Y Y Packaging option
Fields Y Y Packaging option
Field Audit Log Settings Y Y n/a
Field Scripts Y Y Packaging option
Forms Y Y Packaging option
Form Scripts Y Y Packaging option
Indexes Y Y Packaging option
Layout Rules Y Y Packaging option
Macros Y Y Packaging option
Processes Y Y Packaging option
Quick Text Y __TBD__ Packaging option
Record Locators Y Y Packaging option
Subforms Y Y Packaging option
Validations Y Y Packaging option
View definitions Y Y Packaging option
Web Forms Y N N
Application Elements

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

Platform Element Added if New Updated Deleted if Old
Application settings Y Y Packaging option
Access Profiles not included
Business Hours Calendars not included
Classes Y N N
Customer Satisfaction Surveys Y __TBD__ n/a
Case Analytics Dashboard Y __TBD__ Packaging option
Dashboards Y Y Packaging option
Global Picklists Y N N
Knowledge Base articles not included
Knowledge Base categories not included
Mapping Profiles Y Y Packaging option
Pages Y Y Packaging option
Reports Y Y Packaging option
Roles Y Subscriber choice N
Sites Y N N
SLAs not included
Static Resources Y Y Packaging option
Tab Preferences Y Y Packaging option
Team definitions Y N N
(global) Template Variables Y N N
Team Data Sharing Policies Y Y Packaging option
Translation Workbench Y Y __TBD__
View Preferences Y Y Packaging option
Web Services Y __TBD__
Web Tabs Y Y Packaging option
System Elements

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

System Aspect Added if New Updated Deleted if Old
Access Profiles not included
Business Hours Calendars not included
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
(But note that Scheduled Rules are included, along with other Business Rules)
not included
Single Sign-On settings not included
Twitter settings not included
Team-object Business Rules Y Y Packaging option
User-object Business Rules Y Y Packaging option
User-object Fields Y Y Packaging option
User records not included