Difference between revisions of "Overwrite Previous Package"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 2: Line 2:
{{:Option:Overwrite Previous Package}}
{{:Option:Overwrite Previous Package}}


;Considerations:
:* When the Overwrite Previous Package option is enabled, these options become available as part of package configuration:
*When the Overwrite Previous Package option is enabled, these options become available as part of package configuration:
::;Merge: Items in the previous package that were deleted by the packager remain on the subscriber's system.
:;Merge:During installation by a subscriber:
::;Overwrite: Items in the previous package that were deleted by the packager are removed from the subscriber's system, with the exception of these items, which remain on the subscriber's system unless and until they are manually deleted:
::* New Package items are added to the subscribers' database.
::* Global Picklists
::* Package items that were modified by the subscriber ''are not affected''.
::* Classes         
::* Items in the previous package that were deleted by the packager are not removed.
::* Email Templates 
::* If the subscriber has created a new platform element with the same name as an item included in the package...{{TBD|}}
::* Roles           
 
::* Sites           
:;Overwrite:During installation by a subscriber:
::* Teams           
::* New Package items are added to the subscribers' database
::* Web Forms
::* Package items that were modified by the subscriber are ''replaced''
::* Web Services  {{TBD|Confirm}}<noinclude>
::* Items in the previous package that were deleted by the packager are ''removed''.
::* If the subscriber has created a new platform element with the same name as an item included in the package, the subscriber's version is replaced by the packaged item.
 
Those principles apply to these package items:
:* Classes
:* Dashboards
:* Pages
:* Reports
:* Static Resources
:* Tab Preferences
:* View Preferences
:* Web Tabs
:* Object aspects:
::* Business Rules
::* Document Templates
::* Forms, Layout Rules, Form Scripts, and Custom Form Actions
::* Fields and Field Scripts
::* Indexes
::* Macros
::* Validations
 
{{TBD|What about these? (Are these statements accurate?)}}
:{|
|'''Item'''        ||'''Added''' ||'''Replaced''' ||'''Deleted'''
|-
| Global Picklists ||  Y  ||    N    ||    N
|-
| Classes          ||  Y  ||    ?    ||    N
|-
| Email Templates  ||  Y  ||    N    ||    N
|-
| Roles            ||  Y  ||    N    ||    N
|-
| Sites            ||  Y  ||    N    ||    N
|-
| Teams            ||  Y  ||    N    ||    N
|-
| Web Forms        ||  Y  ||    N    ||    N
|-
| Web Services    ||  Y  ||    N    ||    N
|}<noinclude>


[[Category:Tenant Capabilities]]
[[Category:Tenant Capabilities]]
</noinclude>
</noinclude>

Revision as of 02:38, 4 March 2015

The Overwrite Previous Package option gives Publishers the choice to Merge or Overwrite packages. The Merge/Overwrite choice is applied when a Subscriber installs a package.

Lock-tiny.gif

  • When the Overwrite Previous Package option is enabled, these options become available as part of package configuration:
Merge
Items in the previous package that were deleted by the packager remain on the subscriber's system.
Overwrite
Items in the previous package that were deleted by the packager are removed from the subscriber's system, with the exception of these items, which remain on the subscriber's system unless and until they are manually deleted:
  • Global Picklists
  • Classes
  • Email Templates
  • Roles
  • Sites
  • Teams
  • Web Forms
  • Web Services __TBD: Confirm__