Skip to main content

RADplus 2023 Update 104

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Monthly Release 2023.04.00

Product Update Description

The following enhancements are made to multi-server systems modeling sync functionality: 1) Report modeling is enhanced to make use of the modeling sync web services. 2) 'Table Definition' is modified to check the LIVE and UAT systems for conflicts when creating a new column. Finally, an issue is resolved that could cause modeled diagnosis fields to fail to populate due to a column alias build error. NOTE: The multi-server system sync functionality in this update requires that it be installed into all environments.

Required Updates

None

Included Updates

2, 4, 6, 7, 8, 12, 13, 14, 22, 25, 26, 29, 33, 35, 39, 47, 49, 52, 55, 56, 58, 59, 60, 64, 69, 71, 75, 80, 83, 85, 86, 87, 88, 89, 90, 91, 97, 97.1, 98, 101

Details
NEW2 CHANGED0 FIXED1
New (2)
Report Definitions
In "(MSE) Mult-Server Environment" configured systems, "Report Definition" modeling is enhanced to keep "Report Definitions" created in sync, in the BLD, LIVE and UAT systems
Value Added: Adds additional checks to ensure that report definitions are in sync between systems that exist in a 'Multi Server Environment'
Topics
• Report Definition Import
 
Table Definition
In "(MSE) Mult-Server Environment" configured systems, the "BLD" system is enhanced to check the 'LIVE' and 'UAT' systems for conflicts, when adding a new column in form "Table Definition"
Value Added: Ensures that modeling table definition field numbers are kept in sync between systems that exist in a 'Multi Server Environment'
Topics
• Envelope Export • Envelope Import • Modeling
 
Fixed (1)
Modeled form - diagnosis fields
An issue is resolved to ensure that "Table Alias" diagnosis fields configured on a Modeled form, populated diagnosis data as expected
Topics
• Diagnosis • Modeling
 
Acceptance Tests
AV-67958 Summary | Details
Report Definitions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Report Definition Export
Scenario 1: 'Report Definition': (MSE) Multi-Server Environment (Form "Create/Export/Import/Delete") - Validations
Specific Setup:
  • Have three systems, each set up initially with identical databases
  • Configured to communicate with each other over the network in a (MSE) Multi-Server Environment
  • One configured as BLD, one configured as UAT, one configured as LIVE
  • Have a "Report Definition" export file, exported from a system outside the current MSE testing systems. [ExternalReport]
  • As the testing user, have separate avatar session open for each system (BLD, UAT, and LIVE), and log in each environment
Steps
  1. In LIVE,
  2. Open form "Report Definition Import"
  3. Select [ExternalReport], the report definition exported from an external system, as noted in the setup
  4. Validate import is not permitted, with a message indicating that the report does not exist in BLD environment
  5. In BLD
  6. Open form "Report Definition Import"
  7. Select [ExternalReport], validate import is permitted
  8. Click to import the report
  9. Validate import is successful
  10. Open form "Report Definition Export"
  11. Select [ExternalReport]
  12. Export the report [ExternalReportExport] and save the file
  13. In LIVE
  14. Open form "Report Definition Import"
  15. Select [ExternalReportExport],
  16. Validate import is now permitted, now that it has been exported from BLD.
  17. Import the report
  18. Validate import is successful
  19. In BLD
  20. Open form "Report Definition" and create a new definition [ReportA] with two or more parameters
  21. Submit the report and validate submission is successful
  22. Open "Report Definition Export"
  23. Export the definition [ReportExportA] and save the file
  24. In one of the other systems, for this test LIVE is used
  25. Open form "Report Definition Import"
  26. Import [ReportExportA] as 'New'
  27. Validate import is successful
  28. In BLD
  29. Open "Report Definition" to edit [ReportA]
  30. Delete one of the existing parameters.
  31. Submit the form
  32. Return to "Report Definition"
  33. Create another new report definition with one or more parameters [ReportB]
  34. Submit the form and validate submission is successful
  35. Open "Report Definition" Export
  36. Select [ReportB] for export
  37. Validate export is successful [ReportExportB]
  38. In LIVE
  39. Open "Report Definition Import"
  40. Import [ReportExportB]
  41. Validate import is successful
  42. In BLD
  43. Open form "Report Definition Deletion"
  44. Select [ReportB]
  45. Validate a warning message indicating that deleting this report definition will also delete from the following Avatar instances via web service calls, LIVE, is displayed. Click [OK]
  46. Click the "Yes" check box to confirm deletion
  47. Click [Submit]
  48. Validate the "Report Definition Deletion Web Service Dialog", is presented and indicates "In addition to the current environment, this report definition has been deleted from the following environments: LIVE"
  49. Click [OK]
  50. Open "Report Definition"
  51. Search for [ReportB]
  52. Validate is not found, as expected. Close the form
  53. In LIVE
  54. Open "Report Definition"
  55. Validate [ReportB] cannot be found, as expected
  56. Close the form
  57. Open "Report Definition" Import
  58. Click [Select Report Import File] and select [ReportExportB]
  59. Validate a critical error preventing import is displayed, as the report definition does not exist in BLD yet since it was deleted in step 8
  60. In BLD
  61. Open "Report Definition Import"
  62. Click [Select Report Import File] and select [ReportExportB]
  63. Validate is import is successful
  64. In LIVE
  65. Open "Report Definition Import"
  66. Click [Select Report Import File] and select [ReportExportB]
  67. Validated is import is successful now, as the report exists in BLD
  68. Close the form
  69. In LIVE
  70. Re-open "Report Definition" Import
  71. Click [Select Report Import File] and select [ReportExportB] again as "New"
  72. Validate is import is blocked, with message "This report already exists within this system. New copies must be created in the BLD environment first, then moved to the other environments"
  73. Open "Report Definition Export""
  74. Select [ReportB] for export
  75. Validate export is blocked with the following message "This form is not accessible in this environment"
  76. Click [OK] and close the form
  77. In BLD, repeat step 12b
  78. Export the file
  79. Validate export from BLD is successful, as expected
Topics
• Report Definition Import
AV-92397 Summary | Details
Table Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Definition (MSO)
  • Form Definition (MSO)
  • Table Definition (MSO)
Scenario 1: 'Modeling ': (MSE) Multi-Server Environment (Modeled Form "Create/Export/Import/Delete") - Validations
Specific Setup:
  • Have three systems, each set up initially with identical databases
  • Configured to communicate with each other over the network in a (MSE) Multi-Server Environment
  • One configured as BLD, one configured as UAT, one configured as LIVE
  • Have an existing envelope [TestEnvelope] containing a form [TestForm], that exists in BLD and also existing in ether UAT or LIVE. For this test UAT is used
  • [TestForm] contains one or more desired fields on the form, but does not yet contain a "Display" type section, a "Label" field or a 'Report" field
  • In BLD, open form "Form Definition" to edit [TestForm]
  • In the existing main section, add a "Label" and a "Report" object
  • Now add a new section, and choose 'Display' as the type of section.
  • Submit the form and validate submission is successful
  • As the testing user, open a separate avatar session for each system (BLD, UAT, and LIVE), and log in
Steps
  1. In BLD
  2. Open form "Envelope Export" and select [TestEnvelope]
  3. Export the envelope and save the export file in a desired location
  4. Validate export is successful
  5. Log into either LIVE or UAT. For this test UAT is used
  6. Open "Envelope Import" and import [TestEnvelope] as an overwrite
  7. Validate the import is successful
  8. In BLD,
  9. Open "Form Definition" and select [TestForm]
  10. Navigate the "Section Definition" section and delete the "Display" section
  11. Navigate to the "Object Definition" section and delete the "Label" and the "Report" fields
  12. Submit the form.
  13. Validate submission is successful
  14. Staying in BLD
  15. Create a new envelope in "Envelope Definition" [NewTestEnvelop]
  16. Create a new table in "Table Definition" [NewTestTable] with any desired field types
  17. Create a new form in "Form Definition" [NewTestForm], that includes the fields from the table
  18. Validate submissions are successful
  19. Open "Envelope Export"
  20. Export [NewTestEnvelope] and save the file
  21. In UAT
  22. Open "Envelope Import" and select [NewTestEnvelope] for import as 'New'
  23. Validate the import is successful
  24. Staying in UAT
  25. Open [NewTestForm] for any client
  26. Populate the fields and submit the form
  27. Validate submission is successful
  28. In BLD,
  29. Open form "Table Deletion"
  30. Select [NewTestTable]
  31. Validate a message " The selected table is used within one or more forms. It must be removed from all forms prior to deletion."
  32. Close the form
  33. Open form 'Table Definition' to edit [NewTestTable]
  34. Navigate to the "Column Definition" section
  35. Select one of the table columns and click "Delete" to remove it from the table
  36. Validate deletion is blocked, with a message "This field is in use in the following environments and cannot be deleted: UAT"
  37. Click [OK] and close the form
  38. Open form "Form Definition"
  39. Select [NewTestForm] for deletion
  40. Validate an error is displayed blocking submission indicating is there is data present in the form in UAT.
  41. Close the form
  42. In UAT
  43. Open form "NewTestForm"
  44. Select the row filed in step 4 in the pre-display
  45. Click [Delete] to remove the row
  46. In BLD
  47. Open form 'Form Deletion' and select [TestForm] for deletion
  48. Validate a message is displayed that contains "Deleting this form will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion?"
  49. Click [OK]
  50. At prompt "Are you sure that you want to delete this form", click the "Yes" checkbox
  51. Submit the form
  52. Validate the"Form Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this form has been deleted from the following environments: UAT
  53. Click [OK]
  54. Validate submission is successful
  55. Open form "Table Deletion" and select [NewTestTable] for deletion
  56. Validate a message is displayed that contains "Deleting this table will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion?"
  57. Click [OK]
  58. At prompt "Remove table from RADplus_audit_database_tables? ", select the desired response, "Yes" or "No"
  59. Submit the form
  60. Validate the"Table Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this table has been deleted from the following environments: UAT
  61. Click [OK]
  62. Validate submission is successful
  63. Open form Envelope Deletion' and select [NewTestEnvelope] for deletion
  64. Validate a message is displayed that contains "Deleting this envelope will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion??"
  65. Click [OK]
  66. At prompt "Remove table from RADplus_audit_database_tables? ", select the desired response, "Yes" or "No"
  67. Submit the form
  68. At prompt "Are you sure that you want to delete this Envelope", click the "Yes" checkbox
  69. Submit the form
  70. Validate the"Envelope Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this form has been deleted from the following environments: UAT
  71. Validate submission is successful
  72. In UAT
  73. Open "Form Definition" and search for [NewTestForm]
  74. Validate the form is not found, as expected
  75. Open "Table Definition" and search for [NewTestTable]
  76. Validate the table is not found, as expected
  77. Open "Envelope Definition" and search for [NewTestEnvelope]
  78. Validate the envelope is not found, as expected
Topics
• Modeling
AV-92869 Summary | Details
Modeled form - diagnosis fields
Scenario 1: Modeled Forms - Validate "Diagnosis History (ICD-10)" Table Alias field data
Specific Setup:
  • Have a Modeled form [TestForm], configured in 'Table Definition" to use the "Alias Table", "Diagnosis History (ICD10)"
  • [FieldA] is mapped to alias table column "Diagnoses Search (Row1)"
  • [FieldB] is mapped to alias table column "Diagnoses Search (Row2)"
  • [FieldC] is mapped to alias table column "Diagnoses Search (Row3)"
  • Have a client [TestClient] with up to three diagnosis, submitted in form "Diagnosis"
  • Diagnosis (Row1) in the form, is populated with diagnosis value [Diag1]
  • Diagnosis (Row2) in the form, is populated with diagnosis value [Diag2]
  • Diagnosis (Row3) in the form, is populated with diagnosis value [Diag3]
  • Have access to the "Diagnosis" form
Steps
  1. Open [TestForm]
  2. Select [TestClient]
  3. Navigate to the section of the form where the mapped diagnosis fields reside
  4. Validate [FieldA] is displayed with previous diagnosis [Diag1] submitted in the set up, as expected
  5. Validate [FieldB] is displayed with previous diagnosis [Diag2] submitted in the set up, as expected
  6. Validate [FieldC] is displayed with previous diagnosis [Diag3] submitted in the set up, as expected
  7. Navigate [FieldA]
  8. Search for and select a new diagnosis [NewDiag1]
  9. Navigate [FieldB]
  10. Search for and select a new diagnosis [NewDiag2]
  11. Navigate [FieldC]
  12. Search for and select a new diagnosis [NewDiag2]
  13. Submit the form
  14. Validate the form submits successfully
  15. Select [TestClient]
  16. Open form "Diagnosis"
  17. Navigate to the "Diagnoses" grid
  18. Double click to select Row ID "1"
  19. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag1], submitted in step 1c
  20. Double click to select Row ID "2"
  21. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag2], submitted in step 1d
  22. Double click to select Row ID "3"
  23. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag3], submitted in step 1e
  24. Close the form
Topics
• Diagnosis • Modeling