...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
None
Usability
...
DAP-4300 - Introduce the ability to ‘Mask’ a field
Mobile
DAP-8519 - iOS - Show loader when user clicks on create a new record
DAP-8563 - Expand Sub-label option for Segmented, Toggle, and Signature controls
Technical
DAP-7711 - .NET Core Upgrade from 3.1 to v6.0 (API)
DAP-7753 - App. Security-Checkmarx
Usability
None
Enhancements
None
Enhancements
DAP-8754 - Ability to restrict the display of access-based field data in the list and summary
DAP-8759 - Refactoring “Form JSON” to make it lighter when we have Action Item controls
DAP-8767 - Ability to set a limit to the number of controls that can be added to an app
Mobile
None
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we don’t have support this feature only on mobile.
Purpose: To comply with data privacy regulationsimprove usability and close the consistency gap between web and mobile.
Enhanced System:
...
Has a new field-level property to mask data and it can be applied to all the controls except for Label, Video, Action item, Related Data, and Embedded Image.
...
Once masking is turned on for a particular field, then data will be masked and control will be displayed as '**********'.
...
Unmask Access: A new access configuration, 'Unmask,' has been added. Users with 'Unmask' access privilege can 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 and Default Values
...
Existing App Data Masking: Data masking can also be enabled for fields in an existing App, once enabled data masking will be applied to all existing records within the app for the respective fields. Data masking cannot be enabled for fields in an existing App if the fields are already used in any of the areas mentioned in the above configuration restrictions.
...
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.
Field Properties:
Access Configuration:
Details Screen: 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:
...
| Anchor |
|---|
...
|
...
|
...
DAP-
...
8754 -
...
Ability to restrict the display of access-based 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 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
Existing App Data Encryption:
o Data encryption can be enabled for fields in an existing App, and it is applied to newly created records.
o Once enabled encryption property cannot be disabled.
o Technical assistance can be used to encrypt data in existing records for an existing App.
Encrypted fields are not supported in Cognos reportsan 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: NA. Yes.
Configuration in the Form Properties Screen:
...
Example of an Access-Based Field:
...
| Anchor |
|---|
...
|
...
|
...
8759 - Refactoring “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 |
|---|
...
|
...
|
...
8767 - Ability to set 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.