New and Improved Features
New Features
None
Usability
DAP-8766 - The user would like to see App (Source) details in the Action Item Reference field
Enhancements
DAP-8754 - Restrict access-based fields to be configured as list columns
DAP-8759 - Refactoring form definition to make it lighter especially Action Item control
DAP-8767 - Ability to set limits in app builder features to avoid performance issues
Mobile
MP-10008 - Ability to replace a sub-label with a validation message to improve usability
Technical
DAP-8761 - Execution - Mongo DB Driver Upgrade to 2.22
DAP-8766 - User would like to see App (Source) details in the Action Item Reference field
Existing System: Currently, we support this feature only on mobile.
Purpose: To improve usability and close the consistency gap between web and mobile.
Enhanced System:
Action Item List Screen Changes:
On clicking the hyperlink on the reference column, app record details screen opens up so that user can view the complete source information.
As this hyperlink is redirecting to app builder record, permissions would be evaluated and only if user has at least view app permission, then he would be able to see.
User would land back to the action item list on clicking 'Back'.
Action Item Detail Screen Changes:
Currently, we only show 'Source Id' in the source details section.
With this enhancement, rest of the source information would be pulled from source record and will be shown in read-only mode.
As the source fields are not fixed, system dynamically pulls “Top 5” fields configured in summary builder as the source information.
Impacts on existing forms: No
Supported on Mobile: Yes, this feature was originally released in mobile. In this version, we closed the web gap.
List Screen Navigation:
Opening Record Details in the Pop-Up:
Displaying full source information in the “Action Item Details>Source Details” section:
DAP-8754 - Ability to restrict the display of access-based field data in the list and summary
Existing System: Currently, we display the data in List as well as Summary even for the access-based fields.
Purpose: To fix the security flaw in the system.
Enhanced System:
It has a new form property to restrict the access-based fields. By default, this property will be "No”.
Once an admin turns on this property as Yes, any columns configured in List and Summary will be removed.
Going forward, the user wouldn’t be able to configure any access-based field in List and Summary.
PDF export and Email me a Copy features also will not expose these access-based fields.
Impacts on existing forms: No impact as we are turning them off by default.
Supported on Mobile: Yes.
Configuration in the Form Properties Screen:
Example of an Access-Based Field:
DAP-8759 - Refactoring “Form JSON” to make it lighter when we have Action Item controls
Existing System: Currently, we have a very heavy form JSON, depending on the number of action item controls.
Purpose: To improve performance.
Enhanced System: In the enhanced system,
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.
Impacts on existing forms: None.
Supported on Mobile: Yes.
DAP-8767 - Ability to set limits in app builder features to avoid performance issues
Existing System: When the user is trying to open a heavy app, there is some delay after clicking the ‘Create New Record’ option.
Purpose: To improve the usability and indicate to the user that the system is trying to load something for him.
Enhanced System: The user would be able to
See a loader symbol once he 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.
Impacts on existing forms: None.
Supported on Mobile: Yes.
MP-10008 - Ability to replace a sub-label with a validation message to improve usability
Existing System: Currently, we don't have sub-label support for a few controls.
Purpose: To improve usability and extend sub-label support for all the controls.
Enhanced System: User would be able to
See sub-labels for fields configured with Segmented, toggle, and signature controls.
This feature is now supported on both iOS and Andriod.
Impacts on existing forms: None.
Supported on Mobile: Yes.