Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
222
222

New and Improved Features

...

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

...

  • 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. 

...

Anchor
6822
6822
 DAP-6822 - Introduce a configuration to Include QR Code in the System Generated Report

Existing SystemCurrently, we don't have an option to print QR code in the report header.  

Purpose: To improve the usability of PDF report.

...

Enhanced System: Changes include

  • The user would be able to now see the 'Static icons' configured for the fields now in android as well. 
  • DAP-4893 - Andriod - Segmented Control Changes - Values with long text are getting truncated
  • DAP-5786 - Andriod - Tree View Control changes for Inactive parent nodes

Impacts on existing forms: No. 

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

Back to top

...

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

...

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

...

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

...

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