Skip to main content

RADplus 2023 Update 126

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Monthly Release 2023.03.02

Product Update Description

The 'Generate Form Map' field is added to the 'Form And Table Documentation' form. This field will generate an HTML document containing all events associated to a modeled form or site specific section modeling form.

Required Updates

None

Included Updates

None

Details
NEW1 CHANGED0 FIXED0
New (1)
'Form and Table Documentation' form
The 'Generate Form Map' field is added to the 'Form And Table Documentation' form. This field will be available for any "Modeled" form as well as any "Product" form that are available for site specific modeling in form "Site Specific Section Modeling".
The new field will generate an "HTML" web page (.htm) document containing all fields on the form and their associated field numbers along with details of any field event logic configured on the form
Value Added: Provides the users the ability to see what event logic is currently configured on fields in the form
Topics
• Forms • Modeling
 
Acceptance Tests
AV-90092 Summary | Details
'Form and Table Documentation' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form and Table Documentation (PM)
  • App Dashboard
  • NetsmartFormMap Web Page
Scenario 1: "Form and Table Documentation" form (Modeled Forms) - Validate "Generate Form Map' report results
Specific Setup:
  • Have a "Modeled" form that contains event logic defined on the form [FormA].
  • Make a note or all the fields on the form.
  • Make a note of the event logic defined on the form.
  • Have a "Modeled" form that does 'not' contain event logic defined on the form [FormB]
  • Make a note or all the fields on the form
  • Have access to form "Form and Table Documentation"
Steps
  1. Open 'Form and Table Documentation'.
  2. Set 'Type of Documentation' to 'Form'.
  3. Select "Individual" in the "Individual or All Forms" field
  4. Select [FormA] from the 'Form to be Documented' field. (Modeled form with event logic defined)
  5. Navigate to the "Generate Form Map" button and click to launch the w
  6. Validate the user is presented with a file explorer dialog [Note: In Avatar NX the file will automatically be created and saved in the windows "Downloads" directory on the server]
  7. Validate the (.htm) type file name field is populated in the file name field
  8. Validate the file name includes the associated internal "FormID' for [FormA], followed by its form "Name". For example: "NetsmartFormMap_USER9_Modeled Form with Event logic"
  9. Select a folder location to save the file and click [Save]
  10. Navigate to the location of the (.htm) file
  11. Click to open the file
  12. Validate the title of the report reflects the name of [FormA] and its associated internal "FormID"
  13. Validate each "Section" name is displayed on the form as expected with each field contained in that section listed beneath it
  14. Validate the field names contain both the name and its associated field number in brackets, for example "Date of Entry (777.77)"
  15. Locate a field on the form that contains event logic defined
  16. Validate the event logic noted in the setup is displayed as expected. For example:
  17. Date of Entry(777.77)
  18. Type of Event: Result of Input With Value Checking
  19. Compare with For Event: Specific Value
  20. Specific Value: 12/06/2022
  21. Relationship To Comparison Value to Trigger Event: Less Than
  22. Set Specific Objects to Required on Event: Yes
  23. Required: Integer (FormA_Integerfield)
  24. Close the page
  25. Select [FormB] from the 'Form to be Documented' field. (Modeled form with 'no' event logic defined)
  26. Repeat steps 1a thru 1e
  27. Validate results are as expected
  28. Close the form
Scenario 2: "Form and Table Documentation" form (Product Forms) - Validate "Generate Form Map' report results
Specific Setup:
  • Have a "Product" form that is available to be configured for site specific section modeling in form "Site Specific Section" modeling and contains event logic defined on the form [FormA]. For example form "Update Client Data"
  • Make a note or all the fields on the form.
  • Make a note of the event logic defined on the form
  • Have a "Product" form that is available to be configured for site specific section modeling in form "Site Specific Section" modeling and does 'not' have event logic defined on the form [FormB]. For example form "Client Charge Input"
  • Make a note or all the fields on the form
  • Have a "Product" form that is 'not' available to be configured for site specific section modeling in form "Site Specific Section" modeling [FormC]. For example, the "Billed Charges" form'
  • Have access to form "Form and Table Documentation"
Steps
  1. Open 'Form and Table Documentation'.
  2. Set 'Type of Documentation' to 'Form'.
  3. Select "Individual" in the "Individual or All Forms" field
  4. Select [FormA] from the 'Form to be Documented' field. (A 'Product' form that can be configured with site-specific section modeling and contains event logic defined)
  5. Navigate to the "Generate Form Map" button and click to launch the report
  6. Validate the user is presented with a file explorer dialog. [Note: In Avatar NX, the file will automatically be created and saved in the windows "Downloads" directory on the server]
  7. Validate the (.htm) type file name field is populated in the file name field
  8. Validate the file name includes the associated internal "FormID" for [FormA], followed by its form "Name". For example: "NetsmartFormMap_PATIENT14_Update Client Data.htm"
  9. Select a folder location to save the file and click [Save]
  10. Navigate to the location of the (.htm) file
  11. Click to open the file
  12. Validate the title on the page reflects the name of [FormA] and its associated internal "FormID". For example, "Update Client Data (PATIENT14)"
  13. Validate each "Section" name is displayed on the form as expected, with each field contained in that section listed beneath it.
  14. Validate the field names contain both the name and its associated field number in brackets, for example "Date of Citizenship (631.1)"
  15. Locate a field on the form that contains event logic defined
  16. Validate the event logic noted in the setup is displayed as expected. For example:
  17. Date of Citizenship (631.1)
  18. Type of Event: Valid Entry
  19. Prompts To Be Disabled: Gender Identity (730)
  20. Close the page
  21. Select [FormB] from the 'Form to be Documented' field. (A 'Product' form that can be configured with site-specific section modeling and does 'not' contain event logic)
  22. Repeat steps 1a thru 1c
  23. Validate results are as expected
  24. Close the form
  25. Open 'Form and Table Documentation'.
  26. Set 'Type of Documentation' to 'Form'.
  27. Select "Individual" in the "Individual or All Forms" field
  28. Select [FormC] from the 'Form to be Documented' field. (The 'Product' form that can 'not' be configured with site-specific section modeling)
  29. Validate "Generate Form Map" button is not present on the form as expected
Topics
• Forms • Modeling