...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
None
Usability
Enhancements
DAP-8754 - Restrict Ability to restrict the display of access-based fields to be configured as list columnsfield data in the list and summary
DAP-8759 - Refactoring form definition “Form JSON” to make it lighter especially when we have Action Item controlcontrols
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
Mobile
None
| Anchor | ||||
|---|---|---|---|---|
|
...
User would like to see App (Source) details in the Action Item Reference field
Existing System: Currently, we support this feature only on mobile.
...
Displaying full source information in the “Action Item Details>Source Details” section:
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Ability to restrict the display of access-based
...
Purpose: To comply with data privacy regulations.
field data in the list and summary
Existing System: Currently, we don’t have this feature.
Configurable: Yes
...
Title: EnableEncryption
...
Public/Private: Private
...
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:
Has It has a new field form property to encrypt data in an App. The default value of the ‘Encrypt’ restrict the access-based fields. By default, this property will be "No"No”.
Once the encryption property is set an admin turns on this property as Yes, then there will be an alert to the user that he can't undo this change and the property will be disabled.
En
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: NA Yes.
Configuration in the Form Properties Screen:
...
Example of an Access-Based Field:
...
| Anchor | ||||
|---|---|---|---|---|
|
...
“Form JSON” to make it lighter
...
when we have Action Item
...
controls
Existing System: Currently, there is no style difference between a enabled control and a disabled controlwe have a very heavy form JSON, depending on the number of action item controls.
Purpose: To improve usabilityperformance.
Enhanced System: In theenhanced system,
Enabled control Form JSON is refactored in such a way that there 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 improveda considerable reduction in size for any action item app.
This will improve the mobile performance as it has to download less data.
Impacts on existing forms: None. Yes
As part of this refactoring, all existing action item controls display columns have been updated as given below
Customers can go ahead and overwrite this configuration as per their business needs.
This mandatory data correction for all apps was done as the structure to store action item controls within the form JSON was changed.
...
Supported on Mobile: Yes.
| Anchor | ||||
|---|---|---|---|---|
|
...
a limit to the number of controls that can be added to an app
Configurable: Yes
Title: AppControlLimits
Public/Private: Private
Default: 2500
Existing System: Users can add an unlimited number of controls to any app and this sometimes goes beyond what mobile apps can handle.
Purpose: To improve the usability and indicate to the user that the system is trying to load something for himavoid performance and crash issues on mobile.
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 a limit is set, the user will be able to
...
...
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.
...
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.
Add controls to an app only within the specified limits.
By this, we can be sure that we won’t have any performance lag on the mobile later on during the app usage.
If user is trying to create an app beyond the specified limit, system would allow the request but save the app as 'Draft'.
Impacts on existing forms: None.
Supported on Mobile: Yes NA.