Skip to main content

RADplus 2023 Monthly Release 2023.01.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 4 Summary | Details
Avatar Data Warehouse - IRIS
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SQL Query/Reporting Tool
Scenario 1: Data Warehouse Processing (IRIS)- Table row validations
Specific Setup:
  • Have Avatar database server set up that is running on "IRIS" based system that's configured with the parent namespace and one or more child namespaces
  • Have a server installed with the latest released version of "Avatar Data Warehouse Middleware" for "IRIS".
  • Netsmart has been configured the middleware to initiate the data warehouse process
  • Have a "Microsoft SQL Server" where table data processed by the data warehouse process will be stored
  • Have a database program that can query the data in the tables stored on the data warehouse server. For example program "DBeaver Universal Database Manager" or "Crystal Reports"
  • In form "User Definition", a user had been created [AvatarDW] as the designated data warehouse user.
  • [AvatarDW] has been assigned permissions to tables determined to be included in the data warehouse process, that includes tables selected in parent namespace and in any child namespaces
  • In form "Data Warehouse Transient Comparison Configuration", the designated data warehouse user [AvatarDW] has the designated tables selected in previous selected in "Mark Tables for Full Load" section
  • Have a report or query that will display data in the "SYSTEM.dss_inc_error_log" table
  • Have a report or query that will display data in the "SYSTEM.dss_inc_full_load_history" table
  • Netsmart has run "Data Warehouse Middleware" process on the middleware server, in the parent namespace and each child namespace
Steps
  1. Generate the report to display data in the "SYSTEM.dss_inc_error_log" table
  2. Validate there are no results indicating the data warehouse middleware process has completed successfully
  3. Generate the report to display data in the "SYSTEM.dss_inc_full_load_history" table
  4. Validate the expected data rows are present on the report for the parent and child namespace tables selected for data warehouse processing in the setup
  5. Validate each row has "Insert" populated in the "Type" field
  6. Open the program to query data on the 'SQL' database server and connect to the database
  7. Run at query to display rows filed the "dss_completion_flag" table.
  8. Validate the expected tables are present on the results, for the parent and child namespace tables selected for data warehouse processing, in the setup
  9. Validate the "dss_status" field for each row is set to "1", indicating the table was loaded successfully
  10. From the database "Table" tree list, select tables form the parent and child namespaces
  11. Click to display the rows in the table
  12. Validate all data rows are displayed, as expected
Topics
• Data Warehouse
Update 14 Summary | Details
Console Widgets - Military Time
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Console Widget Configuration (PM)
  • Console Widget Configuration (CWS)
  • Patient/Family Teaching
Scenario 1: Console Widgets - Validate the 'Enable Military Time' registry setting for user modeled forms
Specific Setup:
  • The 'Enable Military Time' registry setting must be enabled. Please note: this must be done by a Netsmart Associate.
  • A user modeled form is defined with a 'Time' field (Form A).
  • A console widget must be configured for "Form A" in the 'Console Widget Configuration' form (Widget A).
  • A view must be defined with "Widget A" and the 'Console Widget Viewer' (View A).
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access "Form A".
  2. Enter the desired time in the 'Time' field.
  3. Validate the time displays in military time format.
  4. Populate all other required and desired fields.
  5. Click [Submit] and close the form.
  6. Select "Client A" and navigate to "View A".
  7. Validate "Widget A" contains the record filed in the previous steps.
  8. Validate the 'Time' field displays in military time.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the data filed in the previous steps.
  11. Validate the 'Time' field displays in military time.
  12. Click [Close All].
Topics
• Console Widget • Modeling • Console Widget Configuration
Update 16 Summary | Details
Results To Review To Do List - Removing ToDos
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry Console
  • Orders This Episode
  • Results Entry
  • Notifications Setup
  • Order Code Setup
  • Admission
  • Order Entry Console - Interactions dialog
  • Results Importing
  • Review To Do Item
Scenario 1: Validate results in the Lab Results widget
Steps
  1. Open the "Results Entry" form.
  2. File a header and then file details to enter a lab order for CBC.
  3. Validate you can see the order in the "Lab Results" Widget.
Scenario 2: Lab Result ToDos
Specific Setup:
  • Using the "Notifications Setup" form:
  • Enter a notification for the "Results" notification type.
  • Set the "Notification Text" to "<FULL_NAME><PATID>.
  • Enter a notification for the "Results (Abnormal)" notification type.
  • Set the "Notification Text" to "<FULL_NAME><PATID> has new lab results (Abnormal)".
  • Using the "Order Code Setup" form:
  • Set up a lab order code called "Comprehensive Metabolic Panel (CMP)".
  • Set up a lab order code called "Lipid Panel".
  • Admit or select a test client into any episode.
  • "Order Entry Console" must be set up on the user's homeview or associated home view.
Steps
  1. Using the "Order Entry Console", enter a lab order for CMP.
  2. Complete the order, add it to the scratchpad and Sign the order.
  3. Note the order number.
  4. User the "Order Entry Console", enter a lab order for LIPID.
  5. Complete the order, add it to the scratchpad and Sign the order.
  6. Note the order number.
  7. Using the data from the orders entered into the "Order Entry Console", mockup an HL7 import file.
  8. Import the file using the "Results Importing" file.
  9. Results ToDos will be generated for the 2 orders included in the mocked up import file.
  10. Navigate to the "TodDo's" Widget.
  11. Mark the Results ToDo's as reviewed.
  12. Note the ToDo's are removed from the ToDo Widget.
Topics
• Widgets • Results • NX
Update 20 Summary | Details
Team File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Team File Import
  • Team Definition
Scenario 1: Team Definition Import - Validations
Specific Setup:
  • Have a "Team Definition" import file that contains the "Team Finalizer" field populated [ImportA]. (Make a note of the "Team Description" and the user set in the file as the finalizer)
  • Have a "Team Definition" import file that does not contain the "Team Finalizer" field populated [ImportB]. (Make a note of the "Team Description" set in the file)
  • Have a report created to display data in the "SYSTEM.RADPlus_teams" table
Steps
  1. Open form "Team File Import"
  2. Click [Select Import File]
  3. Navigate to the location of [ImportA] and select the file
  4. Validate the "Team Import File Scan Results" field indicates "No errors detected in import file."
  5. Close the form
  6. Open form "Team Definition"
  7. Click [Select Team]
  8. Validate [TeamA] is present in the list and select the team
  9. Validate the "Team ID" is populated. Note the value
  10. Validate "Team Description" is populated as expected based on the set up
  11. Validate the "Team Finalizer" field is populated as expected based on the setup
  12. Validate any other fields set in the import file are displayed as expected
  13. Close the form
  14. Open form "Team File Import"
  15. Click [Select Import File]
  16. Navigate to the location of [ImportB] and select the file
  17. Validate the "Team Import File Scan Results" field indicates "No errors detected in import file."
  18. Close the form
  19. Open form "Team Definition"
  20. Click [Select Team]
  21. Validate [TeamB] is present in the list and select the team
  22. Validate the "Team ID" is populated. Note the value
  23. Validate "Team Description" is populated as expected based on the set up
  24. Validate the "Team Finalizer" field is blank, as expected based on the setup
  25. Validate any other fields set in the import file are displayed as expected
  26. Close the form
  27. Run the report created to display data in the "SYSTEM.RADPlus_teams" table
  28. Validate a row for [TeamA] imported via [ImportA], is displayed
  29. Validate the "Team ID" is populated.with value noted in step 2a
  30. Validate "Team Description" is populated as expected based on the set up
  31. Validate the "Team Finalizer" field is populated as expected based on the setup
  32. Validate the other fields set in the import file are displayed as expected
  33. Validate a row for [TeamB] imported via [ImportB], is displayed
  34. Validate the "Team ID" is populated.with value noted in step 5a
  35. Validate "Team Description" is populated as expected based on the set up
  36. Validate the "Team Finalizer" field is blank, as expected
  37. Validate the other fields set in the import file are displayed as expected
Modeled Form - service documentation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
  • Appointment Move/Delete
Scenario 1: Modeled Form with service documentation - Submission validations when filing a form as "Draft" for an Appointment
Specific Setup:
  • Have a modeled form configured and enabled for service documentation
  • [TestClient] is enrolled in an episode and has two existing appointments [TestApptA] and [TestAppB]
  • User has access to form "Appointment Move/Delete"
Steps
  1. Access the modeled form.
  2. Select [TestClient] in the 'Select Client' dialog.
  3. Select "Existing Appointment" in the 'Data Row For' field.
  4. Select [TestAppt] in the 'Addresses Which Service/Appointment' field.
  5. Populate any other desired field
  6. Select "Draft" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate the form files successfully
  9. Access form "Appointment Move/Delete form"
  10. Select the practitioner for [TestAppt]
  11. Populate the "Appointment Start Time" and "Appointment End Time" fields s
  12. Select [TestClient] in the "Client ID" field
  13. Click the [Appointment Select] button
  14. Select the row for [TestAppt] in the "Appointment Move/Delete" selection dialog
  15. Click [OK]
  16. Click [Delete/Move Appointment] button
  17. Click [OK]
  18. Access the modeled form.
  19. Search for and select "Client A" in the 'Select Client' dialog.
  20. Select the row submitted in step 1 for edit
  21. Validate the "Draft/Final" field has "Draft" selected
  22. Validate 'Addresses Which Service/Appointment' field., no longer has [TestApptA] selected, as expected
  23. Click 'Addresses Which Service/Appointment' field
  24. Select [TestApptB]
  25. Validate the other data fields are now populated as expected, based on data filed for [TestApptB]
  26. Populate any other desired fields
  27. Submit the form
  28. Validate the form files successfully
  29. Return to the modeled form and select [TestClient]
  30. Select the row just submitted in step 3
  31. Validate all fields are populated as expected
  32. Close the form
User File Import - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User File Import
  • Order Entry User Definition
Scenario 1: 'User File Import' - "Staff" user validations
Specific Setup:
  • Have a system with "Avatar Order Entry" installed
  • Have an existing practitioner [StaffTest] who has not yet been assigned to any user in form "User Definition".
  • In form "Practitioner Enrollment", select [StaffTest] and note the "ID#" assigned to the practitioner
  • Create a "User File Import" file [ImportA], for a new user [UserA]
  • Have the "Practitioner ID" field in the file populated with the "ID#" noted in the previous step
  • Create a "User File Import" file [ImportB], for a new user [UserB]
  • Leave the "Practitioner ID" field in file unpopulated
  • Have a report created, to display data in the "SYSTEM.RADplus_Users" table
  • User has access forms "User Definition" and the "Order Entry User Definition"
Steps
  1. Open the 'User File Import' form.
  2. Click [Select User Import File].
  3. Select [ImportA]
  4. Click [Open].
  5. Validate the "Import File Scan Results" field indicates the file is ready for import
  6. Click [Process User Import File]
  7. Validate message "Import Completed" is displayed
  8. Click [OK].
  9. Close the form
  10. Open form "User Definition"
  11. Select [UserA]
  12. Navigate to the "User Caseload" section
  13. Validate the "Staff Member" field is populated with name of [StaffA] and their "ID#" (noted in the setup)
  14. Close the form
  15. Open form "Order Entry User Definition"
  16. Search for [UserA] in the "Select Order Entry User" field
  17. Validate [UserA] is found, as expected
  18. Validate the "Staff Member" field is populated with [StaffA] and their "ID#", as expected
  19. Close the form
  20. Open the 'User File Import' form.
  21. Click [Select User Import File].
  22. Select [ImportB]
  23. Click [Open].
  24. Validate the "Import File Scan Results" field indicates the file is ready for import
  25. Click [Process User Import File]
  26. Validate message "Import Completed" is displayed
  27. Click [OK].
  28. Open form "User Definition"
  29. Select [UserB]
  30. Navigate to the "User Caseload" section
  31. Validate the "Staff Member" field not populated, as expected
  32. Close the form
  33. Open form "Order Entry User Definition"
  34. Search for [UserB] in the "Select Order Entry User" field
  35. Validate [UserB] is not found, as expected
  36. Close the form
  37. Run the report to display data in the "SYSTEM.RADplus_Users" table
  38. Validate row is present for [UserA]
  39. Validate the "staff_member_ID" field is populated with "ID#" imported for [StaffA] in step 1, as expected
  40. Validate a row is present for [UserB]
  41. Validate the "staff_member_ID" field is blank, as expected
Modeling - Table Alias fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
Scenario 1: Modeled Forms - Validate form submission when hiding fields using "Form Designer"
Specific Setup:
  • Have a modeled form that contains mapped "Table" aliased fields on the form
  • For this example, a form [TestForm] has the following "Service" alias type fields mapped on the form which are necessary to file a service in the modeled form: "Date of Service", "Service Code", "Practitioner, Program", and "Duration"
  • Have access to "Form Designer"
  • Have a report created to display data in the "SYSTEM.Billing_tx_history" table
Steps
  1. Open form "Form Designer"
  2. Select form [TestForm]
  3. Select the section containing the table aliased fields.
  4. Highlight the label and text box for "Duration" and uncheck the box
  5. On left side panel, uncheck the box named "Visible"
  6. Click [Save]
  7. Submit the form
  8. Open [TestForm]
  9. Select any client [TestClient]
  10. Complete Date of Service, Service Code, Practitioner, and Program. These are required. Complete any other prompts desired.
  11. Submit the form as "Final".
  12. Validate submission is blocked with an error message "Prompt mapped to Duration (Minutes) is missing."
  13. Close the form
  14. Open form "Form Designer"
  15. Select form [TestForm]
  16. Select the section containing the table aliased fields.
  17. Highlight the label and text box for "Duration"
  18. On the left side panel, check the box named "Visible" to unhide the field on the form
  19. Click [Save]
  20. Submit the form
  21. Open [TestForm]
  22. Select [TestClient]
  23. Complete "Date of Service", "Service Code", "Practitioner", and "Program".
  24. Submit as the form as "Final"
  25. Validate the form files successfully
  26. Generate the report to display the fields in the "SYSTEM.billing_tx_history" table for [TestClient]
  27. Validate a new row is found for the service created by the [TestForm] form in the previous steps
  28. Validate the "Date of Service", "Service Code", "Practitioner, Program", "Duration" and "Join_To_Tx_history" fields are populated as expected
Topics
• NX • Service Documentation • User Definition • Modeling
Update 23 Summary | Details
State Form Task Scheduler
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Task Scheduler
  • System Task Scheduler
Scenario 1: Scheduling a "State Form Definition" file(s) to be sent to an "FTP" Server (File Type - 'SFTP-Password')
Specific Setup:
  1. Have two state form definition files created in form "State Form Definition" [DefA] and [DefB]
  2. In form "State Form Definition", [DefA] and [DefB] have the following fields populate:
  3. The "File Path" field is populated with a directory location [FileLocation], that exists on the logged in users workstation
  4. In form "State Form Batch Creation" a batch file [Batchfile], has been created that contains state form definition files [DefA] and [DefB]
  5. Have an "FTP Server" set up to receive files
  6. Have the following "FTP Server" information available in order to populate the "State Form Task Scheduler" form during testing:
  7. The "Service Directory" location
  8. The "Server Host Name"
  9. The "Server Port Number"
  10. The "Server Username" field
  11. The "Server Password" field
Steps
  1. Open the 'State Form Task Scheduler' form
  2. Select [DefA]
  3. Select "Yes" in the "Create File" field
  4. Select "Yes" in "Send File To FTP Server" field
  5. In the "FTP Type" field, select "SFTP - Password"
  6. Based on the valid FTP values stated in the setup, populate the following required fields:
  7. "Server Host Name"
  8. "Server Port Number"
  9. "Server Username"
  10. "Server Password"
  11. "Service Directory"
  12. Click [Test FTP Connection]
  13. Validate test is successful
  14. For each FTP field populated in step 1e, enter an invalid value
  15. Click [Test FTP Connection]
  16. Validate the test is not successful
  17. Set the field back to the valid entry
  18. Submit the form
  19. Validate the form files successfully
  20. Open form "System Task Scheduler"
  21. Select the task set up for [DefA] in step 2 from the "Schedule(s)" field
  22. Populate the "Recurrence Pattern" field with desired value
  23. Populate the "Task Occurrence" field with the desired value
  24. Populate the "Start By" field with the desired date for the task to start
  25. Populate the "Start Time" field with the desired time for the task to start
  26. Select "No" in the "Inactive Task" field
  27. Click [Schedule Task]
  28. Close the form
  29. When the scheduled start by date and time for task filed in step 3 has passed:
  30. Validate the state form file [DefA] exists in the folder [FileLocation] on the logged in users server, set in step1
  31. Open the file
  32. Validate data results are as expected
  33. Validate the state form file [DefA] exists in the [Service Directory] location on the "FTP" server, specified in step 1e
  34. Open the file
  35. Validate date results are as expected
  36. Repeat steps 1 and 2, selecting the batch file [DefB]
  37. When the scheduled start by date and time for task filed has passed:
  38. Validate the state form file(s) [DefA] and [DefB] exists in the folder [FileLocation] on the logged in users server, set in step1
  39. Open each file
  40. Validate data results are as expected
  41. Validate the state form file [DefA] and [DefB] exists in the [Service Directory] location on the "FTP" server, specified in step 1e
  42. Open each file
  43. Validate date results are as expected
State Form Task Scheduler
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form File Generation
  • State Form Task Scheduler
  • System Task Scheduler
Scenario 1: "State Form Task Scheduler" - Scheduled a task for a' State Form Definition' file (Create File - No)
Specific Setup:
  • Have a state form definition file created in form "State Form Definition" [DefinitionA] with the "File Path" field populated with a valid folder location on the Avatar server. Make note of the folder location
Steps
  1. Open form "State Form Task Scheduler"
  2. Select "Single Definition" in the "Type" field
  3. Select the [DefinitionA] from the "Select Batch or Definition" drop down list
  4. Set field "Create File" to "No"
  5. Set the "File Description" field to a desired file name
  6. Select "Static" in the "Change From Date"
  7. Set the "Static Date" field to today's date
  8. Select "Static" in the "Change Through Date"
  9. Set the "Static Date" field to today's date
  10. Select "Yes" in the "Create File" field
  11. Click [Submit]
  12. At the dialog, "Filed. In order for compiles to be run, the new task must be scheduled using the 'System Task Scheduler' form", click [OK]
  13. Open the "System Task Scheduler" form
  14. In the "Schedule(s)" field, select the task created in step for [DefinitionA] in step 1
  15. Select a desired recurrence type pattern from the "Recurrence Pattern" field. For example "Daily"
  16. Populate a desired value in the "Task Occurrence Sequence".
  17. Populate the "Start By" field with today's date
  18. Populate the "Start Time" field with a time later than the current time
  19. Click [Schedule Task]
  20. Close the form
  21. Wait till the "Start Time" set in step 2 has passed
  22. Open the "State Form File Generation" form.
  23. Select [DefinitionA] in the "State Form" field
  24. Select "Dump File" in the "File Generation Options" field
  25. In the "Select File" field, select the compiled file for [DefinitionA], generated by the automated task set up in step 2
  26. Click [Process]
  27. Validate data displayed on the report is as expected
  28. On the Avatar server:
  29. Navigate to the folder location noted in the setup, where the state form file was set to be created
  30. Validate no file was generated, as expected since field "Create File" was set to "No" in step 1c
Topics
• State Form Task Scheduler • NX
Update 28 Summary | Details
Support is added for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Progress Notes (Group and Individual)
  • Appointment Management
  • Client Ledger
  • Avatar NX Report Viewer
  • Staff Members Hours And Exceptions
Scenario 1: Progress Notes (Group and Individual) - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • The 'Progress Notes' widget is on the HomeView for the logged in user.
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Enable Treatment Plan Grid" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings]
  4. Select "Enable Treatment Plan Grid" for 'Progress Notes (Group and Individual)' from the 'Registry Setting' list.
  5. Click [OK].
  6. Validate the 'Registry Setting Details' field contains "Enter "Y" to add 'Treatment Plan' grid field to the form. Enter "YD" to add the grid field and enable the functionality to default the previously selected treatment plan to the new row. Enter "N" to remove the field from the form."
  7. Enter "Y" in the 'Registry Setting Value' field.
  8. Click [Submit].
  9. Validate a "Registry Editor Filing" message is displayed stating: Successful filing.
  10. Click [OK].
  11. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  12. Click [No].
  13. Access the 'Progress Notes (Group and Individual)' form.
  14. Verify the 'Treatment Plan' grid is displayed.
  15. Enter "Client A" in the 'Select Client' field.
  16. Select the desired episode in the 'Select Episode' field.
  17. Select "Independent Note" in the 'Progress Note For' field.
  18. Select any value in the 'Note Type' field.
  19. Click [New Row] in the 'Treatment Plan' grid.
  20. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  21. Click [View] in the 'Select T.P. Item Note Addresses' field.
  22. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  23. Select the desired treatment plan item in the 'Treatment Plan' window.
  24. Click [Return].
  25. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  26. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  27. Enter the desired value in the 'Notes Field' field.
  28. Select "Draft" in the 'Draft/Final' field.
  29. Click [File Note].
  30. Validate a "Progress Notes" message is displayed stating: Note Filed.
  31. Click [OK].
  32. Validate the 'Treatment Plan' grid no longer contains the previously filed row.
  33. Select the note filed in the previous steps in the 'Select Draft Note To Edit' field.
  34. Validate the 'Treatment Plan' grid contains the row filed in the previous steps.
  35. Click [New Row] in the 'Treatment Plan' grid.
  36. Validate the 'Select T.P. Version' field does not contain a value.
  37. Select the second row in the 'Treatment Plan' grid.
  38. Click [Delete Row].
  39. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows?
  40. Click [Yes].
  41. Select "Final" in the 'Draft/Final' field.
  42. Click [File Note].
  43. Validate a "Progress Notes" message is displayed stating: Note Filed.
  44. Click [OK] and close the form.
  45. Access the 'Registry Settings' form.
  46. Enter "Enable Treatment Plan Grid" in the 'Limit Registry Settings to the Following Search Criteria' field.
  47. Click [View Registry Settings]
  48. Select "Enable Treatment Plan Grid" for 'Progress Notes (Group and Individual)' from the 'Registry Setting' list.
  49. Click [OK].
  50. Enter "YD" in the 'Registry Setting Value' field.
  51. Click [Submit].
  52. Validate a "Registry Editor Filing" message is displayed stating: Successful filing.
  53. Click [OK].
  54. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  55. Click [No].
  56. Access the 'Progress Notes (Group and Individual)' form.
  57. Verify the 'Treatment Plan' grid is displayed.
  58. Enter "Client A" in the 'Select Client' field.
  59. Select the desired episode in the 'Select Episode' field.
  60. Select "Independent Note" in the 'Progress Note For' field.
  61. Select any value in the 'Note Type' field.
  62. Click [New Row] in the 'Treatment Plan' grid.
  63. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  64. Click [View] in the 'Select T.P. Item Note Addresses' field.
  65. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  66. Select the desired treatment plan item in the 'Treatment Plan' window.
  67. Click [Return].
  68. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  69. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  70. Click [New Row] in the 'Treatment Plan' grid.
  71. Validate the 'Select T.P. Version' field defaults in with the value selected in the first row.
  72. Click [View] in the 'Select T.P. Item Note Addresses' field.
  73. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  74. Select the desired treatment plan item in the 'Treatment Plan' window.
  75. Click [Return].
  76. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  77. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  78. Enter the desired value in the 'Notes Field' field.
  79. Select "Final" in the 'Draft/Final' field.
  80. Click [File Note].
  81. Validate a "Progress Notes" message is displayed stating: Note Filed.
  82. Click [OK] and close the form.
  83. Select "Client A" and navigate to the 'Progress Notes' widget.
  84. Validate the progress notes filed in the previous steps are displayed.
  85. Validate the rows filed in the 'Treatment Plan' grid are displayed.
Scenario 2: Enhanced Appointment Management Grid - Validate scheduling/posting individual appointments
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A practitioner has hours defined for scheduling (Practitioner A).
  • The 'Enable Enhanced Appointment Management Grid' registry setting is set to "Y".
Steps
  1. Access the 'Appointment Management' form.
  2. Select "Practitioner A" in the 'Practitioner' field.
  3. Enter the current date in the 'Appointment Start Date' and 'Appointment End Date' fields.
  4. Click [Add/Edit Appointments].
  5. Validate the 'Appointment Management' grid is displayed and contains any existing appointments for the current date.
  6. Click [New Row].
  7. Enter the desired time in the 'Start' field.
  8. Enter the desired duration in the 'Duration' field.
  9. Validate the 'End' field is calculated based on the start time/duration of the appointment.
  10. Enter "Practitioner A" in the 'Practitioner' field.
  11. Enter the desired value in the 'Service Code' field.
  12. Enter "Client A" in the 'Client' field.
  13. Check "Post" for the appointment for "Client A".
  14. Click [Save] and validate the grid closes.
  15. Close the form.
  16. Access the 'Client Ledger' form.
  17. Select "Client A" in the 'Client ID' field.
  18. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  19. Select "Simple" in the 'Ledger Type' field.
  20. Select "Yes" in the 'Include Zero Charges' field.
  21. Click [Process].
  22. Validate the report contains the posted visit for "Client A".
  23. Close the report and the form.
Scenario 3: Diagnosis - Add new / Add to Problem List
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A practitioner must be defined (Practitioner A).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Click [Add] if present.
  3. Select any value for the 'Type of Diagnosis' field.
  4. Enter the desired values for the 'Date of Diagnosis' and 'Time of Diagnosis' fields.
  5. Click [New Row].
  6. Enter and select the desired value in the 'Diagnosis Search' field.
  7. Select "Practitioner A" in the 'Diagnosing Practitioner' field.
  8. Populate any desired and required fields.
  9. Select "Yes" in the 'Add to Problem List' field.
  10. Submit the form.
  11. Select "Client A" and access the 'Problem List' form.
  12. Click [Enter Problems].
  13. Validate the new diagnosis is included.
  14. Click [View - DSM/IDC Code].
  15. Validate a dialog opens with the DSM/IDC code data for the problem.
  16. Close out of the dialog.
  17. Click [View - System Notes].
  18. Validate the dialog displays the user information for the problem.
  19. Close out of the dialog.
  20. Click [Close/Cancel].
  21. Close the form.
Scenario 4: Site Registration - Add a site with hours of operation
Specific Setup:
  • Please note: This is for Avatar NX systems only.
Steps
  1. Access the 'Site Registration' form.
  2. Enter any value in the 'Select Site' field (Site A).
  3. Click [New Site].
  4. Validate a 'Site' dialog stating: "Auto Assign Next ID Number?"
  5. Click [Yes].
  6. Validate the 'Site Name' field contains "Site A".
  7. Enter the desired value in the 'Site Registration Date' field.
  8. Populate all required and desired fields.
  9. Select "Yes" in the 'Copy Information From An Existing Site?' field.
  10. Validate a 'Warning' dialog stating: "Copying information from an existing site will overwrite current 'Site Registration' Information. You must file this form prior to viewing/editing the 'Site Registration' information. Do you want to continue?" and click [Yes].
  11. Validate the 'Select Existing Site' field is enabled and required.
  12. Select "No" in the 'Copy Information From An Existing Site?' field.
  13. Validate the 'Select Existing Site' field is disabled.
  14. Select "All" in the 'Associated Programs' field.
  15. Verify the 'Time Zone' field is present and required.
  16. Select the desired value in the 'Time Zone' field.
  17. Click [Site Hours of Operation].
  18. Add the desired hours of operation and click [Save].
  19. Validate an 'Exit Grid' dialog stating: "Save Successful." and click [Yes].
  20. Click [Submit].
  21. Access the 'Site Registration' form.
  22. Enter "Site A" in the 'Select Site' field.
  23. Validate the form populates with the values entered in the previous steps.
  24. Close the form.
Scenario 5: 'Staff Members Hours and Exceptions' - Verification of 'Staff Member Hours' Information Entry/Filing
Specific Setup:
  • A staff member must be defined in 'Practitioner Enrollment' (Staff Member A).
Steps
  1. Access the 'Staff Members Hours and Exceptions' form for "Staff Member A".
  2. Click [Staff Member Hours].
  3. Validate the 'Staff Member Hours' grid is displayed.
  4. Click [New Row].
  5. Enter the desired date in the 'Effective Date' field.
  6. Select the desired day in the 'Day' field.
  7. Select the desired site in the 'Site' field.
  8. Enter the desired times in the 'Start Time' and 'End Time' fields.
  9. Populate any other desired values.
  10. Click [Save], [Yes], and [Submit].
  11. Access the 'Staff Members Hours and Exceptions' form for "Staff Member A".
  12. Click [Staff Member Hours].
  13. Validate the 'Staff Member Hours' grid is displayed.
  14. Validate the hours entered in the previous steps are displayed as expected.
  15. Close the form.
Topics
• Progress Notes • Appointment Management • Diagnosis • Site Registration • Practitioner
Update 35 Summary | Details
Envelope definition data
Scenario 1: Validate data in the 'SYSTEM.radplus_envelope_info' SQL Table View
Specific Setup:
  1. Have one or more modeled "Envelopes" defined in form "Envelope Definition" in the "PM" namespace and in any child namespace's. For this test "CWS" and "MSO" have envelopes defined
  2. The user has permissions assigned to query table view 'SYSTEM.radplus_envelope_info' in their user definition
  3. Have a report created to display data in table view 'SYSTEM.radplus_envelope_info', in each namespace
Steps
  1. Open the report created for table view 'SYSTEM.radplus_envelope_info' in the "PM" namespace
  2. Click to generate the report
  3. Validate the report reflects all the expected envelopes, defined in that namespace
  4. Validate the following fields are populated for each envelope, based the field values selected in form "Envelope Definition"
  5. Build Application (Avatar PM)
  6. Build Environment
  7. Envelope ID
  8. Envelope Name
  9. Envelope (SQL) Schema
  10. Envelope Version
  11. Is Envelope Eligible for Export?
  12. Always Allow Export
  13. Open the report created for table view 'SYSTEM.radplus_envelope_info' in the "CWS" namespace
  14. Click to generate the report
  15. Validate the report reflects all the expected envelopes, defined in that namespace
  16. Validate the following fields are populated for each envelope, based the field values selected in form "Envelope Definition"
  17. Build Application (Avatar CWS)
  18. Build Environment
  19. Envelope ID
  20. Envelope Name
  21. Envelope (SQL) Schema
  22. Envelope Version
  23. Is Envelope Eligible for Export?
  24. Always Allow Export
  25. CDR (SQL) Schema
  26. Open the report created for table view 'SYSTEM.radplus_envelope_info' in the " MSO" namespace
  27. Click to generate the report
  28. Validate the report reflects all the expected envelopes, defined in that namespace
  29. Validate the following fields are populated for each envelope, based the field values selected in form "Envelope Definition"
  30. Build Application (Avatar MSO)
  31. Build Environment
  32. Envelope ID
  33. Envelope Name
  34. Envelope (SQL) Schema
  35. Envelope Version
  36. Is Envelope Eligible for Export?
  37. Always Allow Export
  38. CDR (SQL) Schema
Topics
• SQL Data Access
2022 Update 116 Summary | Details
State Form Query Logging - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form File Generation
  • State Form Query Logging
Scenario 1: 'State Form Query Logging' form - Functionality and validations
Specific Setup:
  • Have a system with two state form file definitions created in form "State Form Definition" [SFileA] and [SFileB]
  • [SFileA] is a definition that contains one record [Rec]
  • [SFileB] is a definition that contains two records [Rec] and [Rec2]
  • Have a report to display data in the "RADplus_sf_audit_query" table, sorted by the "ID" field and displaying the fields "ID", "Query" and "Rec"
Steps
  1. Open form "State Form File Generation"
  2. Select definition [SFileA] in the "State Form" field. (Make a note of the file "ID" number located next to the state form file name)
  3. Select "Compile" in the "File Generation Options" field
  4. Populate the "File Description" field
  5. Click [Process]
  6. At the "Compile Complete" dialog, click [OK]
  7. Open form "State Form Query Logging"
  8. Select definition [SFileA] in the "State Form" field
  9. Validate the "Record" filed is automatically populated with the record name [Rec]. (Make a note of the record name)
  10. Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
  11. Close the form
  12. Run the report created to query table "RADplus_sf_audit_query" table
  13. In the "ID" column, locate the row that contains a value starting with the definition "ID" for [SFileA], noted in step 1a
  14. Validate the "Record" field value matches the value noted in step 2a
  15. Validate the "Query" field value matches the value noted in step 2a
  16. Close the report
  17. Open form "State Form File Generation"
  18. Select definition [SFileB] in the "State Form" field. (Make a note of the file "ID" number, located next to the state form file name)
  19. Select "Compile" in the "File Generation Options" field
  20. Populate the "File Description" field
  21. Click [Process]
  22. At the "Compile Complete" dialog, click [OK]
  23. Open form "State Form Query Logging"
  24. Select definition [SFileB] in the "State Form" field
  25. Click the "Record" field
  26. Validate there are two records for selection, as expected. [Rec] and [Rec2]
  27. Select [Rec]
  28. Validate the "Record" field is automatically populated with the record name [Rec]. (Make a note of the record name)
  29. Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
  30. Navigate back to the "Record" field
  31. Select [Rec2]
  32. Validate the "Record" field is automatically populated with the record name [Rec]. (Make a note of the record name)
  33. Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
  34. Run the report created to query table "RADplus_sf_audit_query" table
  35. In the "ID" column, locate the row(s) that contains a value starting with the definition "ID" for [SFileB], noted in step 4a
  36. Validate a row is found for record name [Rec]
  37. Validate the "Query" field value for record [Rec] matches the value noted in step 5a
  38. Validate a row is also found for record name [Rec]
  39. Validate the "Query" field value for record [Rec2] matches the value noted in step 5a
  40. Close the report
'State Form Parameters Definition' - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Parameter Definition
  • State Form File Generation
  • State Form Definition
Scenario 1: 'State Form Parameters Definition" form - Functionality and validations
Specific Setup:
  • In form "Update Client Data", have one or more clients on the system that have any "Date", "Single-Select" field and "Multi-Select" field populated. For this test the following fields will be used:
  • "Martial Status", single-select field
  • "Date of Birth", date field
  • "Other Languages", multi-select field
  • Have a state form definition file [StateFile] set up in form "State Form Definition", that extracts "PATID", "Name", "Marital Status", "Date of Birth" and "Other Languages" from the "SYSTEM.patient_current_demographics" table
  • In form "State Form Definition", edit file [StateFile]
  • Navigate to the "Define Record Table" section of the definition and
  • Select the row defined containing the "SYSTEM.patient_current_demographics" table
  • Navigate to the "Additional SQL Conditions" column and populate the field with the following SQL parameter "p.marital_status_code={?Param1}"
  • Submit the form
Steps
  1. Open form "State Form Parameter Definition"
  2. Select [StateFile] in the "State Form Definition" field
  3. Select "Add New" in the "Select Parameter" field
  4. Set the "Parameter Description" field to a desired name for the single-select field. For this example, "Marital Status"
  5. Validate the "Parameter Number" field contains "1"
  6. Validate the "Parameter Reference" field contains "{?Param1}"
  7. Select "Single Select Dictionary" in the "Parameter Type" field
  8. Select "Yes" in the "Required" field
  9. In the "Entity Database" field, select "Client"
  10. Search and select "(10) Marital Status" from the "Dictionary" field
  11. Select "Active" in the "Status" field
  12. Click the [File] button
  13. Validate the form submits successfully
  14. Open form "State Form File Generation" and select [StateFile] in the "State Form" field
  15. Click the "Compile" radio button in the "File Generation Options" field
  16. Set the "File Description" field to the desired name. For example, "Married Clients File"
  17. Click the Process button
  18. The user is prompted with a "Select Values - Dialog"
  19. Validate the "Martial Status" dictionary selection list is displayed
  20. Select the desired marital status and click [OK]
  21. Click [OK] at the "Compile Complete" message
  22. In the "File Generation Options" field, select the "Dump File" radio button
  23. Click [Process]
  24. Validate the "Data Dump File - Report" contains only clients with a "Martial Status" field equal to the value selected in the previous step
  25. Close the report
  26. Open form "State Form Definition", edit the state form file [StateFile]
  27. Navigate to the "Define Record Table" section of the definition and
  28. Select the row defined containing the "SYSTEM.patient_current_demographics" table
  29. Navigate to the "Additional SQL Conditions" column and replace the previous SQL parameter with one for the "Date" field. For this test enter "p.other_lang_code={?Param2}"
  30. Open form "State Form Parameter Definition"
  31. Select [StateFile] in the "State Form Definition" field
  32. Select "Marital Status" in the "Select Parameter" field, entered in step 1
  33. Click [Delete] to removed it
  34. Click the "Select Parameter" field and select "Add New"
  35. Validate the "Parameter Number" field contains "1"
  36. Validate the "Parameter Reference" field contains "{?Param1}"
  37. Set the "Parameter Description" field to a desired name for the multi-select field. For this example, "Other Languages"
  38. Select "Multi-Select Dictionary" in the "Parameter Type" field
  39. Select "Yes" in the "Required" field
  40. In the "Entity Database" field, select "Client"
  41. Search and select the multi-select field, for this test,"(149) Primary Language" is selected
  42. Select "Active" in the "Status" field
  43. Click the [File] button
  44. Validate the form submits successfully
  45. Open form "State Form File Generation" and select [StateFile] in the "State Form" field
  46. Click the "Compile" radio button in the "File Generation Options" field
  47. Set the "File Description" field to the desired name. For example, "Other Languages File"
  48. Click the [Process] button
  49. The user is prompted with a "Select Values - Dialog"
  50. Validate the "Other Languages" dictionary selection list is displayed
  51. Select the desired values and click the [OK] button
  52. Click [OK] at the "Compile Complete" message
  53. In the "File Generation Options" field, select the "Dump File" radio button
  54. Click [Process]
  55. Validate the "Data Dump File - Report" contains only clients that have the "Other Languages" field populated with the value(s) selected in the previous step
  56. Close the report
  57. Open form "State Form Definition", edit the state form file [StateFile]
  58. Navigate to the "Define Record Table" section of the definition and
  59. Select the row defined containing the "SYSTEM.patient_current_demographics" table
  60. Navigate to the "Additional SQL Conditions" column and replace the previous SQL parameter with one for the "Date" field. For this test enter "p.date_of_birth={?Param1}"
  61. Submit the form
  62. Open form "State Form Parameter Definition"
  63. Select [StateFile] in the "State Form Definition" field
  64. Select "Other Languages" in the "Select Parameter" field, entered in step 1
  65. Click [Delete] to removed it
  66. Click the "Select Parameter" field and select "Add New"
  67. Validate the "Parameter Number" field contains "1"
  68. Validate the "Parameter Reference" field contains "{?Param1}"
  69. Set the "Parameter Description" field to a desired name for the multi-select field. For this example, "Date of Birth"
  70. Select "Date" in the "Parameter Type" field
  71. Select "Yes" in the "Required" field
  72. Select "Active" in the "Status" field
  73. Click the [File] button
  74. Validate the form submits successfully
  75. Open form "State Form File Generation" and select [StateFile] in the "State Form" field
  76. Click the "Compile" radio button in the "File Generation Options" field
  77. Set the "File Description" field to the desired name. For example, "Date of Birth File"
  78. Click the [Process] button
  79. The user is prompted with a "Select Values - Dialog"
  80. Validate the "Date of Birth" input field is displayed
  81. Enter the desired date and click [OK]
  82. Click [OK] at the "Compile Complete" message
  83. In the "File Generation Options" field, select the "Dump File" radio button
  84. Click [Process]
  85. Validate the "Data Dump File - Report" contains only clients that contain a date of birth equal to value populated in the previous step
  86. Close the report
'State Form Definition Versioning' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form Definition Versioning
  • Enter a description of any changes made- Dialog
Scenario 1: State Form Definition - Import/Export
Specific Setup:
  • Have a state form definition file created in form "State Form Definition". [SFDefFile]
Steps
  1. Open form "State Form Definition"
  2. Click section "State Form Definition File Import/Export"
  3. Select [SFDefFile] from the "Select State Form For Export" field
  4. Click [Export State Form]
  5. Click [Save] to save the file [SFileExp] to a folder
  6. Close the form
  7. Open form "State Form Definition"
  8. Select [SFDefFile] for edit
  9. Navigate to any field on the form and note its current value. For example the "File Type" field
  10. Enter or select a new value in the field
  11. Submit the form
  12. Open form "State Form Definition"
  13. Select [SFDefFile] for edit
  14. Validate the change made to the field in step 2 is present as expected
  15. Close the form
  16. Open form "State Form Definition"
  17. Click section "State Form Definition File Import/Export"
  18. Click [Select File for Import]
  19. Navigate to the location of the export file [SFileExp]
  20. Select the file
  21. Click [Open]
  22. Click [Process Import]
  23. Validate message "Import Complete" is displayed
  24. Close the form
  25. Open form "State Form Definition"
  26. Select [SFDefFile] for edit
  27. Validate the change made to the field in step 2, has returned to its original value
  28. Close the form
Scenario 2: "State Form Definition Versioning" form - Functionality and validations
Specific Setup:
  • A state form file definition file exists, created in form "State Form Definition" [StateFormFile]
Steps
  1. Open form "State Form Definition Versioning"
  2. Select [StateFormFile] from the "State Form Definition" field
  3. Click "Create New Version" in the "Action" field
  4. Validate the "Version Number" field is set to "1"
  5. Click "Create New Subversion"
  6. Validate a message stating a subversion cannot be created until the initial version is created is displayed
  7. Click [OK]
  8. Click "Create New Version"
  9. Populate the "Version Description" field
  10. Submit the form
  11. Return to form "State Form Definition Versioning"
  12. Select [StateFormFile] from the "State Form Definition" field
  13. Click "Create New Subversion"
  14. Validate a message is displayed stating that the current version must be finalized before a subversion can be created
  15. Click [OK]
  16. Click "Finalize Version
  17. Validate a message is displayed stating that once this form is submitted, the definition cannot be modified until a new version is created.
  18. Click [OK]
  19. Click [Submit]
  20. Return to form "State Form Definition Versioning"
  21. Select [StateFormFile] from the "State Form Definition" field
  22. Click "Create New Subversion" in the "Action" field
  23. Validate the "Version Number" field contains "1.01"
  24. Populate the "Version Description" text field
  25. Submit the form
  26. Open form "State Form Definition"
  27. Select [StateFormFile] from the "State Form Definition" field
  28. Validate the "Version Number" field contains "1.01"
  29. Change any field value on the form. For this example the "File Type" was changed from "Delimited" to "XML"
  30. Click the [File Form] button
  31. In the "Enter a description of any changes made" dialog, enter a description of the change
  32. Click the OK button
  33. Close the form
  34. Open form "State Form Definition Versioning"
  35. Select [StateFormFile] from the "State Form Definition" field
  36. Validate the "Version Number" field has a value of "1.01"
  37. Validate the "Change Log" text box contains: "Version 1.01", the description of the change, the time/date of the change and name of the user who filed the change
  38. Click "Restore Version" in the "Action" field
  39. Select "1" from the "Select Version" field
  40. Submit the form
  41. Open form "State Form Definition"
  42. Select [StateFormFile] from the "State Form Definition" field
  43. Validate the "Version Number" field has a value of "1"
  44. Validate the field value change made in step 4, has been reverted back to its original value. (For this test, the "File Type" field value has been reverted back to its original value of "Delimited")
  45. Close the form
  46. Open form "State Form Definition Versioning"
  47. Select [StateFormFile] from the State Form Definition field
  48. Click "Restore Version" in the "Action" field
  49. Select "1.01" from the "Select Version" field
  50. Submit the form
  51. Open form "State Form Definition"
  52. Select [StateFormFile] from the "State Form Definition" field
  53. Validate a warning is displayed "Definition is currently final, editing is not permitted unless a new version is created in the 'State Form Definition Versioning' form.
  54. Validate the [File Form] and the [Delete Form] buttons are disabled
  55. Validate the field value change made in step 4 has returned. (For this test, the "File Type" field value has returned to changed value of "XML" made in step 4)
  56. Close the form
  57. Open form "State Form Definition Versioning"
  58. Select [StateFormFile] from the State Form Definition field
  59. Validate the "Version Number" field is populated with "1"
  60. Click "Delete Version" in the "Action" field
  61. Submit the form
  62. Click "Yes" to return to the form
  63. Select [StateFormFile] from the State Form Definition field
  64. Validate the "Version Number" field is populated with "1.01"
  65. Click "Restore Version" in the "Action" field
  66. Validate message "No additional versions found for selected definition" is displayed
  67. Click [OK]
  68. Close the form
Topics
• NX • State Form Tools • State Forms
2022 Update 142 Summary | Details
Product Updates - form compiles
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Updates (PM)
  • Print Error Log (PM)
Scenario 1: 'Product Updates' Form - Installation and post installation validations
Specific Setup:
  • Have a system where a product update [TestUpdate] will be installed that compile a form or forms. For example an update that will require compiling "Modeled" forms.
Steps
  1. Open form "Product Updates"
  2. Click [Select Application]
  3. Select the desired application
  4. Click [Select Update/Customization Pack]
  5. Browse to the location containing the ".GSA" file for [TestUpdate]
  6. Click [OK]
  7. Click [Review Update/Customization Pack Contents]
  8. Validate the results in the "Review Update/Customization Pack Contents" text box are as expected for the update being loaded
  9. Click [Install Update Customization Pack]
  10. Validate message "Update Loaded" is displayed
  11. Click [OK]
  12. Close the form
  13. Open form "Current Server" in application the update was installed in
  14. Navigate to the "Updates" list section
  15. Click the search text editor icon
  16. In the update listing search for the update installed in step 1
  17. Validate the update is found, as expected
  18. Close the form
  19. Open form "Print Error Log"
  20. Select today's date
  21. Run the report
  22. Validate there are no errors
  23. Locate any form that may have been recompiled by the product update. For example a "Modeled" form
  24. Populate the fields on the form
  25. Submit the form
  26. Validate the form files successfully
  27. Return to the form
  28. Select the row just submitted
  29. Validate all fields are populated, as expected
Topics
• Update Install • NX
2022 Update 143 Summary | Details
Registry Setting - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling Import/Export (CWS)
  • Form Designer (CWS)
  • Progress Notes (Group and Individual)
Scenario 1: Registry Settings - submission of a registry setting
Steps
  1. Access the 'Registry Settings' form.
  2. In the "Limit Registry Settings to the Following Search Criteria" field, enter any keyword to find a desired registry setting
  3. Click [View Registry Settings].
  4. Validate the registry setting is displayed as expected and in a timely manner
  5. Note the current value of the setting and change it to a new value
  6. Click [Submit].
  7. Validate a "Registry Editor Filing" dialog is displayed stating: Successful filing.
  8. Click [OK]
  9. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  10. Click [Yes].to return to the form
  11. In the "Limit Registry Settings to the Following Search Criteria", select the same registry setting updated in step 1
  12. Validate the value changed in step 1b is present, as expected
  13. Click [Submit].
  14. Validate a "Registry Editor Filing" dialog is displayed stating: Successful filing.
  15. Click [OK]
  16. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  17. Click [Yes].to return to the form
  18. In the "Limit Registry Settings to the Following Search Criteria", select the same registry setting updated in step 1
  19. Validate the value submitted in step 2b is present, as expected
  20. Close the form
Topics
• Registry Settings • NX