Skip to main content

RADplus 2024 Update 23

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Update 93
RADplus 2023 Update 96
RADplus 2024 Monthly Release 2024.00.01

Product Update Description

The error '[UNDEFINED]GetWorkflowStatus+5^GUIObjectHADF1', which can occur when restoring a temporary backup, is resolved. An issue where simultaneous ODBC connection requests may fail to login is resolved. In addition, error logging for the 'Connect/Disconnect Application Namespace' form is improved.

Required Updates

None

Included Updates

None

Details
NEW0 CHANGED1 FIXED2
Changed (1)
Connect/Disconnect Application Namespace
Error logging for the 'Connect/Disconnect Application Namespace' form is enhanced to ensure all errors are recorded
Value Added: Enhances logging of errors that are found during form submission
Topics
• Database Management
 
Fixed (2)
"Service Documentation" enabled modeled forms
An issue is resolved to ensure that "AutoSave" functionality works as expected for "Service Documentation" enabled modeled forms, when the registry setting "Default to Draft" is either enabled or disabled.
Topics
• 837 Institutional • 837 Professional • About... • Accounts Receivable Management • Accu-Chek • Add New Appointment • Add Non-User Signature • Administration Location • Auto Save • NX • Service Documentation
 
ODBC connection requests
An issue is resolved to ensure that multiple ODBC requests made to a database, can be made successfully
Topics
• Database Management
 
Acceptance Tests
AV-94577 Summary | Details
Connect/Disconnect Application Namespace
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Application Namespace Connections Validation
  • Connect/Disconnect Application Namespace
Scenario 1: Connect/Disconnect Application Namespace - Disconnect Database/then Reconnect with "CDR" Link 'enabled'
Specific Setup:
  • Have a system with a child namespace, for example "Avatar MSO", that is already connected to the parent namespace, for example "Avatar PM", via the "Connect/Disconnect Application Namespace" form
  • Have a report to display data in the "SYSTEM.radplus_error_log" table
Steps
  1. Open the "Connect/Disconnect Application Namespace" form:
  2. From the "Application" field, select the application noted in the setup
  3. In the "Connect or Disconnect" field, select:
  4. "Connect/Maintain Connection/Repair Connection".
  5. Submit the form (Note submission can take some time):
  6. Validate submission is successful.
  7. Close the form
  8. Run the report based on the "SYSTEM.radplus_error_log"
  9. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  10. Re-open the "Connect/Disconnect Application Namespace" form:
  11. From the "Application" field, select the application noted in the setup
  12. In the "Connect or Disconnect" field, select:
  13. "Connect/Maintain Connection/Repair Connection"
  14. In the "Clinical Data Repository (CDR) Link", select "No"
  15. Submit the form (Note submission can take some time):
  16. Validate submission is successful.
  17. Run the report based on the "SYSTEM.radplus_error_log"
  18. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  19. Open form "Applications Namespace Connection Validations":
  20. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  21. Validate there is a message stating "There are no Application/Namespace errors".
  22. Close the form.
Scenario 2: Connect/Disconnect Application Namespace - Disconnect Database/then Reconnect with "CDR" Link 'disabled'
Specific Setup:
  • Have a system with a child namespace, for example "Avatar MSO, that is already connected to the parent namespace, for example "Avatar PM", via the "Connect/Disconnect Application Namespace" form
  • Have a report to display data in the "SYSTEM.radplus_error_log' table
Steps
  1. Open the "Connect/Disconnect Application Namespace" form:
  2. From the "Application" field, select the application noted in the setup
  3. In the "Connect or Disconnect" field, select:
  4. "Connect/Maintain Connection/Repair Connection".
  5. Submit the form (Note submission can take some time):
  6. Validate submission is successful.
  7. Close the form
  8. Run the report based on the 'SYSTEM.radplus_error_log"
  9. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  10. Re-open the "Connect/Disconnect Application Namespace" form:
  11. From the "Application" field, select the application noted in the setup
  12. In the "Connect or Disconnect" field, select:
  13. "Connect/Maintain Connection/Repair Connection"
  14. In the "Clinical Data Repository (CDR) Link", select "Yes"
  15. Submit the form (Note submission can take some time):
  16. Validate submission is successful.
  17. Run the report based on the "SYSTEM.radplus_error_log"
  18. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  19. Open form "Applications Namespace Connection Validations":
  20. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  21. Validate there is a message stating "There are no Application/Namespace errors".
  22. Close the form.
Topics
• Database Management
AV-94934 Summary | Details
"Service Documentation" enabled modeled forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
Scenario 1: Service Documentation - Validate 'Autosave' functionality (Registry setting "Default to Draft" set to "N")
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • Open 'Form Definition' for the [TestForm] and set 'Form supports automatic backup' to 'Yes'.
  • Registry setting "RADplus->Modeling->Settings->Default To Draft" is set to "N"
  • An appointment [TestAppt] has been scheduled with a client [TestClient] in form "Appointment Scheduling"
  • An existing service exists for [TestClient]
Steps
  1. Open form [TestForm]
  2. Select [TestClient] in the client search field
  3. In the "Documentation For" selection field
  4. Select "Existing Appointment"
  5. Validate the "Draft/Final" field has 'not' defaulted to "Draft" selected, as expected
  6. Do not make a selection in the field
  7. Populate any other required or desired fields
  8. Click the "Backup Form" button to auto save your changes
  9. Validate a message is displayed on the form indicating the time of the backup.
  10. Close the form
  11. Reopen form [TestForm]
  12. Select [TestClient] in the client search field
  13. Validate "Restore/Delete Backup Data" screen is displayed
  14. Validate a row is displayed indicating there is an unsubmitted backup
  15. Click "Yes" to accept the backup
  16. Validate [TestForm] is loaded successfully
  17. Validate the "Draft/Final" field has 'not' defaulted to "Draft" selected, as expected
  18. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  19. Submit the form
  20. Validate the form submits successfully
  21. Re- open form [TestForm]
  22. Select [TestClient] in the client search field
  23. Select the row just submitted
  24. Validate the "Draft/Final" field has 'not' defaulted to "Draft" selected, as expected
  25. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  26. Repeat steps 1 thru 3 for [TestClient]
  27. Selecting the clients existing service in the "Documentation For" selection field and clicking the "Backup Form" button to auto save your changes
  28. Validate results are as expected
Scenario 2: Service Documentation - Validate 'Autosave' functionality (Registry setting "Default to Draft" set to "Y")
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • Open 'Form Definition' for the [TestForm] and set 'Form supports automatic backup' to 'Yes'.
  • Registry setting "RADplus->Modeling->Settings->Default To Draft" is set to "Y"
  • An appointment [TestAppt] has been scheduled with a client [TestClient] in form "Appointment Scheduling"
  • An existing service exists for [TestClient]
Steps
  1. Open form [TestForm]
  2. Select [TestClient] in the client search field
  3. In the "Documentation For" selection field
  4. Select "Existing Appointment"
  5. Validate the "Draft/Final" field has defaulted with "Draft" selected, as expected
  6. Populate any other required or desired fields
  7. Click the "Backup Form" button to auto save your changes
  8. Validate a message is displayed on the form indicating the time of the backup
  9. Close the form
  10. Reopen form [TestForm]
  11. Select [TestClient] in the client search field
  12. Validate "Restore/Delete Backup Data" screen is displayed
  13. Validate a row is displayed indicating there is an unsubmitted backup
  14. Click "Yes" to accept the backup
  15. Validate [TestForm] is loaded
  16. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  17. Validate in the "Draft/Final" is set to "Draft", as expected
  18. Submit the form
  19. Validate the form submits successfully
  20. Re- open form [TestForm]
  21. Select [TestClient] in the client search field
  22. Select the row just submitted
  23. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  24. Validate in the "Draft/Final" is set to "Draft", as expected
  25. Repeat steps 1 thru 3 for [TestClient]
  26. Selecting the clients existing service in the "Documentation For" selection field and clicking the "Backup Form" button to auto save your changes
  27. Validate results are as expected
Topics
• Auto Save • Service Documentation
AV-95526 Summary | Details
ODBC connection requests
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
Scenario 1: Validate successfully executing ODBC connections to the Avatar database
Specific Setup:
  • Have a standard cache server set up to run reports direct from the database and/or an "ECP" server configured (by Netsmart) to connect to the cache database server, so that reports can be generated via the "ECP" server
  • [TestUserA] has an "ODBC Data Source Administrator" connection set up and has access to the utility program for testing
  • [TestUserA] has "ODBC" SQL table access assigned in myAvatar to [TestTableA] and [TestTableB] any other desired tables
  • [TestUserA] has a two reports setup using their ODBC connection
  • [TestReportA] set up to access data in [TestTableA]
  • [TestReportB] set up to access data in [TestTableB]
  • [TestClient] has a row of data submitted in [TestTableA] and [TestTableB]
  • [TestUserB] has permission to form "User Definition" to update SQL table access for [TestUserA]
Steps
  1. As [TestUserA], open the Windows "ODBC Data Source Administrator" utility program
  2. In the "User Data Sources" list, select the connection set up for [TestUser]
  3. Validate the "Host", "Port", "Cache Namespace", "System Code", "Username" and "Password" fields, contain the appropriate values
  4. Click [Test Connection]
  5. Validate the connections is successful
  6. Leave the utility program open
  7. Open [TestReportA] and [TestReportB]
  8. Click to preview the [TestReportA]
  9. Right away, click to preview the [TestReportB]
  10. Validate results are as expected for [TestTableA] and [TestTableB]
  11. Log into Avatar as [TestUserB]
  12. Open form "User Definition" and select [TestUserA] for edit
  13. Navigate to the "Forms and SQL Access" section and click "Select Tables for Product SQL Access"
  14. From the "Tables" tree list, either select or deselect any desired table(s)
  15. Click [OK]
  16. Don't submit the form
  17. As [TestUserA]:
  18. Click to preview the [TestReportA]
  19. Validate results are as expected for [TestTableA]
  20. As [TestUserB]:
  21. Submit the "UserDefinition" form left open in step 3
  22. Right away, as [TestUserA]
  23. Click [Test Connection] in "ODBC Data Source Administrator" utility program left open in step 1
  24. Validate the connections is successful
  25. As [TestUserB]:
  26. Repeat step 3, modifying table permissions for [TestUserA]
  27. As [TestUserA]:
  28. Click to preview the [TestReportA] again
  29. Validate results are as expected for [TestTableA]
  30. As [TestUserB], submit "User Definition" left open in step 5
  31. Right away as [TestUserA]
  32. Click to preview the [TestReportA]
  33. Validate results are as expected for [TestTableB]
Topics
• Database Management