Skip to main content

RADplus 2023 Monthly Release 2023.02.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 52 Summary | Details
Customization Pack - installation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Print Error Log (PM)
Scenario 1: Load & Verify Successful Customization Pack Installation
Specific Setup:
  • Customization pack [TestCustPack] is available for installation in the system
Steps
  1. Internal Testing Only
Namespace validation and correction process
Scenario 1: Application Namespace Connection Validation process - (Internal) Validations
Steps
  1. Internal Testing Only
Scenario 2: Application Namespace Connection Validation
Specific Setup:
  1. Have a system with one or more child namespaces. For example: "PM" or "CWS" namespaces
  2. Have a system that the following modules installed in the system: "Avatar Data Warehouse", " Avatar CWS State Forms" or "Avatar ProviderConnect NX 2023 " and any other desired modules
Steps
  1. Open form "Applications Namespace Connection Validations"
  2. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  3. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mapping errors.
  4. Click [Process]
  5. Validate the "Application Namespace Connections Validation" report list the expected connected child applications and namespace(s)
  6. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mappings errors.
Netsmart Programmer Alerts
Scenario 1: Validate (Internal) "Programmer Alert" functionality
Steps
  1. Internal Testing Only
Topics
• Update Install • Cache • NX • Database Management
Update 59 Summary | Details
Document Routing - comments
Scenario 1: Validate "Doc Routing" workflow "Approval Comments" data in SQL table "DocR.Comments"
Specific Setup:
  • Have a system with both "PM" and "CWS" namespaces
  • Have the following forms set up on the system
  • [FormA] is "PM" form that is enabled for document routing and has prompt "Allow Comments During Approval" set to "Yes" in form "Document Routing Setup"
  • Have a report or query set up that can used to display data in the SQL table "Doc.R.Comments" pointing to the "PM" namespace [ReportA]
  • [FormB] is "CWS" form that is enabled for document routing and has prompt "Allow Comments During Approval" set to "Yes" in form "Document Routing Setup"
  • Have a report or query set up that can used to display data in the SQL table "Doc.R.Comments" pointing to the "CWS" namespace [ReportB]
  • [FormC] can be set up in either "PM" or "CWS". Is enabled for document routing and has prompt "Allow Comments During Approval" set to "Yes" in form "Document Routing Setup"
  • Have a report or query [ReportC] set up that can used to display data in the SQL table "Doc.R.Comments" pointing to the namespace the [FormC] was created in
  • [UserA] and [UserB] are staff members.
  • In form "User Definition" [UserA] has permissions set to be a to be a "Co-signer" for other staff members
  • Log in as [UserA]
Steps
  1. Open [FormA]
  2. Select a client [TestClient]
  3. Populate the desired fields on the form
  4. File the form as "Final"
  5. At the "Route To" screen
  6. Add [UserB] as an approver
  7. Submit the form
  8. Validate submission is successful
  9. Repeat step 1 for forms for [FormB]
  10. Validate results are as expected
  11. Log out as [UserA]
  12. Log in as [UserB]
  13. Navigate to the "My To Do's" widget and locate the To Do sent in step 1 for [FormA]
  14. Click to [Review]
  15. At the "Document Preview" screen, validate the document contents are as expected
  16. Click [Accept]
  17. Click [Sign]
  18. At the "Approval Comments" dialog, enter the desired comments
  19. Click [OK]
  20. Validate submission is successful
  21. In the "My To Do's" widget, locate the To Do sent in step 2 for [FormB]
  22. Click to [Review]
  23. At the "Document Preview" screen, validate the document contents are as expected
  24. Click [Accept]
  25. Click [Sign]
  26. At the "Approval Comments" dialog, enter the desired comments
  27. Click [OK]
  28. Validate submission is successful
  29. Run [ReportA] to display data in the SQL table "Doc.R.Comments" in the "PM" namespace
  30. Validate a row is displayed for [TestClient] for the To Do approved in sent in step 1
  31. Validate the "approved_user" field reflects [UserB] who approved the To Do in step 5
  32. Validate the "Appoved_Comment" field reflects the comment entered in step 5 by [UserB]
  33. Run [ReportB] to display data in the SQL table "Doc.R.Comments" in the "CWS" namespace
  34. Validate a row is displayed for [TestClient] for the To Do approved in sent in step 2
  35. Validate the "approved_user" field reflects [UserB] who approved the To Do in step 6
  36. Validate the "Appoved_Comment" field reflects the comment entered in step 5 by [UserB]
  37. Log out as [UserB]
  38. Log in as [UserA]
  39. Open [FormC]
  40. Select a client [TestClient]
  41. Populate the desired fields on the form
  42. File the form as" Final"
  43. At the "Route To" screen
  44. Add [UserB] as an approver
  45. Submit the form
  46. Validate submission is successful
  47. Navigate the "My To Do's widget
  48. Click on the "Sign" tab
  49. In the "Staff" search field, search for [UserB]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  50. Validate the To Do sent to [UserB] is found, select the To Do to review it
  51. Click [Accept]
  52. At the "Approval Comments" dialog, populate the text field with a desired comment
  53. Click [OK]
  54. Click [Sign All]
  55. Validate the To Do is removed from the To Do list
  56. Then right a way, in the "Staff" search field, search for [UserA].
  57. Locate the To Do for [FormC]
  58. Click [Review]
  59. Click [Accept]
  60. At the "Approval Comments" dialog, populate the text field with a desired comment
  61. Click [OK]
  62. Validate the To Do is removed from the To Do list successfully
  63. Run [ReportC] to display data in the SQL table "Doc.R.Comments"
  64. Validate there are two rows displayed for [TestClient], for the To Do sent to [UserB] in step 11
  65. For the first row,
  66. Validate the "approved_user" field reflects [UserA] who signed the To Do sent to [UserB] in step 11
  67. Validate the "AppovedComment" field reflects the comment entered in step 12b by [UserA]
  68. For the second row
  69. Validate the "approved_user" field reflects [UserA] who approved the To Do that was sent to themselves in step 11
  70. Validate the "AppovedComment" field reflects the comment entered in step 12b by [UserA]
"DocR.comments" - To Do approvals
Internal Test Only
Topics
• Document Routing • My To Do's • Approval Comments
Update 60 Summary | Details
Support for the 'Alternate Lookup By Room' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Client Ledger
Scenario 1: Validate the 'Alternate Lookup By Room' registry setting
Specific Setup:
  • Two clients (Client A & Client B) must be admitted into inpatient episodes in the same room (Room A).
  • The registry setting "Include Active Room Number with Client" is set to "1".
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Alternate Lookup By Room" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting' field contains: Avatar PM->Client Information->Client Lookup->->->Alternate Lookup By Room.
  5. Validate the 'Registry Setting Detail' field contains: Selecting 'Y' will add an alternate search for clients by room number in the My Clients widget and Client Search. This must be an exact match and will look at the 'Include Active Room Number With Client Name' registry setting to potentially parse the room number. Select 'N' to disable this functionality.
  6. Enter "Y" in the 'Registry Setting Value' field.
  7. Click [Submit] and close the form.
  8. Search for "Room A" in the 'Search Clients' field.
  9. Validate both "Client A" and "Client B" are displayed.
  10. Access the 'Progress Notes (Group and Individual)' form.
  11. Enter "Room A" in the 'Select Client' field.
  12. Validate "Client A" and "Client B" are displayed.
  13. Close the form.
  14. Access the 'Client Ledger' form.
  15. Enter "Room A" in the 'Client ID' field.
  16. Validate "Client A" and "Client B" are displayed.
  17. Close the form.
  18. Access the 'Account Registration' form.
  19. Enter "Room A" in the 'Select Client' dialog.
  20. Validate "Client A" and "Client B" are displayed.
  21. Click [Cancel].
  22. Access the 'Service Authorization' form.
  23. Enter "Room A" in the 'Select Client' dialog.
  24. Validate "Client A" and "Client B" are displayed.
  25. Click [Cancel].
  26. Access the 'Registry Settings' form.
  27. Enter "Alternate Lookup By Room" in the 'Limit Registry Settings to the Following Search Criteria' field.
  28. Click [View Registry Settings].
  29. Validate the 'Registry Setting' field contains: Avatar PM->Client Information->Client Lookup->->->Alternate Lookup By Room.
  30. Enter "N" in the 'Registry Setting Value' field.
  31. Click [Submit] and close the form.
  32. Search for "Room A" in the 'Search Clients' field.
  33. Validate "Client A" and "Client B" are not displayed.
  34. Access the 'Progress Notes (Group and Individual)' form.
  35. Enter "Room A" in the 'Select Client' field.
  36. Validate "Client A" and "Client B" are not displayed.
  37. Close the form.
  38. Access the 'Client Ledger' form.
  39. Enter "Room A" in the 'Client ID' field.
  40. Validate "Client A" and "Client B" are not displayed.
  41. Close the form.
  42. Access the 'Account Registration' form.
  43. Enter "Room A" in the 'Select Client' dialog.
  44. Validate "Client A" and "Client B" are not displayed.
  45. Click [Cancel].
  46. Access the 'Service Authorization' form.
  47. Enter "Room A" in the 'Select Client' dialog.
  48. Validate "Client A" and "Client B" are not displayed.
  49. Click [Cancel].
Client Lookups
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Final to Draft Override (CWS)
  • Practitioner Enrollment
Scenario 1: Final to Draft Override - Form Validations
Specific Setup:
  • A modeled form is defined with the 'Draft/Final' prompt (Form A).
  • A client is enrolled in an existing episode (Client A).
  • A practitioner is defined with credentials on file (Practitioner A).
  • "Client A" and "Practitioner A" must have the same ID numbers.
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Submit].
  5. Access the 'Final to Draft Override' form.
  6. Select "Form A" in the 'Form' field.
  7. Select "Client A" in the 'Entity Lookup' field.
  8. Validate "Client A" does not display with practitioner credentials.
  9. Click [Select Row].
  10. Select the finalized record filed in the previous steps and click [OK].
  11. Validate the 'Row Contents' field contains the values entered in the previous steps.
  12. Enter the desired value in the 'Override Reason' field.
  13. Click [Submit].
  14. Select "Client A" and access "Form A".
  15. Select the record filed in the previous steps and click [Edit].
  16. Validate "Draft" is now selected in the 'Draft/Final' field.
  17. Close the form.
Topics
• Registry Settings • Client Search • Final to Draft Override
Update 64 Summary | Details
Envelope Import - support for Multiple Envelope Export
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Import (CWS)
  • Form Deletion (PM)
  • Table Deletion (PM)
  • Envelope Deletion (PM)
  • Form Deletion (CWS)
  • Table Deletion (CWS)
  • Envelope Deletion (CWS)
  • Modeled Form Doc Routing
  • Envelope Export (PM)
  • ModeledForm
  • User Definition
  • Multiple Envelope Export
  • Envelope Import (MSO)
  • Envelope Definition (MSO)
Scenario 1: "Envelope Import" - Validate importing envelope(s) containing modeled form(s) in parent and child namespaces
Specific Setup:
  • Have an envelope "Envelope A", exported from the parent namespace. For example, the "PM" Namespace.
  • Have an envelope "Envelope B", exported from a child namespace. For example, the "CWS" namespace.
  • Have another envelope "Envelope C", exported from any namespace that contains a modeled form that is enabled for document routing.
  • Have an envelope "Envelope D", exported from a child namespace. For example, the "MSO" namespace.
Steps
  1. Open the "Envelope Import" form from the PM menu.
  2. Import "Envelope A" from setup.
  3. Create a new envelope.
  4. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  5. Import file.
  6. Refresh Menus.
  7. Open the form associated with the import.
  8. File the form.
  9. Validate it files successfully.
  10. Open the "Envelope Import" form from the CWS menu.
  11. Import "Envelope B" from setup.
  12. Create a new envelope.
  13. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  14. Import file.
  15. Refresh Menus.
  16. Open the form associated with the import.
  17. File the form.
  18. Validate it files successfully.
  19. Open the "Envelope Import" form from the CWS menu.
  20. Import "Envelope C" from setup.
  21. Create a new envelope.
  22. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  23. Import file.
  24. Refresh Menus.
  25. Open the form associated with the import.
  26. File the form.
  27. Validate it files successfully.
  28. Open the "Envelope Import" form from the MSO menu.
  29. Import "Envelope D" from setup.
  30. Create a new envelope.
  31. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  32. Import file.
  33. Refresh Menus.
  34. Open the form associated with the import.
  35. File the form.
  36. Validate it files successfully.
Scenario 2: Envelope Export - validations
Specific Setup:
  • Have an existing Modeled form [FormA] that exists in [EnvelopeA].
Steps
  1. Open form "Envelope Definition".
  2. Select [EnvelopeA].
  3. Note the value in the "Envelope Version Number" field, for example "1.01".
  4. Close the form.
  5. Open form "Envelope Export".
  6. Select [EnvelopeA].
  7. Click [Begin Export].
  8. In the "File Explorer" dialog, select a folder location in the "Save In" field to save the export file.
  9. In the "File_Name" field, validate that the file name populated includes the name of [ReportA], appended by a "V" followed by the "Report Version Number" value noted in step 1 and the file extension. For example, "NetsmartExportModeledFormV1_01.TXT".
  10. Click [Save].
  11. Close the form.
  12. Open file "Envelope Import".
  13. Click [Select Envelope Import File]
  14. In the "File Explorer" dialog, navigate to the location of the export file.
  15. Select the file and click [Open].
  16. Select the "Overwrite Existing" radio button.
  17. Click [Begin Import Scan].
  18. Click [Begin Import].
  19. At the "Import Complete" dialog, click [OK].
  20. Close the form.
  21. At the Home View, search for [FormA] and open the form.
  22. Populate the desired fields on the form.
  23. Submit the form.
  24. Validate the form files successfully.
Scenario 3: Multiple Envelope Export - Form Validation
Specific Setup:
  • Using the "User Definition" form:
  • Give the user access to the "Multiple Envelope Export" form.
  • This form is available under the "Modeling" menu in the parent and child namespaces.
  • File the form.
  • Must have envelopes available for export.
Steps
  1. Open the "Multiple Envelope Export" in the parent or child namespace.
  2. Select several envelopes to export.
  3. Open the "Envelope Import" in the parent or child namespace selected above.
  4. Import the envelope creating a new envelope if it doesn't exist already or overwriting an existing envelope.
  5. Open the "Envelope Definition" form in the parent or child namespace selected above.
  6. Validate the envelope imported.
Multiple Envelope Export - Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Import (CWS)
  • Form Deletion (PM)
  • Table Deletion (PM)
  • Envelope Deletion (PM)
  • Form Deletion (CWS)
  • Table Deletion (CWS)
  • Envelope Deletion (CWS)
  • Modeled Form Doc Routing
  • Envelope Export (PM)
  • ModeledForm
  • User Definition
  • Multiple Envelope Export
  • Envelope Import (MSO)
  • Envelope Definition (MSO)
Scenario 1: "Envelope Import" - Validate importing envelope(s) containing modeled form(s) in parent and child namespaces
Specific Setup:
  • Have an envelope "Envelope A", exported from the parent namespace. For example, the "PM" Namespace.
  • Have an envelope "Envelope B", exported from a child namespace. For example, the "CWS" namespace.
  • Have another envelope "Envelope C", exported from any namespace that contains a modeled form that is enabled for document routing.
  • Have an envelope "Envelope D", exported from a child namespace. For example, the "MSO" namespace.
Steps
  1. Open the "Envelope Import" form from the PM menu.
  2. Import "Envelope A" from setup.
  3. Create a new envelope.
  4. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  5. Import file.
  6. Refresh Menus.
  7. Open the form associated with the import.
  8. File the form.
  9. Validate it files successfully.
  10. Open the "Envelope Import" form from the CWS menu.
  11. Import "Envelope B" from setup.
  12. Create a new envelope.
  13. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  14. Import file.
  15. Refresh Menus.
  16. Open the form associated with the import.
  17. File the form.
  18. Validate it files successfully.
  19. Open the "Envelope Import" form from the CWS menu.
  20. Import "Envelope C" from setup.
  21. Create a new envelope.
  22. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  23. Import file.
  24. Refresh Menus.
  25. Open the form associated with the import.
  26. File the form.
  27. Validate it files successfully.
  28. Open the "Envelope Import" form from the MSO menu.
  29. Import "Envelope D" from setup.
  30. Create a new envelope.
  31. Click "Yes" in "Load Un-Locked Dictionary Entries" and "Load Locked Dictionary Entries".
  32. Import file.
  33. Refresh Menus.
  34. Open the form associated with the import.
  35. File the form.
  36. Validate it files successfully.
Scenario 2: Envelope Export - validations
Specific Setup:
  • Have an existing Modeled form [FormA] that exists in [EnvelopeA].
Steps
  1. Open form "Envelope Definition".
  2. Select [EnvelopeA].
  3. Note the value in the "Envelope Version Number" field, for example "1.01".
  4. Close the form.
  5. Open form "Envelope Export".
  6. Select [EnvelopeA].
  7. Click [Begin Export].
  8. In the "File Explorer" dialog, select a folder location in the "Save In" field to save the export file.
  9. In the "File_Name" field, validate that the file name populated includes the name of [ReportA], appended by a "V" followed by the "Report Version Number" value noted in step 1 and the file extension. For example, "NetsmartExportModeledFormV1_01.TXT".
  10. Click [Save].
  11. Close the form.
  12. Open file "Envelope Import".
  13. Click [Select Envelope Import File]
  14. In the "File Explorer" dialog, navigate to the location of the export file.
  15. Select the file and click [Open].
  16. Select the "Overwrite Existing" radio button.
  17. Click [Begin Import Scan].
  18. Click [Begin Import].
  19. At the "Import Complete" dialog, click [OK].
  20. Close the form.
  21. At the Home View, search for [FormA] and open the form.
  22. Populate the desired fields on the form.
  23. Submit the form.
  24. Validate the form files successfully.
Scenario 3: Multiple Envelope Export - Form Validation
Specific Setup:
  • Using the "User Definition" form:
  • Give the user access to the "Multiple Envelope Export" form.
  • This form is available under the "Modeling" menu in the parent and child namespaces.
  • File the form.
  • Must have envelopes available for export.
Steps
  1. Open the "Multiple Envelope Export" in the parent or child namespace.
  2. Select several envelopes to export.
  3. Open the "Envelope Import" in the parent or child namespace selected above.
  4. Import the envelope creating a new envelope if it doesn't exist already or overwriting an existing envelope.
  5. Open the "Envelope Definition" form in the parent or child namespace selected above.
  6. Validate the envelope imported.
Envelope Export - exporting aliased dictionaries
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Definition (MSO)
  • Table Definition (MSO)
  • Form Definition (MSO)
  • Envelope Export (MSO)
  • Envelope Import (MSO)
Scenario 1: Table Definition - Export a single response dictionary item that maps to a different entity
Specific Setup:
  • Using "Envelope Definition":
  • Create a new envelope form in the child or parent namespace.
  • Allow the envelope to be exportable.
  • Using "Table Definition" form:
  • Navigate to the "Column Definition" section.
  • Add desired fields.
  • Add a Single Response Dictionary field that is mapped to another database.
  • Using "Form Definition" form:
  • Create a new form utilizing all the fields created under the "Table Definition".
Steps
  1. Open "Envelope Export".
  2. Export the envelope you created in setup.
  3. Log into another test system.
  4. Open "Envelope Import".
  5. Import the envelope you just exported.
  6. Open "Envelope Definition".
  7. Validate the envelope you just imported exists.
  8. Open the form that was imported.
  9. Populate with data.
  10. File the form.
Topics
• Modeling • Envelope Import • NX • Envelope Definition • Envelope Export
Update 66 Summary | Details
Client Picture - Table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Import Client Picture (PM)
Scenario 1: Validate data in the "SYSTEM.RADplus_client_picture" table
Specific Setup:
  • Have a report or query [TestReport]" created to display data in the ""SYSTEM.RADplus_client_picture"' table
  • Have client [ClientA] who does not have a picture image uploaded yet in the system
  • Have an image [TestImageA] on the system available for import for [ClientA]
  • Have client [ClientB] who already has a picture image uploaded [TestImageB]
  • Have an image [TestImageC] on the system available for import to replace the current image for [ClientB]
  • [TestUser] has access to form "Import Client Picture"
  • Log in as [TestUser]
Steps
  1. Access the 'Import Client Picture' form.
  2. Select [ClientA] in the 'Client' field.
  3. Right click in the 'Picture' field.
  4. Click [Acquire Image].
  5. Navigate to [TestImageA] and select the image
  6. Validate the image in the 'Picture' field is displayed as expected
  7. Submit the form. [Note the current date and time]
  8. Validate the form files successfully
  9. Access [TestReport] and generate the report or query
  10. Locate the row just submitted for [ClientA]
  11. Validate the "PATID" field value for [ClientA], is populated as expected
  12. Validate the 'data_entry_date" field value reflects the date noted in step 1
  13. Validate the 'data_entry_time" field value reflects the time noted in step 1
  14. If "UTC" time is enabled on the system:
  15. Validate the 'data_entry_utc" field value reflects the date and time noted in step 1 but in "UTC" time and date format. (For example, if the time zone is "Eastern" and the date and time in step 1 was "6/22/23" at "1:52 PM", the value would be display as "6/22/2023 5:52:16PM")
  16. Validate the "data_entry_timezone_info_all" field value is displayed as expected, based on the time zone. (For example, if the time zone is "Eastern", the value displayed would be "EDT;Eastern Daylight Time;-0400")
  17. Validate the 'data_entry_by_login' field value is [TestUser]
  18. Validate the "picture" field is populated with [TestImageA], as expected
  19. Access the 'Import Client Picture' form.
  20. Select [ClientB] in the 'Client' field.
  21. Validate [TestImageB], is displayed as expected
  22. Right click on the image in the 'Picture' field.
  23. Click [Acquire Image].
  24. Navigate to [TestImageC] and select the image
  25. Validate that image is now displayed as expected
  26. Submit the form. [Note the current date and time]
  27. Validate the form files successfully
  28. Access [TestReport] and generate the report or query
  29. Locate the row just submitted for [ClientB]
  30. Validate the "PATID" column for [ClienB], is populated as expected
  31. Validate the 'data_entry_date" field value reflects the date noted in step 3
  32. Validate the 'data_entry_time" field value reflects the time noted in step 3
  33. When "UTC" time is enabled on the system:
  34. Validate the 'data_entry_utc" field value reflects the date and time noted in step 3 in "UTC" time format
  35. Validate the "data_entry_timezone_info_all" field values displayed as expected based on the time zone.
  36. Validate the 'data_entry_by_login' field value is [TestUser]
  37. Validate the "picture" field is populated with [TestImageC], as expected
Topics
• SQL Data Access • NX
Update 69 Summary | Details
Multi-row SQL Widgets - Event log entries
Scenario 1: SQL Widget ('Multiple Row SQL' Type) - Validate entries in the "SYSTEM.radplus_event_log" table
Specific Setup:
  • Have a report or query to display data in the "SYSTEM.RADplus_event_log" table [TestReport]
  • In form "Widget Definition" have a "Multiple Row SQL" type widget created [MultWidget] based on a table. For this test the "cw_hist_client_allergies" filed in form "Client Allergies and Hypersensitivities", is used
  • Have a client [ClientA] with just one allergy filed in form "Client Allergies and Hypersensitivities"
  • Have another client [ClientB] with two more allergies filed in form "Client Allergies and Hypersensitivities"
  • Have [MultWidget] placed on a user's home view or additional console view
Steps
  1. At the home view, select [ClientA], the client with just one entry filed in the table
  2. Navigate to location of widget [MultWidget]
  3. Click the "Refresh" button in the widget (Note the current date and time)
  4. Validate results are displayed as expected. For this test, just one row is displayed as expected for the "Allergies" on file for [ClientA]
  5. Run the [TestReport], created to display data in the "SYSTEM.RADplus_event_log" table
  6. Validate there are only two event log rows displayed for the transaction to step 1a:
  7. One entry row is displayed for accessing [ClientA]
  8. Validate the 'event_date' and 'event-time' are consistent with the date time noted in step 1a
  9. Second row entry is for refreshing the widget with the loaded data for [ClientA]
  10. Validate the 'event_date' and 'event-time' are consistent with the date time noted in step 1a
  11. Click to refresh the widget again
  12. Repeat steps 1a and 1b
  13. Validate results are as expected
  14. At the home view, select [ClientB], the client with multiple entries filed in the table
  15. Navigate to location of widget [MultWidget]
  16. Click the "Refresh" button in the widget (Note the current date and time)
  17. Validate results are displayed as expected. For this test, just one row is displayed as expected for the "Allergies" on file for [ClientB]
  18. Run the [TestReport], created to display data in the "SYSTEM.RADplus_event_log" table
  19. Validate there are still only two event log rows displayed for the transaction to step 2a, as expected. (Note: only two event log entries are expected, even when multiple entire are displayed in the widget)
  20. One entry row is displayed for accessing [ClientB]
  21. Validate the 'event_date' and 'event-time' are consistent with the date time noted in step 2a
  22. Second row entry is for refreshing the widget with the loaded data for [ClientB]
  23. Validate the 'event_date' and 'event-time' are consistent with the date time noted in step 2a
  24. Click to refresh the widget again
  25. Repeat steps 2a and 2b
  26. Validate results are as expected
Topics
• Admission • Audit Log
Update 83 Summary | Details
View Definition - view deletion
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
Scenario 1: NX "View Definition" - Validate 'myDay', 'Client Dashboard' and "Additional myDayViews" load successfully after an assigned "View" is deleted
Specific Setup:
  • Have or create two views in form "View Definition".
  • [TestViewA] is set as a home view
  • [TestViewB] is set as a chart view
  • Have four existing users set up in form "User Definition" that are either assigned to one or more roles or not assigned to a role [UserA], [UserB], [UserC] and [UserD].
  • In form 'NX View Definition'
  • Each user has been set up with a "myDay" and "Client Dashboard" and "Additional myDay Views", that don't include [TestViewA] and [TestViewB] as a selected view
  • Logged in user has access to "NX View Definition" and "View Definition"
Steps
  1. Open 'NX View Definition' and select [UserA] in the "Select User" field
  2. Change their current 'myDay' to the view [TestViewA]
  3. Click [File] to submit the changes
  4. In the "Select User" field select [UserB]
  5. Change their current 'Client Dashboard' view to [TestViewB]
  6. Click [File] to submit the changes
  7. In the "Select User" field select [UserC]
  8. Change their 'myDay' to the view [TestViewA]
  9. Change their 'Client Dashboard' to the view [TestViewB]
  10. Click [File] to submit the changes
  11. In the "Select User" field select [UserD]
  12. Leave the current values selected in the 'myDay' and 'Client Dashboard' fields
  13. Click "Additional myDay Views"
  14. Select [TestViewA] and any other desired views
  15. Click [File] to submit the changes
  16. Open "View Definition"
  17. Click "Select View" and select [TestViewA]
  18. Click [Delete View]
  19. Submit the form
  20. Validate the form files successfully
  21. Click "Select View" and select [TestViewB]
  22. Click [Delete View]
  23. Submit the form
  24. Validate the form files successfully
  25. Log out as the current logged in user
  26. Log in as [UserA]
  27. Validate their "myDay" view [TestViewA] has not loaded and the view has defaulted to the "Netsmart Default" view as expected, as their assigned view [TestViewA] had been deleted. (Note: the Netsmart default view has just the "Did You Know?" widget and "Message Center" widget on the view)
  28. Select any client and click "Open Dashboard" link next to their name
  29. Validate their assigned "Client Dashboard" view loads as expected
  30. Close the client dashboard
  31. Click back to the "myDay "view
  32. Validated any "Additional myDay Views" assigned, are displayed across the top of the page as expected
  33. Click on any of the additional views
  34. Validate the views loads as expected
  35. Log out as [UserA]
  36. Log in as [UserB]
  37. Validate their assigned "myDay" view has loaded as expected
  38. Select any client and click "Open Dashboard" link next to their name
  39. Validate their assigned "Client Dashboard" view [TestViewB] is not displayed and the view has defaulted to the "Netsmart Default" dashboard view as expected. [Note: the Netsmart default dashboard view only contains the "My To Do's" widget]
  40. Close the client dashboard
  41. Click back to the "myDay "view
  42. Validated any "Additional myDay Views" assigned, are displayed across the top of the page as expected
  43. Click on any of the additional views
  44. Validate the views loads as expected
  45. Log out as [UserB]
  46. Log in as [UserC]
  47. Validate their "myDay" view [TestViewA] has not loaded and the view has defaulted to the "Netsmart Default" view as expected, as their assigned view [TestViewA] had been deleted.
  48. Select any client and click ""Open Dashboard" link next to their name
  49. Validate their assigned "Client Dashboard" view [TestViewB] is not displayed and the view has defaulted to the "Netsmart Default" dashboard view as expected
  50. Close the client dashboard
  51. Click back to the "myDay "view
  52. Validated any "Additional myDay Views" assigned, are displayed across the top of the page as expected
  53. Click on any of the additional views
  54. Validate the views loads as expected
  55. Log out as [UserC]
  56. Log in as [UserD]
  57. Validate their assigned "myDay" view has loaded as expected
  58. Select any client in the "My Clients" widget and click ""Open Dashboard" link next to their name
  59. Validate their assigned "Client Dashboard" loads as expected
  60. Select any client and click "Open Dashboard" link next to their name
  61. Validate their assigned "Client Dashboard" loads as expected
  62. Click back to the "myDay" view.
  63. Validate their assigned "Additional myDay Views" are displayed as expected except for [TestViewA], as that view was deleted
  64. Click on any of the additional views
  65. Validate the views loads as expected
Topics
• NX • NX View Definition
 

RADplus_2023_Monthly_Release_2023.02.01_Details.csv