...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
DAP-1946 - Integrate "Configurable Action Item" screen in app builder6890 - Ability to define any form control as unique for data validation
DAP-5205 7965 - Ability to set up app level default alerts and reminders for action itemsA framework to integrate an API so that complex business rules can be configured
Enhancements
DAP-5813 - 7113 - Populate 'System generated Id' as 'Source Id' in Calendar list ScreenEnhance Set Actions - Ability to set an empty value to control
DAP-6920 6402 - Fix the design flaw with duplicate calendar categories for a single appConfiguration to set the number of decimal values to be displayed for a numeric control
DAP-5315 7611 - Enhance Formula Builder to include aggregate functions like Minimum, Maximum, Sum and Average
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)
...
Usability
Common
DAP-7851 - Activity Log - Track every activity performed by the user in app builder.
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have a static action item screen that doesn't have configuration support. Purpose: To upgrade app builder action item to a configurable action item frameworkdon’t have any data validation rule for supporting uniqueness. We have this feature only from the data import screen.
Purpose: To improve usability and data validation capabilities.
Enhanced System: With this upgrade, the 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. Define a field or a set of fields as unique. (Max of 5 fields per form).
This property is available for all fields except for multi-select controls.
As the system needs to evaluate the uniqueness check on every record save, this app will not be available in offline mode.
Additional filter configurations can be applied in form properties section - (for example, to define the date range or the status of transaction records for the unique criteria evaluation)
Impacts on existing forms: No
Available in Supported on Mobile: Yes.
Web Details screen:
...
Mobile Details Screen
...
Clicking 'View action item' will navigate to List Screen
...
| Anchor |
|---|
...
|
...
|
...
7965 -
...
A framework to integrate an API so that complex business rules can be configured
Existing System: Currently, we have alerts and reminders for each action itemcan’t have any custom API integration in app.
Purpose: To be able to set default alerts and reminders as well as default owners for all action items created for an meet the diversified business needs of each app.
Enhanced System:
...
An API with custom logic can be integrated into an app.
The system would be able to set a default alert and reminder for every action item created for a particular app.
We can even set a default owner for the action items created for that app.
This setup is available in the Location setup → Administration Setup → Module Defaultspull data from an API and set a value to a control based on the API response.
The configuration of this feature for an app can be done only from the backend.
Currently, this feature is supported only on the web. In the future, we can support this on mobile online mode.
Impacts on existing forms: No impact.
Available in Mobile: NA
...
Supported on Mobile: No.
Example: Ability to check the status of all action items created for a MOC request and only if all are closed only then the status can be changed.
...
| Anchor |
|---|
...
|
...
|
...
Enhance Set Actions - Ability to set an empty value to control
Existing System: We currently populate 'Source Id' as 0 for all action items created from app builder. Currently, we don't have a configuration to set a control's value to blank.
Purpose: To be consistent with all modules and populate the system-generated id of the record as source idable to reset a few control for enhanced use of the system.
Enhanced System:
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. to assign an empty value to a control based on a condition and existing data will be overwritten with empty.
Configuration can be done by using the actions screen → set action.
This is most relevant in a workflow-based app where the use case is to reset all the approvals when the workflow is changed from 'Approved' to ‘On-Hold’ or ‘Pending’.
Impacts on existing forms: For all existing records, the source Id would auto-populateNone.
Available in Supported on Mobile: Yes.
...
The example below shows how to configure a blank value to a textbox, dropdown, and signature control.
...
| Anchor |
|---|
...
|
...
|
...
6402 -
...
Configuration to set the number of decimal values to be displayed for a numeric control
Existing System: Currently, duplicate calendar categories are getting created if an app is renamed.
Purpose: To always have a unique calendar category even if the form name is updated.
Enhanced System:
...
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).
...
system is printing all the decimal digits in all the reports, notifications.
Purpose: To be able to round off digits for numeric controls
Enhanced System:
User would be able to get this additional configuration only when the numeric control is defined as "Decimal".
When a user is entering data, post save the system would round off the number to a preset number of digits.
The same is the case when a formula is getting evaluated, the system would be able to round off the resultant value.
Reports and Notifications will be printing the value as per the round-off configuration.
Impacts on existing forms: Yes, all action items are moved under latest category.
Available in Mobile: NA.
...
None, the round-off digits configuration would be blank.
Supported on Mobile: Yes.
The example below shows how to set Round off Digits as 2 to the “Initial Exposure Score” control.
...
| Anchor |
|---|
...
|
...
|
...
7611 -
...
Ability to set a specific time in the formula builder
Existing System: Currently, there is no support for aggregate functions we are unable to set a time (Eg: 10:30 Pm) to time control in the formula builder.
Purpose: To be able to support risk score calculations that are based on Minimum and Maximumenhance the formula builder for time controls.
Enhanced System: The user would be able to:
Configure a 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 SectionsThis configuration is even available in set actions as well.
default value where he can assign a static time to a time control.
Impacts on existing forms: No impact.
Available in Supported on Mobile: Yes.
...
The example below shows how to set time = 5:30 Pm to the “Time of Request” control.
...
| Anchor |
|---|
...
|
...
|
...
6891 - Ability to configure dependency between a single and a multi-selection control
Existing System: Currently, we don’t have sub-label display support in andriod. can’t configure a dependency for any multiple selection control.
Purpose: To improve usability.
Enhanced System: Changes include:
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: None.
Available in Mobile: Yes.
...
...
Existing System: 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:
...
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.
...
establish dependency between Single-Selection control (as a parent) and Multple-Selection Control(as a child).
Enhanced System: In the enhanced system, the user would be able to
Configure a dependency between an employee dropdown (Multi-Select) and a supervisor dropdown (Single-Select).
Based on the supervisor selected, only those employees who report to him would appear in the dropdown and the user can select multiple employees.
All Multiple selection controls have this option to establish dependency.
Impacts on existing forms: None.
Available in Supported on Mobile: Yes.
...
| Anchor |
|---|
...
|
...
|
...
131 - Introduce a copy feature in actions
Existing System: Currently, We we don’t have this feature only on andriod and weba feature to copy an action.
Purpose: To improve usability of a segmented control.
Enhanced System: 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 already available in android and now will be available on iOS too.
Impacts on existing forms: None.
Available in Mobile: Yes.
...
...
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.
...
The user would be able to select a particular action and copy it.
The system would create a duplicate of the selected action and later user would be able to modify it as per the needs and re-save.
The sequence of the newly created action would be right after the original action.
Impacts on existing forms: This additional property will be blank for all the existing formsNone.
Available in Supported on Mobile: Available on Andriod NA.
...
Supervisor Selection
...
Ability to see additional display value (Emp Id in the below example)
...
...