Liquid UI - Documentation - 2.3.30 Feature Locking based on license type in Android

2.3.30 Feature Locking based on license type in Android


Purpose

Organizations using Liquid UI for Android can regulate access to app functionalities through license-based feature locking. Feature access (including barcode scanning, printing, OCR) is restricted based on user license type, ensuring authorized personnel only and operational compliance.

License tiers, like User Lite or User Industrial, determine feature availability. Upon license updates through methods such as activation links, QR codes, or LAMP sync, access permissions are automatically modified.

Feature lock is:

  • Applied client-side for a seamless user experience
  • Enforced during both device activation and license sync
  • Managed by admins via the LAMP portal

Prerequisites

  • The device must be assigned a valid Lite or Industrial license via the LAMP portal.
  • Ensure the Liquid UI for Android app is updated to version __ or higher.
  • The device must sync with the latest license data from LAMP
 

How to observe feature locking

  1. Apply a User Industrial license in LAMP.
  2. Open Liquid UI and go to Menu > About to confirm the license type.
     
     
  3. Use a controlled feature (e.g., barcode scan) - it should work normally.
  4. Change the license to User Lite via LAMP, then sync the device.
     
 

Re-attempt the same feature. Based on the lock configuration, you will see either:

  1. Inform: The user is notified that the feature is not included in their current license.
     
 
  1. Warning: A dialog alerts the user that the feature may not be allowed under their current license. The scanned value will be populated in the input field, but you cannot proceed further.
     
     
  2. Prohibited: The feature is fully blocked. A notification informs the user that access is not permitted, and the feature cannot be used.

These responses are designed to make the license restrictions transparent without disrupting the overall SAP workflow.

 

Note: No app restart is required to enforce the new restrictions.

 

Can't find the answers you're looking for?