23.4 App Builder Release Notes
Who is this article for?EHS Users.
No elevated permissions are required.
This article is the latest App Builder Release Notes (Version 23.4), find the newest enhancements and features designed to elevate your app-building experience. Explore the updates that help improve functionality, increased efficiency, and a seamless integration of innovative tools.
- Displaying App (Source) Details in the Action Item Reference Field
- Restricting the Display of Access-based Field Data in Lists and Summaries
- Making “Form JSON” Smaller for Action Item Controls
- Limiting the Number of Controls Added to an App
- Further Reading
1. Displaying App (Source) Details in the Action Item Reference Field
Currently, this feature is exclusively supported on mobile devices. The aim of this change is to enhance usability and bridge the consistency gap between the web and mobile platforms.
Note: This feature was initially released on mobile, and in this version, we have closed the gap for web users.
1.1 Action Item List Screen Changes
- Clicking the hyperlink on the reference column opens the app record details screen, enabling users to view comprehensive source information.
- The hyperlink redirects to the app builder record, with permissions evaluated (requiring at least view app permission for access).
- Users return to the action item list by clicking Back.
1.2 Action Item Detail Screen Changes
- Previously, only Source ID was displayed in the source details section.
- With this enhancement, the remaining source information is pulled from the source record and displayed in read-only mode.
- Dynamically, the system fetches the Top 5 fields configured in the summary builder as the source information.
Note: This improvement has no impact on existing forms.
- Navigating the List View screen:
- Opening Record Details in the Pop-Up:
- Displaying full source information in the Action Item Details, then Source Details:
2. Restricting the Display of Access-based Field Data in Lists and Summaries
In the current setup, access-based fields are displayed in both List and Summary views. The objective of this change is to rectify a security flaw in the system.
The enhanced system introduces a new form property to control access-based field display. By default, this property is set to No.
Note: There is no impact on existing forms as the default setting is to deactivate them.
2.1 Enhanced System
The enhanced system has the following new features:
- When an admin switches this property to Yes, any columns configured in List and Summary will be removed.
- Users will no longer have the ability to configure access-based fields in List and Summary.
- Features such as PDF export and Email me a Copy will also exclude these access-based fields.
Note: This enhancement is supported on mobile.
- Configuration in the Form Properties Screen:
- Example of an Access-Based Field:
3. Making “Form JSON” Smaller for Action Item Controls
Currently, the JSON form is quite large dependent on the number of action item controls, impacting system performance. The purpose of this improvement is to enhance overall system efficiency.
3.1 Enhanced System
The enhanced system has the following new features:
- Form JSON is refactored in such a way that there will be a considerable reduction in size for any action item app.
- This will improve the mobile performance as it has to download less data.
Note: This feature will impact existing forms.
- As part of this refactoring, all existing action item controls display columns have been updated.
- Customers can go ahead and overwrite this configuration as per their business needs.
Note: This enhancement is supported on mobile.
Important: This mandatory data correction for all apps was done as the structure to store action item controls within the form JSON was changed.
4. Limiting the Number of Controls Added to an App
Users currently have the flexibility to add an unlimited number of controls to any app, sometimes exceeding the capacity that mobile apps can effectively handle. The primary objective of this enhancement is to prevent performance and crash issues on mobile devices.
Note: This feature has no impact on existing forms.
4.1 Configuration Details
- Configurable: Yes
- Title: AppControlLimits
- Public/Private: Private
- Default: 2500
4.2 Implementing a Limit
- Users can add controls to an app within the specified limits only.
- Ensures optimal performance during app usage on mobile devices.
- If a user attempts to exceed the specified limit, the system allows the request but saves the app as a Draft.