...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
DAP-1946 - Integrate "Common Configurable Action Item" screen in app builder
DAP-5205 - Ability to set up app level default alerts and reminders for action items
Enhancements
DAP-7113 - Populate 'System generated Id' as 'Source Id' in Calendar list Screen
DAP-6920 - Fix the design flaw with duplicate calendar categories for a single app
Mobile
DAP-1705 - Related Data Control Changes - Implement online search approach
DAP-7025 - iOS : Segmented Control Changes - Display complete text label without truncation
DAP-7306 - Android : Ability to concatenate another data source field in a dropdown
Technical
DAP-7454 - File Scanning while uploading attachments
PMP-87592 - .NET Core Upgrade from 3.1 to v6.0 (DAPI & MAPI)
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have a static action item screen that doesn't have configuration support.
...
Enhanced System: With this upgrade, user would be able to:
Turn on/off fields and features of action item screen.
Make fields mandatory and optional using the configuration.
Able to access latest CAPA features like - Due date extension, Verification, Asset Picklist integration etc.. .
Action item would now be access-driven - user would be able to create/ update action item only based on calendar action item permissions.
Impacts on existing forms: No
...
Mobile Details Screen | Clicking 'View action item' will navigate to List Screen |
|---|---|
  |   |
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have alerts and reminders for each action item.
...
Impacts on existing forms: No impact.
Available in Mobile: NA
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: We currently populate 'Source Id' as 0 for all action items created from app builder.
...
User would be able to see the actual record Id as source Id in action item list screen.
This would help users to identify the actual source record where the action item was created.
...
Available in Mobile: Yes.
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have only "Users By Group" data sourceduplicate calendar categories are getting created if an app is renamed.
Purpose: To be able to select the users with the help of role filteralways have a unique calendar category even if the form name is updated.
Enhanced System: Users would be able to:
...
Configure this data source to any single/multi-selection control.
...
Add a data source filter on a particular role so that they don't see the full user list.
...
Calendar category creation logic has been enhanced so that its always unique for an app.
There wouldn’t be any duplicate calendar categories even though there are modifications done to app.
All existing action items are also remapped to one single category (which is the latest in use).
There will be no data loss because of this consolidation.
Impacts on existing forms: No Yes, all action items are moved under latest category.
Available in Mobile: Yes NA.
...
...
| Anchor |
|---|
...
|
...
|
...
Existing System: User would be able to change the data type of a column using field settings. Currently, this shows up as a button and on clicking opens up a po-up.
...
5315 - Enhance Formula Builder to include aggregate functions like Minimum, Maximum, Sum and Average
Existing System: Currently, there is no support for aggregate functions in the formula builder.
Purpose: To be able to support risk score calculations that are based on Minimum and Maximum.
Enhanced System: The user would be able to:
Configure the data type of the column right in the grid without any additional click.
Users can expand/collapse the settings for usability.
Data type selection is mandatory and currently, it is defaulted to "String" for any new column.
Note: The data type selection option is only available while creating the data source, it cannot be modified for the existing data sources.
Note: If the proper data type is not selected it may not work in the formulas and when auto-populating the data into desired fieldsa formula that involves calculating a Minimum/ Maximum (Num1, Num2, … Num n).
Even other aggregate functions - sum and average will be supported to improve usability.
The outcome of these functions will be a numeric value and the values configured inside an aggregate function should also be all numeric controls.
The functions should have all controls configured as comma-separated values.
These functions are be supported in:
Default Value
Set maximum and minimum limits to numeric control
In Action Conditions
Set Actions
Both Repeater and Sections.
Impacts on existing forms: No impact impact.
Available in Mobile: NA Yes.
...
| Anchor |
|---|
...
|
...
|
...
3846 - Provide Sub-label display support in Andriod
Existing System: Currently, the system displays data from a single data source columnwe don’t have sub-label display support in andriod.
Purpose: To improve usability of a dropdown control to display additional information.
Enhanced System: Changes include:
'Addtional Display Field' property added to every single/multi-auto complete control.
User would be able to configure an additional column of the same data source.
This column would be displayed along with the primary display column with a hyphen (Ex: 'Name' - 'ID')Sub-lables added in the form were previously not getting displayed on the android app.
Now, user can see the sub-lables on app with this release.
There is no additional configuration required for this enhancement.
Impacts on existing forms: This additional property will be blank for all the existing formsNone.
Available in Mobile: Not available. Feature implemented only on web. Yes.
...
...
| Anchor |
|---|
...
|
...
|
...
DAP
...
-1705 - Related Data Control Changes - Implement online search approach
Existing System: Currently, we don't have an option to print QR code in the report header. Purpose: To improve the usability of PDF report.Currently, when user is searching for a specific record of related app, it only shows up if its already loaded on mobile device.
Purpose: To improve usability of related data search.
Enhanced System:
Users have to switch to “System Defined Header (With QR Code)” for the existing forms.
PDF's generated going forward will have the QR Code printed on the header portion.
If any app doesn't need to have this feature, we can let the PDF remain as is with the default option - "System Defined Header".
Impacts to Existing Forms: No Impact.
Available in Mobile: Yes.
...
If user is online, then he would be able to search across full list of records created for that app in that location.
Based on the search criteria of the related data control, mobile would make a database call to get the relevant records.
This way user doesn’t need to rely only on the device data but can link the record which he is looking for even though it is not present on the device.
Impacts on existing forms: None.
Available in Mobile: Yes.
| Anchor |
|---|
...
|
...
|
...
7025 - iOS : Segmented Control Changes - Display complete text label without truncation
Existing System: Currently, we have few usability gapsWe have this feature only on andriod and web.
Purpose: To improve the usability of the android app. a segmented control.
...
Enhanced System:Changes include
...
The user would be able to now see the 'Static icons' configured for the fields now in android as well. (Already available in iOS)
...
Improve the usability of the 'Tree View Control' by displaying the parent nodes even though they are inactivated so that the tree structure is visible. However, they will not be available for selection. (Already available in iOS)
Changes include:
Values with long text will no longer truncate.
The size of the control will be increased to accommodate the entire value. (
This is not yet implemented in iOS)already available in android and now will be available on iOS too.
Impacts on existing forms: NoNone.
...
Available in Mobile: Yes.
...
Static Icons support for every field
...
Segmented Control
...
Tree View Control
: Yes.
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, the system displays data from a single data source column.
Purpose: To improve usability of a dropdown control to display additional information.
Enhanced System: Changes include:
'Addtional Display Field' property added to every single/multi-auto complete control.
User would be able to configure an additional column of the same data source.
This column would be displayed along with the primary display column with a hyphen (Ex: 'Name' - 'ID').
Impacts on existing forms: This additional property will be blank for all the existing forms.
Available in Mobile: Available on Andriod.
Supervisor Selection | Ability to see additional display value (Emp Id in the below example) |
|---|---|
 |  |