Skip to main content

RADplus 2023 Update 96.1

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Monthly Release 2023.03.01
RADplus 2023 Update 96

Product Update Description

An intermittent issue where external ODBC connections would authenticate but fail to return any data is resolved. An issue where the 'Avatar Sessions' widget may show incorrect user data for ODBC connections is resolved.

Required Updates

RADplus 2023 Update 96

Included Updates

96

Details

NEW0 CHANGED0 FIXED2
Fixed (2)
Data reports/queries
An issue is resolved to ensure that external and internal "ODBC" connections made to run reports/queries, authenticate and return data as expected
Topics
• Import Reports • Query/Reporting • SQL Data Access
 
Sessions Widget
An issue is resolved to ensure the 'Avatar Sessions' widget always displays the correct user data for ODBC connections
KB0075662 v0.01
Data reports/queries
An issue is resolved to ensure that external and internal "ODBC" connections made to run reports/queries, authenticate and return data as expected
Topics
• Forms Designer • Widgets • Import Reports • Query/Reporting • SQL Data Access
 
Acceptance Tests

Update 96 Summary | Details
Data reports/queries
Scenario 1: Validate data results from reports generated using an ODBC login connection
Specific Setup:
  • Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
  • Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
  • Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
  • Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
  • In form "Import Reports"
  • Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
  • [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
  • Have three modeled forms available for testing
  • [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
  • [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
  • [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
  • [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
  1. In application "Crystal Reports"
  2. Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
  3. Click to process the report
  4. Validate the report display all data as expected
  5. Close the report
  6. Repeat step 1a again to regenerate the report
  7. Validate results are as expected
  8. Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
  9. Click to process the report
  10. Validate the report display all data as expected
  11. Close the report
  12. Repeat step 1c again to regenerate the report
  13. Validate results are as expected
  14. Log in Avatar
  15. Search for and open [ReportC], the report imported to run from a menu
  16. Validate when selected form the menu, the report launches successfully
  17. Validate the report display all data as expected
  18. Close the report
  19. Repeat step 2a again to regenerate the report
  20. Validate results are as expected
  21. Close the report
  22. Search for and open [ReportD], the "Report Definition" report
  23. Populate any prompts on the form
  24. Click to process the report
  25. Validate the report display all data as expected
  26. Close the report
  27. Repeat step 2b again to regenerate the report
  28. Validate results are as expected
  29. Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
  30. Populate the form
  31. Submit the form as "Final"
  32. Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
  33. Approve/ route and submit the document
  34. Validate submission is successful
  35. Repeat step 2c again
  36. Validate results are as expected
  37. Search for and open [FormB], the form configured with a post filing report
  38. Populate the fields on the form
  39. Submit the form
  40. Validate the form files successfully
  41. Validate the post filing report [ReportF] is launched
  42. Validate the data is displayed as expected
  43. Repeat step 2e again to regenerate the report
  44. Validate results are as expected
  45. Search for and open [FormC], the form configured with the command button report
  46. Populate the fields on the form
  47. Navigate to the "Command Button" field
  48. Click the field to launch the report
  49. Validate [ReportG] is launched
  50. Validate data is displayed as expected
  51. Submit the form
  52. Validate the form submits successfully
  53. Validate the command button report [ReportF] is launched
  54. Validate the data is displayed as expected
  55. Submit the form
  56. Validate the form files successfully
  57. Repeat step 2g again to regenerate the report
  58. Validate results are as expected

Topics
• Import Reports • Query/Reporting • SQL Data Access
Update 96.1 Summary | Details
Sessions Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Crystal Reports or other SQL Reporting tool (ReportA)
Scenario 1: "Avatar Sessions" Widget - validate data results
Specific Setup:
  • Have user [UserA] logged in who has the "Avatar Sessions" widget on their desktop.
  • Have another user [UserB] who has not logged in yet.
  • Have a third user [UserC] who has a ODBC connection created to connect to the testing system, that is configured using his userID and password
  • [UserC] has a report created [ReportA], to display data in a table in the testing system, using his ODBC connection
Steps
  1. Log in as [UserA] and note the date and time of login
  2. Navigate to the "Avatar Sessions" widget
  3. Refresh the widget and and note the current date and time
  4. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA].
  5. If this is a Netsmart hosted system
  6. Validate the "Login Date" and "Login Time" are consistent with time a date noted in step 1
  7. Validate the "Last Activity" date and time are consistent with the date and time noted in step 2a
  8. Note the current number of connections stated in the "# of Connections" column
  9. Launch any form
  10. Refresh the the "Avatar Sessions" widget
  11. Validate the number of connections in the "# of Connections" column has incremented by 1
  12. Close the form just launched
  13. Validate the number of connections in the "# of Connections" column has decreased by 1
  14. Log in as [UserB] and note the current date and time.
  15. Navigate to the "Avatar Sessions" widget and refresh the widget
  16. Validate a row for both [UserA] and [UserB] are listed in the widget
  17. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA]
  18. Validate the "UserID" column of the widget includes the expected user ID associated with [UserB]
  19. Repeat step 2b for [UserB]
  20. Validate results are as expected
  21. As [UserC]
  22. Open [ReportA]
  23. Click to generate the report. Note the date and time
  24. Validate the report launches successfully
  25. As [UserA]
  26. Click the 'Refresh' button on the "Avatar Sessions" widget
  27. Validate a row for both [UserA] and [UserB] are listed in the widget
  28. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserA]
  29. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserB]
  30. Validate a new row is present in the widget for [UserC]
  31. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserC].
  32. Note the number of connections in the "# of Connections" column
  33. As [UserC], close [ReportA]
  34. As [UserA]
  35. Click the 'Refresh' button on the "Avatar Sessions" widget
  36. Validate the row for [UserC] is no longer present in the widget, as expected
  37. Validate the rows for [UserA] and [UserB] are still present
  38. As [UserB]
  39. Log out of Avatar
  40. As [UserA]
  41. Click the 'Refresh' button on the "Avatar Sessions" widget
  42. Validate the row for [UserB] is no longer present in the widget, as expected
  43. Validate the row for [UserA] is present, as expected
Data reports/queries
Scenario 1: Validate data results from reports generated using an ODBC login connection
Specific Setup:
  • Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
  • Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
  • Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
  • Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
  • In form "Import Reports"
  • Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
  • [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
  • Have three modeled forms available for testing
  • [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
  • [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
  • [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
  • [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
  1. In application "Crystal Reports"
  2. Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
  3. Click to process the report
  4. Validate the report display all data as expected
  5. Close the report
  6. Repeat step 1a again to regenerate the report
  7. Validate results are as expected
  8. Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
  9. Click to process the report
  10. Validate the report display all data as expected
  11. Close the report
  12. Repeat step 1c again to regenerate the report
  13. Validate results are as expected
  14. Log in Avatar
  15. Search for and open [ReportC], the report imported to run from a menu
  16. Validate when selected form the menu, the report launches successfully
  17. Validate the report display all data as expected
  18. Close the report
  19. Repeat step 2a again to regenerate the report
  20. Validate results are as expected
  21. Close the report
  22. Search for and open [ReportD], the "Report Definition" report
  23. Populate any prompts on the form
  24. Click to process the report
  25. Validate the report display all data as expected
  26. Close the report
  27. Repeat step 2b again to regenerate the report
  28. Validate results are as expected
  29. Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
  30. Populate the form
  31. Submit the form as "Final"
  32. Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
  33. Approve/ route and submit the document
  34. Validate submission is successful
  35. Repeat step 2c again
  36. Validate results are as expected
  37. Search for and open [FormB], the form configured with a post filing report
  38. Populate the fields on the form
  39. Submit the form
  40. Validate the form files successfully
  41. Validate the post filing report [ReportF] is launched
  42. Validate the data is displayed as expected
  43. Repeat step 2e again to regenerate the report
  44. Validate results are as expected
  45. Search for and open [FormC], the form configured with the command button report
  46. Populate the fields on the form
  47. Navigate to the "Command Button" field
  48. Click the field to launch the report
  49. Validate [ReportG] is launched
  50. Validate data is displayed as expected
  51. Submit the form
  52. Validate the form submits successfully
  53. Validate the command button report [ReportF] is launched
  54. Validate the data is displayed as expected
  55. Submit the form
  56. Validate the form files successfully
  57. Repeat step 2g again to regenerate the report
  58. Validate results are as expected
Topics
• Forms Designer • Widgets • Import Reports • Query/Reporting • SQL Data Access