Post-deployment tasks and UI behavior

There are tasks that must be completed after the global package has been deployed. This section describes these tasks.

Security does not have any post-deployment tasks.

Post-deployment UI behavior

Post-deployment UI behavior shares on these actions:

  • Viewing available global package updates: For objects deployed through a global package, you can view available updates directly from the object in the target tenant.
  • Accessing updates: A hyperlink labeled Available Global Package updates is displayed on supported global package objects in the target tenant. Select this link to open an overlay containing update information.
  • Updates overlay:
    • When selected, an overlay displays a grid with available updates.
    • The grid currently shows the template version of the most recently deployed object version.
    • It represents the latest version of the object as delivered by the global package.
  • Reviewing an update: Within the overlay, select the Review button to view the package content. A new tab opens displaying the selected object version in a read-only format. This view includes all information delivered as part of the global package for that object.
  • Navigating the Review tab:
    • The review tab opens to the right of the live object, allowing side-by-side comparison.
    • The live object remains unchanged and editable (if supported) while viewing the package version.
    • To exit the review, select the Close icon on the tab.
These actions help you to:
  • Understand what changes are included in the latest package version.
  • Review package-delivered content without impacting your current configuration.
  • Safely compare your live object with the latest available update before taking action.

Editable packages help you to customize security configurations (roles and other master data types) to meet their specific business needs. When a new version of the base package is released, the system does not automatically overwrite your customizations.

When a new base package version is available, it is published to the global package location. Your existing customized (editable) package remains untouched until you explicitly choose to upgrade. The upgrade process compares your current live package against the new template version and identifies differences. You retain full control over which updates to accept and which customizations to preserve.

The upgrade process does not remove user-to-role or master data types assignments that exist on your tenant. Custom roles created by your organization (not part of the base package) are never affected by the upgrades. If a base role definition has changed and you have customized that same role, you will need to decide whether to keep your version or adopt the new base definition.