AgileApps Support Wiki

Difference between revisions of "Overwrite Previous Package"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
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.
{{:Option:Overwrite Previous Package}}


;Considerations:
==About the "Overwrite" Option==
*When the Overwrite Previous Package option is enabled, these options become available as part of package configuration:
In general, the ''Overwrite Previous Package'' option means that:
:;Merge:During installation by a subscriber:
:* Previously installed items are deleted, if the container they are in is included in the package. (Otherwise, they are not deleted.)
::* New Package items are added to the subscribers' database.
:* Previously installed Email templates and Quick Text items are updated, if the object is included in the package. (Otherwise, they are not updated.)
::* Package items that were modified by the subscriber ''are not affected''.
 
::* Items in the previous package that were deleted by the packager are not removed.
For example, suppose that a package contains an object that defines two Web Forms, and that a subscriber installed that package. Further suppose that the publisher deletes those web forms, and creates a new package containing that object. When the subscriber installs the new package, the Web Forms are deleted from the subscriber's system is the package was created with the Overwrite option. Otherwise, they remain.
::* If the subscriber has created a new platform element with the same name as an item included in the package...{{TBD|}}


:;Overwrite:During installation by a subscriber:
==Working with the "Overwrite" Option==
::* New Package items are added to the subscribers' database
{{:Option:Overwrite Previous Package}}
::* Package items that were modified by the subscriber are ''replaced''
When enabled by the service provider, a package publisher has two additional options when creating a package:
::* Items in the previous package that were deleted by the packager are ''removed''.
:;Merge: Previously-installed items created when an earlier version was installed are ''not'' deleted.
::* 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.
:: They remain on the subscriber's system, even if they were deleted by the publisher.
:;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:


Those principles apply to these package items:
::* Applications (if previously added as a result of a [[Package Dependency]]
:* Classes
::* Classes         
:* Dashboards
::* Global Picklists
:* Pages
::* Global Template Variables
:* Reports
::* Roles           
:* Static Resources
::* Teams           
:* Tab Preferences
::* Web Services
:* 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?)}}
:''Learn more:'' [[Package Items#How Package Items are Applied]]<noinclude>
:{|
|'''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>

Latest revision as of 23:02, 5 August 2015

About the "Overwrite" Option

In general, the Overwrite Previous Package option means that:

  • Previously installed items are deleted, if the container they are in is included in the package. (Otherwise, they are not deleted.)
  • Previously installed Email templates and Quick Text items are updated, if the object is included in the package. (Otherwise, they are not updated.)

For example, suppose that a package contains an object that defines two Web Forms, and that a subscriber installed that package. Further suppose that the publisher deletes those web forms, and creates a new package containing that object. When the subscriber installs the new package, the Web Forms are deleted from the subscriber's system is the package was created with the Overwrite option. Otherwise, they remain.

Working with the "Overwrite" Option

Lock-tiny.gif

When enabled by the service provider, a package publisher has two additional options when creating a package:

Merge
Previously-installed items created when an earlier version was installed are not deleted.
They remain on the subscriber's system, even if they were deleted by the publisher.
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:
  • Applications (if previously added as a result of a Package Dependency
  • Classes
  • Global Picklists
  • Global Template Variables
  • Roles
  • Teams
  • Web Services
Learn more: Package Items#How Package Items are Applied
Retrieved from "https://agileappscloud.info/aawiki-src/index.php?title=Overwrite_Previous_Package&oldid=9093"