Partial Locking Framework - Pages

In the Partial Locking Framework, a Page functions as the fundamental visual container within the application user interface. It establishes the basis for all interface components, encompassing tabs, sections, and cells. Pages can either originate from the Source Tenant or be created locally within the Destination Tenant (custom pages). The functional behaviour, edit permissions, and upgrade impact of a page are governed by its lock state, which determines the level of control granted to Tenant or Super Administrators.

Locking Behavior

The locking state of a page during an application install or upgrade is automatically determined based on the lock status of its parent entity (object or tab). Pages may be in one of four states:

  • Unlocked (Custom) – Created in the destination tenant.

  • Unlocked – Originates from the source tenant but has no lock restrictions.

  • Partially Locked – Editable only in specific, controlled areas.

  • Locked – Fully protected from modification.

Object Pages

  • If the parent object is unlocked, its associated pages are also unlocked upon installation or upgrade.

  • If the parent object is locked, the pages remain locked.

  • In case of a partially locked parent object, the tenant can select the desired lock state (Unlocked, Partially Locked, or Locked) from the Partial Lock Preferences page.

Note: If a tenant activates the support login feature, a Super Admin is granted the ability to log in as a Tenant Admin, thereby obtaining full permissions. This functionality enables the Super Admin to access and modify components that are either Partially Locked or Fully Locked.

Generic Pages

The page’s lock state reflects the lock status of its parent tab. If a generic page is linked to multiple installed tabs, its lock state is determined by the most recently updated tab or application.

Tenant Admin Permissions

Tenant Admins have varied permissions depending on the lock state of the page. The following table outlines which actions are permitted in each case:

Page-Specific Actions & Properties

 

Built on Destination Tenant

Built on Source Tenant & Pushed to Destination Tenant

Action/Property

 Unlocked (Custom) Page Unlocked Page Partially Locked Page Locked Page

Preview

Clone

Sync

Delete

Page Name

Target Edit Page

Columns

Enable Tabs

Do not use AJAX loading for Tabs

Hide "More Actions..." drop-down list

Hide "PDF Export" link for this page

HTML Event Handlers

Navigation Order

Height / Width in Pixels (Popup pages only)

Create Sections

Reorder Sections

Delete Sections

Create Page Tabs

Reorder Page Tabs

Delete Page Tabs
Note:

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

  • 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, the system automatically sets a Modified flag. This flag indicates that the page has diverged from its source version and influences upgrade behaviour. During the next application upgrade, source changes will not reflect on a modified, partially locked page unless Restore Upgrade Compatibility is exercised. This protects existing destination customizations on the page.

This information is displayed in the pages table under the object definition page.

A red exclamation triangle icon appears beside the components that undergo modifications.

Restoring Upgrade Path

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

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

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

  • From More actions, select Restore Upgrade Compatibility.

  • A confirmation dialogue indicating that this action is irreversible. Confirm and proceed to restore the modified page 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 is restored to its source version.

Note: The Restore Upgrade Compatibility action may impact the entire page hierarchy, including: Page container, Tabs, Sections and Cells.