Skip to end of banner
Go to start of banner

22.2 App Builder Release Notes - Draft

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

New and Improved Features


New Features

Enhancements

Usability

  • DAP-7127 - Usability changes to "Field Settings" option in manage data sources
  • DAP-7008 - Ability to concatenate (or show as a sub-label) another data source field in a dropdown
  • DAP-6822 - Introduce a configuration to Include QR Code in the System Generated Report
  • DAP-5944 - Andriod iOS Gaps 

Technical

  • DAP-6769 - .NET Core version 3.1 to 6.0 Upgrade (DAPI & MAPI)
  • DAP-6831 - xUNIT - .NET UNIT Testing Framework Implementation in AppBuilder Microservices
  • DAP-6830 - Jest - React UNIT Testing Framework Implementation in AppBuilder

DAP-6758 - Enhanced Related Data Control - Ability to create a record and link it

Existing System: Currently, we would only be able to search a record and link. 

Purpose: User should be able to add a record and link with smoother navigation.

Enhanced System: The user would be able to: 

  • Create a record from the parent form without any hassel.
  • On save, the record not only gets saved but also is linked to the parent record where it is referenced.
  • This feature is configurable. All existing apps would be defaulted to "Search" only option.
  • Users can modify the app and select "Both - Search & Add", or only "Add". 

Impacts on existing forms: No

Available in Mobile: Yes.

Details screen changes: 

MobileWeb


Configuration: 


Back to top

 DAP-7051 - Flexibility to download attachments from notification

Existing SystemCurrently, we don't have an option to download an attachment from notification. 

Purpose: To access attachments from notification. 

Enhanced System: 

  • Users would be able to download the attachments from notification.
  • If an upload control is configured in a notification, then a hyperlink is made available. 
  • On clicking the hyperlink of the attachment, it would redirect user to our processmap application and ask for authorization. 
  • Once authorized, the attachment automatically downloads. 

Impacts on existing forms: No impact. 

Available in Mobile: NA 


Back to top

 DAP-6793 - Physical Demand Analysis(PDA) App Integration with Occ. Health

Existing System: We currently don't have a solution for capturing PDA metrics.  

Purpose: To provide the ability to capture and compare the PDA metrics against the employee job requirements. 

Enhanced System:

  • User would be able to enter physical, environmental, and cognitive metrics for every job classification

  • Medical staff would be able to associate the PDA records with the employee restriction summary record. 
  • Once the association is done, the system would generate the comparison report between the restrictions identified and the PDA. 
  • This report would help the supervisor to decide whether the employee is fit for the job role. 
  • Users would also be able to navigate to the associated PDA record from occ. health module with a single click. 

Impacts on existing forms: No impact 

Available in Mobile: NA 


Back to top

DAP-7007 - Introduced "Users By Role" Datasource 

Existing System: Currently, we have only "Users By Group" data source. 

Purpose: To be able to select the users with the help of role filter. 

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. 
  • While entering the data, only users belonging to a selected role will show up in the details screen.  

Impacts on existing forms: No 

Available in Mobile: Yes. 


Back to top

DAP-7127 - Usability changes to "Field Settings" option in manage data sources

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. 

Purpose: To improve the usage of the feature and help users configure the right data type for each column. 

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. 

Impacts on existing forms: No impact 

Available in Mobile: NA.


Back to top

DAP- 6631 - Changes to "Add" behavior of a repeater section

Existing System:

  • Currently, we have usability issues with the add button of a repeater. 
  • When Add is clicked, the user also has to expand the repeater section if it is collapsed. 

Purpose: To improve usability.  

Enhanced System: Changes include:  

  • When “+Add“ is clicked, repeater section should expand (even when it is in collapsed mode) and show one instance to enter data. 

  • Also, if there are already instances added in the repeater, we should collapse all instances and only expand the instance where the user has to enter data.

  • Introduced “Expand All” and “Collapse All” options on the repeater section so that users can perform bulk Expand/ Collapse operations.

  • Sort option also added to sort the instances (Default ASC).

Impacts on existing forms: No impact 

Available in Mobile: Not available. 



Back to top

 DAP- 4382 - Enhance related data control to show attachments

Existing SystemCurrently, we don't show the upload controls in the display columns list.  

Purpose: To improve the usability of the related data control

Enhanced System: The user would be able to: 

  • View and configure upload controls as part of display columns. 
  • In details screen, when an asset is selected, system would also pull the attachments associated with the selected asset. 
  • We have also enabled the click and now user can click on asset card and navigate to the asset profile to view full details. 

Impacts to Existing Forms: No Impact. 

Available in Mobile: No. 


Configure Upload Controls in Display Columns: 



Ability to view asset files when an asset is selected: 


Back to top

DAP- 6081 - Ability to define what fields/sections of a form will be copied when the clone feature of a form is enabled

Existing System: Currently, on clicking copy, everything gets copied and we can't set any rules to copy only few sections. 

Purpose: To provide the flexibility to configure what sections to copy. 

Enhanced System: The user would be able to: 

  • Configure "Copy Rules" where user can set what sections to be copied. 
  • The configuration would have two options -  "Copy Everything Except" Or "Copy only Selected". 
  • For all existing forms, Copy rules will be blank and the user would be able to copy everything as per the current behavior.  

Impacts on existing forms: No, the user can copy everything. 

Available in Mobile: Yes, supported in both iOS and Android. 



Back to top

DAP- 6342 - Ability to add "Empty/Not Empty" conditions on system generated Id field

Existing System: Currently, user would not be able to configure actions for system-generated Id control. 

Purpose: To provide flexibility to configure actions that are "Save-Dependant". 

Enhanced System: User would be able to: 

  • Configure 'Empty' or 'Not Empty' based conditions for a System Generated Id.
  • If a user wants to have the application behave differently after record save, then this configuration will be much helpful as a system-generated Id gets generated when users hits save.
  • So, any condition like "Id is Empty" is configured means the behavior is applicable for record create scenarios. 
  • Similarly, any condition like "Id is Non-Empty" is configured means the behavior is applicable to all existing records which are already created and user wants to update it.

Impacts on existing forms: No

Available in Mobile: Yes on both iOS and Andriod.



Back to top


DAP- 6341 - Introduced a configuration for "Public/ Anonymous Document Link"

Configurable: Yes

  • Title 1:EnablePublicLink
  • Public/Private: Yes
  • Default: No
  • Title 2:AppBuilderUser

  • Public/Private: Yes
  • Default: Blank

Existing System: Currently, we have this functionality available without configuration abilities. 

Purpose: To provide configuration. 

Enhanced System: The user would be able to: 

  • Show/Hide the public notification link in the notification builder using "EnablePublicLink" custom setting. If value is set to "Yes" then public link would be shown. 
  • "App Builder User" custom setting will be used to set a particular user as the public user. We need to provide the User Id as the value to the custom setting

Impacts on existing forms: No

Available in Mobile: NA. 


Back to top

DAP- 5629 - Save only edited fields data (Parallel Users Case)

Existing System: Currently, when two users are updating the same record, data is getting overwritten. 

Purpose: To prevent data loss. 

Enhanced System: Changes include 

  • System would save only edited fields data and this will help users to prevent data loss if they edit fields of different sections. 
  • Apps that have Multi-approval workflow or Multi-Access configuration on different sections can take advantage of this feature. 

Impacts on existing forms: No

Available in Mobile: Yes, supported on both iOS and Android. 

Back to top

DAP- 6444 - Ability to record the source (iOS/Andriod) when a record is created/updated from mobile

Existing System: Currently, in the backend we save only whether the record is created/updated from web/mobile. 

Purpose: To uniquely identify the source (iOS / Andriod) for analytics or issue investigation. 

Enhanced System: Changes include

  • Differentiate the record which is created/updated from the android app and iOS app.
  • In the backend, the system would capture the source information. 

Impacts on existing forms: No

Available in Mobile: Yes, supported on both iOS and Android. 

Back to top

  • No labels