23.3 App Builder Release Notes
Who is this article for?Userswho want to learn more about 23.3 app builder enhancements.
No elevated permissions are required.
In this article, the release notes for App Builder version 23.3 are explored, focusing on the latest updates and enhancements made to elevate the application development experience. See below for detailed feature updates designed to enhance capabilities within the App Builder platform.
- Introduce the Ability to Mask a Field
- Introduce the Ability to Encrypt Data
- Android - When a Field is Disabled Show the Background as Grey to Indicate it is Non-editable
- iOS - Show Loader When User Clicks on "Create a New Record"
-
Expand Sub-label Option for Segmented, Toggle, and Signature Controls
- Further Reading
1. Introduce the Ability to Mask a Field
Currently, the system doesn't have this specific feature. The introduction of this feature is intended to address and comply with data privacy regulations.
1.1 Enhanced System
- New field-level property for data masking, applicable to all controls except Label, Video, Action Item, Related Data, and Embedded Image.
- When data masking is enabled for a field, the data will be masked, and the control will display as '**********'.
- Introducing Unmask Access: A new access configuration, Unmask, allows users with this privilege to view the actual data behind the masked control(s).
-
Configuration Restrictions: Masked fields cannot be configured in the following areas:
- List & Summary Views
- Action Conditions
- Notification Conditions
- Set Actions
- Formula Builder
- Default Values
- Data Masking for Existing Apps: Data masking can be enabled for fields in existing apps, and it will be applied to all existing records within the app for the respective fields. However, it cannot be enabled if the fields are already used in areas mentioned in the above configuration restrictions.
Important: Masked fields are not supported in Cognos reports.
Note: There is no impact on existing forms and this feature is supported on mobile.
- Field Properties:
- Access Configuration:
- Details Screen in Web:
- Details Screen in Mobile:
2. Introduce the Ability to Encrypt Data
The purpose of introducing this feature is to comply with data privacy regulations. Currently, the system lacks this functionality.
2.1 Configuration Details
- Configurable: Yes
- Title: EnableEncryption
- Public/Private: Private
- Default: False
2.2 Enhanced System
The enhanced system has the following new features for users:
- Has a new field property to encrypt data in an App. The default value of the Encrypt property will be No.
- Once the encryption property is set as Yes, then there will be an alert to the user that he can't undo this change and the property will be disabled.
- Encryption support will be a maximum of 5 controls per app. A configuration option is available to increase the limit.
- Encrypt property is applicable only to controls below:
- Textbox
- Textarea
- Numeric
- Date
- Time
- System Generated Id
- Signature
- QR Code
- Toggle
2.3 Existing App Data Encryption
Important: Encrypted fields are not supported in Cognos reports.
- Data encryption can be enabled for fields in an existing App, and it is applied to newly created records.
- Once enabled encryption property cannot be disabled.
- Technical assistance can be used to encrypt data in existing records for an existing App.
Note: There is no impact on existing forms.
3. Android - When a Field is Disabled Show the Background as Grey to Indicate it is Non-editable
In the existing system, there is no style difference discernible between an enabled control and a disabled control. The purpose of this improvement is to enhance usability by implementing a clear visual distinction between enabled and disabled controls.
3.1 Enhanced System
The enhanced system has the following new features for users:
- Enabled control will be shown with a grey background indicating that it is not editable.
- Android is now consistent with iOS and Web platforms on this representation.
- There is no functional change and only the usability is improved.
Note: There is no impact on existing forms and this feature is supported on mobile.
- New Android mobile enhancement:
- Current web implementation:
4. iOS - Show Loader When User Clicks on "Create a New Record"
In the existing system, users experience a delay after clicking the Create New Record option when opening a heavy app. The purpose of addressing this is to enhance usability and provide a clear indication to the user that the system is actively loading information for them.
4.1 Enhanced System
The enhanced system has the following new features for users:
- See a loader symbol once a user clicks on the Create New Record or plus icon seen on the list screen.
- Once the loader ends, the user will be able to see the form that is ready for data input.
- There is no functional change and a loader is introduced to indicate that form is being rendered.
Note: There is no impact on existing forms and this feature is supported on mobile.
5. Expand Sub-label Option for Segmented, Toggle, and Signature Controls
In the existing system, sub-label support is currently unavailable for certain controls. The purpose of this enhancement is to improve usability and extend sub-label support to encompass all controls.
5.1 Enhanced System
The enhanced system has the following new features for users:
- See sub-labels for fields configured with segmented, toggle, and signature controls.
- This feature is now supported on both iOS and Android.
Note: There is no impact on existing forms and this feature is supported on mobile.
- New mobile enhancement:
- Current web implementation:
6. Further Reading
- 23.3 Insight Release Notes
- 23.3 Performance Management Release Notes
- 23.3 Risk Assessment Release Notes
- 23.3 Occupational Health Release Notes
- 23.3 Mobile Pro Release Notes
- 23.3 Industrial Hygiene Release Notes
- 23.3 Foundation & Framework Release Notes
- 23.3 Audit Management Release Notes
- 23.3 Activity Management Release Notes
- 23.3 LMS Release Notes
- 23.3 IMS Release Notes