Partial Locking Framework - Page Tabs

Each Page tab has a lock state and inherits upgrade behaviours and permission constraints from the Page. Tabs can either originate from the Source Tenant or be created locally on the Destination Tenant, and are subject to locking, ordering, and metadata rules defined by the Partial Locking framework.

Locking Behavior

The lock status of a Page Tab is derived from its source Page or, in the case of generic pages, from the associated application/tab that most recently updated the page.

In scenarios where a tab is associated with multiple installed applications, the latest update takes precedence and determines the effective lock state.

Tenant Admin Permissions

Tenant Admin permissions on Page Tabs are scoped based on the tab’s lock state. The table below lists the supported actions.

 

Built on Destination Tenant

Built on Source Tenant & Pushed to Destination Tenant

Action/Property

Unlocked (Custom) Tab Unlocked Tab Partially Locked Tab Locked Tab

Tab Name

Integration Name

Show In

Tab-Level Help

 

Note:
  • Super Admins have full administrative control over all page tabs, regardless of their lock status. This includes the ability to preview, clone, synchronise, rename, delete, and modify.

  • If a Super Admin modifies any properties, the component will remain on the upgrade path. The source will override these changes during the next upgrade.

Upgrade Compatibility

When a permitted change is made to a Partially Locked Page Tab, the system automatically sets a Modified flag. This flag indicates that the page tab has diverged from its source version and influences upgrade behaviour. This information is displayed in the pages table under the object definition page. Likewise, a red exclamation triangle icon is rendered within the tab that undergoes any modification.

Restoring Upgrade Path

To revert a Partially Locked tab to its original state, use the Restore Upgrade Compatibility action. This is available only for page tabs marked as Modified components.

To restore the modified page tab to its original state, do the following:

  • Navigate to the page view from the object definition page.

  • Under the Page view, go to the Page Tabs.

  • Select Restore Upgrade Compatibility for the modified page tab that needs restoration.

  • A confirmation dialogue indicating that this action is irreversible. Confirm and proceed to restore the modified tab to its original state, and the Modified flag is cleared.

  • During the next application upgrade, all customizations for the page are overwritten, and the page tab is restored to its source version.

Note: When restoring upgrade compatibility for a page section, it is important to note that only the section container is included in the application upgrade path. This process does not impact the sections and cells.

Tab Reordering on Application Upgrades

During application upgrades, the order of Page Tabs in the Destination Tenant is updated based on the layout defined in the Source Tenant. However, any Custom Tabs added by the destination tenant are preserved and never removed. The following rules explain how tabs are added, reordered, or removed during upgrades:

Scenario Behavior in Destination Tenant after Upgrade Custom Tabs Impact

A new tab is added in the Source Tenant

The new tab is inserted immediately after the tab that precedes it in the Source tab order.

Not affected. Custom tabs retain their positions.

A New tab is the first tab in Source

The new tab becomes the first OOTB tab in the destination page.

Not affected. Custom tabs follow OOTB tabs.

An Existing tab is reordered in Source

The tab is moved in the destination to match its new position relative to other OOTB tabs in the Source.

Custom tabs remain in their current positions.

A Tab is deleted in the Source

The tab is removed from the destination. Any custom sections inside the deleted tab are moved to the last tab on the page.

Custom tabs are not deleted.

Destination has custom tab(s)

Custom tabs are preserved as-is and are not reordered or removed during upgrade.

Fully preserved.

No custom tabs in destination

All tabs (OOTB only) follow the exact order defined in the source.

Not applicable.

Custom section inside deleted tab

The section is not deleted; instead, it is moved to the bottom of the last remaining tab on the page.

Section content preserved.