Difference between revisions of "Package Items"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 29: | Line 29: | ||
|- | |- | ||
|valign="top"| | |valign="top"| | ||
*[[ | *[[Classes]] (includes<br>user-created classes) | ||
| | | | ||
|- | |- | ||
|valign="top"| | |valign="top"| | ||
*[[ | *[[Mapping Profile]]s | ||
| | | | ||
| Line 44: | Line 44: | ||
|- | |- | ||
|valign="top"| | |valign="top"| | ||
*[[ | *[[Processes]] | ||
| | |||
*The [[Business Hours Calendar]] used in processes.<br>(Such calendars are never updated. So the package installer is free to modify the calendar to suit their purposes.) | |||
|- | |||
|valign="top"| | |||
*[[Process Models]] | |||
| | | | ||
*[[Teams] and [[Roles]] used in Process Models | |||
|- | |- | ||
|valign="top"| | |valign="top"| | ||
* | *[[Reports]] | ||
| | | | ||
| Line 55: | Line 62: | ||
|valign="top"| | |valign="top"| | ||
*[[Roles]] | *[[Roles]] | ||
| | |||
|- | |||
|valign="top"| | |||
*Sites | |||
| | |||
*Includes [[Pages]] | |||
|- | |||
|valign="top"| | |||
*[[Static Resources]] | |||
| | | | ||
| Line 68: | Line 86: | ||
*Includes Teams and Roles involved | *Includes Teams and Roles involved | ||
*Includes Child Teams if the ''Include Child Teams'' option is selected for that team | *Includes Child Teams if the ''Include Child Teams'' option is selected for that team | ||
|- | |- | ||
| Line 82: | Line 95: | ||
|- | |- | ||
|valign="top"| | |valign="top"| | ||
* | *Web Tabs (includes<br>[[Pages]], or [[Widgets]], if available) | ||
| | | | ||
|} | |} | ||
Revision as of 01:20, 30 July 2013
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.)
Standard Dependencies
Platform Element Dependent Elements - Application
- Includes Custom Objects
- Includes Web Tabs
- Includes Application Information settings
- Includes role-based Workspace Display Order for objects
- Includes role-based Default View Preferences for objects
- Object Data and other
Data (Package Data)
- Classes (includes
user-created classes)
- The Business Hours Calendar used in processes.
(Such calendars are never updated. So the package installer is free to modify the calendar to suit their purposes.)
- [[Teams] and Roles used in Process Models
- Sites
- Includes Pages
- Includes Teams and Roles involved
- Includes Child Teams if the Include Child Teams option is selected for that team
- Includes localized labels and items
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
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
