Partial Locking Framework - Page Section
A Page Section is a container that groups fields, lists, charts, grid controls, or other UI components. Like pages and tabs, sections are subject to lock states that dictate their behaviour during upgrades and customization.
Locking Behavior
The lock state of a section is derived from the lock state of the parent page. Section-level locking affects both structure and configuration.
-
Sections created in the destination tenant are Unlocked (Custom).
-
Sections from the source application may be Unlocked, Partially Locked, or Locked.
Tenant Admin Permissions
The following table outlines the actions that a Tenant Admin can perform on a section based on its lock status.
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant |
||
---|---|---|---|---|
Action/Property |
Unlocked (Custom) Section | Unlocked Section | Partially Section | Locked Section |
Section Title |
![]() |
![]() |
![]() |
![]() |
Integration Name |
![]() |
![]() |
![]() |
![]() |
Tab |
![]() |
![]() |
![]() |
![]() |
Columns |
![]() |
![]() |
![]() |
![]() |
Style |
![]() |
![]() |
![]() |
![]() |
Collapse Style |
![]() |
![]() |
![]() |
![]() |
Default New Field Section |
Partially Allowed
|
![]() |
Field should not be automatically added to PL pages. |
![]() |
Show In |
![]() |
![]() |
![]() |
![]() |
Section-Level Help |
![]() |
![]() |
![]() |
![]() |
HTML Event Handlers |
![]() |
![]() |
![]() |
![]() |
Add Component |
![]() |
![]() |
![]() |
![]() |
Hide Component |
![]() |
![]() |
![]() |
![]() |
Remove Component |
![]() |
![]() |
![]() |
![]() |
Edit Component |
![]() |
![]() |
![]() |
![]() |
Super Admins have full administrative control over all page sections, 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 Section, the system automatically sets a Modified
flag. This flag indicates that the page section 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 section that undergoes any modification.
Restoring Upgrade Path
To revert a Partially Locked section to its original state, use the Restore Upgrade Compatibility action. This is available only for page sections marked as Modified components.
To restore the modified page section 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 Sections.
-
Select Restore Upgrade Compatibility for the modified page section that needs restoration.
-
A confirmation dialogue indicating that this action is irreversible. Confirm and proceed to restore the modified section 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 section is restored to its source version.
Section Reordering on Application Upgrade
During application upgrades, the order of Page Sections 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 sections are added, reordered, or removed during upgrades:
Scenario | Behavior in Destination Tenant after Upgrade | Custom Tabs Impact |
---|---|---|
A new section has been added to the Source |
Inserted immediately after the section above it in the source layout. If it’s the first section, it becomes the first OOTB section. |
Not affected. Custom sections retain their positions. |
An existing section is reordered in the Source |
Repositioned relative to the section directly above it in the source layout. |
Custom sections remain in place. |
A section is deleted in the Source |
The section is removed in the destination. Any custom content inside is moved to the bottom of the last remaining section or tab. |
Content is preserved but relocated. |
A section is moved across tabs in Source |
The section appears under the new tab as defined in the source. The destination tab structure is updated accordingly. |
Custom sections are not moved unless explicitly reparented. |
No custom sections exist |
The destination section order will match the source exactly. |
Not applicable. |
Custom section(s) exist |
Source-defined sections are updated; custom sections remain in their existing positions. |
Preserved as-is, does not affect due to source reordering. |
Manually reassign the section to a new tab |
Not supported. Section-to-tab reparenting must come from Source Tenant. |
- |