...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
Mobile
DAP-8519 - iOS - Show loader when user clicks on create a new record
DAP-8563 - Provide Expand Sub-label support option for remaining Segmented, Toggle, and signature Signature controls
Technical
DAP-7711 - .NET Core Upgrade from 3.1 to v6.0 (API)
DAP-7753 - App. Security-Checkmarx
Usability
None
Enhancements
None
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we can’t mask field datadon’t have this feature.
Purpose: To comply with the regulatory requirementsdata privacy regulations.
Enhanced System: With this feature, user would be able to:
Share an app with a group of users.
Will be able to configure control-level access on a particular field/section to a group.
Will be able to send a notification to a group.
When a group is selected in all the above scenarios, location scope is always considered.
Ex: User part of a selected group, can access the app only in the location for which he has scope.
Impacts on existing forms: No
Supported on Mobile: Yes.
...
Existing System: Currently, we don’t have a feature to upload images to the notification template.
Purpose: To improve the usability of the notification template.
Enhanced System: The user would be able to
...
Upload a static image to the notification template.
...
Users can use this feature to make the template look more visual than printing plain text.
...
Supported Image types are: Jpeg, Jpg, Jpe, Jfif, Png, Gif, Bmp
...
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.
Masked fields are not supported in Cognos reports.
Impacts on existing forms: No impact.
Supported on Mobile: NA Yes.
...
Existing System: Currently, we have form settings tab on the 'Form Builder' page next to field properties.
Purpose: To improve usability.
...
The form properties are moved to 'App Settings' page.
Form properties is the first tab where user can actually see all the controls.
There is no functional change and this story only intends to move the controls for better usability.
Impacts on existing forms: None.
Supported on Mobile: NA. Field Properties:
...
Access Configuration:
...
Details Screen:
Web Screen | Mobile Screen |
|---|---|
 | .png?version=1&modificationDate=1695041699829&cacheVersion=1&api=v2) |
| Anchor |
|---|
...
|
...
|
...
4332 -
...
Introduce the ability to 'Encrypt' data
Purpose: To comply with data privacy regulations.
Existing System: Currently, we don’t have the option to remove an iconthis feature.
Purpose: To improve usability. Configurable: Yes
Title: EnableEncryption
Public/Private: Private
Default: False
Enhanced System: User would be able to
...
Has a new field property to encrypt data in an App. The default value of the ‘Encrypt’ property will be "No".
Once the app is re-saved, the icon wouldn’t be visible on iOS/Andriod devices.
Device auto-adjusts the extra space and renders the form using the wide space now available.
Impacts on existing forms: None.
Supported on Mobile: Yes.
...
Configurable: Yes
Title: SuperAdmins
Public/Private: Private
Default: 1000 (ProcessMap Admin)
Existing System: Currently, we don't have a configuration to set a user as super admin.
Purpose: To be able to configure super admin for apps, who can access all apps.
Enhanced System: Super admin would be able to
Access all apps irrespective of whether an app is shared with him.
He would be able to Modify/ Delete an app that is not shared with him.
Super admin will also be able to access module-integrated apps as well on the home page and will be able to Modify/Delete.
Module-integrated apps will be displayed under a reserved category - “System Apps“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 reports.
Impacts on existing forms: NoneNo impact.
Supported on Mobile: NA.
...
| Anchor |
|---|
...
|
...
|
...
8518 - Android - When a field is disabled then show the background as grey to indicate that it is non-editable
Existing System: Currently, we cannot set minimum and maximum limits to time control.there is no style difference between a enabled control and a disabled control.
Purpose: To enhance time control. improve usability.
...
Enhanced System:The user would be able to:
...
Configure minimum and maximum limits which would be validated while entering data.
...
The limits could be a formula as well.
In theenhanced 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: No Yes.
Android (New Enhancement) | Web (Implementation Already Exists) |
|---|---|
.png?version=1&modificationDate=1695042316447&cacheVersion=1&api=v2) |  |
| Anchor |
|---|
...
|
...
|
...
8519 - iOS - Show loader when user clicks on create a new record
Existing System: Recently, in v22.3 we have refactored the way data sources are downloaded on mobile. Click Here to go over the (Phase-1) release notes. When the user is trying to open a heavy app, there is some delay after clicking the ‘Create New Record’ option.
Purpose: To handle all the remaining scenarios where the user can directly land on the details screenimprove the usability and indicate to the user that the system is trying to load something for him.
Enhanced System: The improved system would handle the below-mentioned scenarios:
...
Navigation from email notification live link.
...
Navigate to the details screen by scanning QR Code.
...
Navigation from a parent form to a child form by using related data control.
...
Navigation from (Action Item Summary → Source Card) to source record details.
...
In all the above-mentioned scenarios, data sources download would be triggered only when user clicks on a particular app to eliminate the blank dropdown issue before landing on to the details screen.
...
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.
...
| Anchor |
|---|
...
|
...
|
...
Expand Sub-label option for Segmented, Toggle, and Signature controls
Existing System: Currently, there is no configuration to turn off data transfer from an outbound API.
Purpose: To be able to have better control on data export.
Enhanced System:
...
The system would provide a configuration to turn off outbound API data transfer by app.
...
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. Default would be 'Yes'.
Supported on Mobile: NA Yes.
Mobile (New Enhancement) | Web (Implementation Already Exists) |
|---|---|
 |  |