Applications
In the Partial Locking Framework, an Application is the top-level container that groups the interface and configuration components delivered to a tenant. Applications can originate from a Source Tenant or be created locally in the Destination Tenant. An application's lock state controls which metadata Tenant Admins can modify and how those values are handled during a later application upgrade.
Locking Behavior
When application XML is generated, a Tenant Admin or Super Admin can select one of three lock states for a source application:
-
Unlocked – Tenant Admins can modify all application properties.
-
Partially Locked – Tenant Admins can modify only the application properties explicitly permitted by the framework.
-
Locked – Tenant Admins cannot modify application metadata.
An application created directly in the Destination Tenant is treated as an Unlocked (Custom) application.
The selected lock state applies to the application itself. Attaching or detaching child components does not modify the application's upgrade path.
Tenant Admin Permissions
Tenant Admin permissions vary according to the application's origin and lock state. The following table identifies the actions and properties available for each state.
Application-Specific Actions and Properties
|
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant |
||
|---|---|---|---|---|
|
Action/Property |
Unlocked (Custom) Tab | Unlocked Tab | Partially Locked Tab | Locked Tab |
|
This application is deployed |
|
|
|
|
|
This application is hidden (does not appear in the Sidebar selector) |
|
|
|
|
|
Show first level of menus below tabs (Original UI only; not available in Classic UI) |
|
|
|
|
|
Edit |
|
|
|
|
|
Application Name |
|
|
|
|
|
Integration Name |
|
|
|
|
|
Custom Logo – File |
|
|
|
|
|
Custom Logo – Hide Logo |
|
|
|
|
|
Enable Help |
|
|
|
|
|
External Application Help Link |
|
|
|
|
|
UI Blueprint for Desktop |
|
|
|
|
|
UI Blueprint for Mobile |
|
|
|
|
|
Application Theme |
|
|
|
|
|
Field Labels Render Mode for Desktop |
|
|
|
|
|
Field Labels Render Mode for Tablet |
|
|
|
|
|
Field Labels Render Mode for Smartphone |
|
|
|
|
|
Use Horizontal Responsive Design |
|
|
|
|
|
Use Native Calendar and Time Control on mobile devices |
|
|
|
|
|
Right-to-Left Text Direction |
|
|
|
|
|
Notifications Position |
|
|
|
|
|
Enable GridControl Selective Edit |
|
|
|
|
|
Bootstrap Version |
|
|
|
|
|
Hosts Whitelist for Client REST API |
|
|
|
|
|
Delete |
|
|
|
|
Super Admins have full administrative control over all application types, regardless of lock state. This includes the ability to edit restricted properties and delete Partially Locked or Locked applications.
Upgrade Compatibility
When a new application version is pushed from the Source Tenant, upgrade behavior is determined by the application's origin, lock state, and modification status. The same rules apply whether a Tenant Admin or Super Admin made the destination change.
Unlocked (Custom) Applications
Applications created in the Destination Tenant are ignored by the application upgrade. Their metadata is not replaced by source content.
Partially Locked Applications
For a Partially Locked application:
-
Properties that Tenant Admins cannot edit are updated from the Source Tenant during an upgrade.
-
The source updates the property when the Destination Tenant has not modified it.
-
A destination edit to an allowed property is preserved during upgrades while the application remains marked Modified.
-
After Restore Upgrade Compatibility is performed, source values replace the destination values during the next application upgrade.
Locked Applications
Application metadata for a Locked application is copied from the Source Tenant during an upgrade. Tenant Admins cannot change the application metadata.
Adding and Removing Applications
Applications can be created through an application installation or an out-of-the-box LCAP Marketplace installation.
To remove an application from a Destination Tenant, a Tenant Admin or Super Admin must first undeploy it and then delete it manually. Deleting the application also deletes associated components that are not linked to another application in the tenant and may result in data loss.
Tenant Admins can delete only Unlocked (Custom) and Unlocked applications. A Super Admin can also delete Partially Locked and Locked applications.
If any type of application is deleted either by a Super Admin or by a Tenant Admin, the only way to retrieve it is to install the application again.
Restoring the Upgrade Path
Use Restore Upgrade Compatibility to discard application-level customizations and return a Partially Locked application to its source-managed upgrade path. The action is available under More actions on the application metadata view and is displayed only for Partially Locked applications that have been modified.
To restore upgrade compatibility:
-
Open the application metadata view.
-
From More actions, select Restore Upgrade Compatibility.
-
Review the warning that the action is irreversible and that application-level destination configurations will be removed during the next application upgrade.
-
Confirm the action.
After confirmation, the application's Modified flag is cleared. During the next application upgrade, the application metadata is restored to the out-of-the-box source version and destination customizations to that metadata are overwritten.
Restoring an application's upgrade path does not affect its child components, including:
-
Tabs
-
Objects
-
Portals
-
Roles
-
Custom Methods
-
Authentication Profiles
-
Hosted Files
-
Batch Jobs
-
Seed Record Packages