Skip to main content

RADplus 2022 Monthly Release 2022.00.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 3 Summary | Details
Identity Manager - logins
Scenario 1: Avatar "Identity Manager" - User Login validation
Specific Setup:
  • Have a system with the "Identity Manager" module installed and configured
  • Have an active "Identity Manager" user set up in form "User Definition" [UserA]
Steps
  1. Launch the Avatar login screen
  2. Select the desired system code in the "System Code" field
  3. Populate the "Username" field with the user name for [UserA]
  4. Populate the "Password" field with the password for [UserA]
  5. Click [Sign In]
  6. In the "Search Forms" search box, search for any form
  7. Validate the form is launched as expected
  8. Populate any desired fields in the form
  9. Submit the form
  10. Validate submission is successful
Topics
• Cache • NX
Update 6 Summary | Details
Routing Admin Dashboard
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Routing Admin Dashboard
Scenario 1: Routing Admin Dashboard - Search results validations
Specific Setup:
  • The system is set up for "Rule Based Routing"
  • The system has over a "1000" documents filed in a single rule based routing queue.[QueueA]
Steps
  1. Open the 'Routing Admin Dashboard' form.
  2. Select [QueueA] in the 'Queue' field and leave all other search criteria fields unpopulated
  3. Click [Search]
  4. Validate up to "1000" rows of data are displayed in the grid. (The system maximum number of rows that can be displayed in the grid)
  5. in the "Queue Search Criteria" section, use any of the search fields to narrow down the results, for example the "Select Programs" field
  6. Click [Search]
  7. Validate the results are displayed as expected, based on the search criteria
Topics
• Rule Based Routing
Update 7 Summary | Details
Avatar NX - connecting to external ODBC sources
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • NX External ODBC Data Sources
Scenario 1: 'NX External ODBC Data Sources" form - Functionality
Specific Setup:
  • Have access to an external database server [ServerA], that contains table data [TableA]. For example, an "SQL Server"
  • Using the windows "ODBC Data Source Administrator", create a "User Data Source" [DataSourceA] configured to use an "SQL Server" driver to connect to the [ServerA]
Steps
  1. Open form "NX External ODBC Data Sources"
  2. Select "Create New" in the "Action" field
  3. Set the "Driver Type" field to desired value
  4. Set the "ODBC Data Source Name" to [DataSourceA]
  5. Set the "Server Host/IP" to the "Host" name or "IP Address" of [ServerA]
  6. Set the "Username" field to the login user name for [ServerA]
  7. Set the "Password" field to the login password for [ServerA]
  8. Click the [File] button
  9. Click the [OK] button
  10. Return to form "NX External ODBC Data Sources"
  11. Select "Edit Existing" in the "Action" field
  12. In the "Select Existing Data Source" field, select [DataSourceA]
  13. Validate the "Driver Type" field is populated with the value selected in step 3
  14. Validate the "ODBC Data Source Name" is populated with [DataSourceA]
  15. Validate the "Server Host/IP" field is set to the value populated in step 5
  16. Validate the "Username" field is set to the value populated in step 6
  17. Validate the Password field is populated with the value populated in step 7
  18. Exit the form
Scenario 2: 'Import Reports' Form (Avatar NX) - Validate "Import Report for Command Button Launch" requiring and External "ODBC" connection
Specific Setup:
  • An external database exists on [ServerA] that contains data in a table [TableA].
  • Using form "NX External ODBC Data Sources", have an "ODBC Data Source" created [DataSourceA] configured to use an ODBC driver to connect to the external database server [ServerA]
  • Have a Crystal Report [ReportA] created that connects to the external database [ServerA] using [DataSourceA] in order to display data in [TableA].
Steps
  1. Open form "Import Reports"
  2. Select "Import Report for Command Button Launch" in the "Select Import Type"
  3. Select "Import New Report" in the "New or Existing Report" field
  4. Set the "Report Description" field to a desired report name
  5. Click the [Select Report for Import] button
  6. Navigate to the location of [ReportA]
  7. Select the report
  8. Select "Yes" in field "Does This Report Require ODBC Connections In Addition To The Current Database" field
  9. In the "Connection Type" field, select "myAvatar NX"
  10. In the "myAvatar NX Connection" field, select [DataSourceA]
  11. Click [Add New Connection] button
  12. Validate the Additional ODBC Connections text box is populated with the [DataSourceA] connection
  13. Click [Submit]
  14. Return to the form
  15. Select "Import Report for Document Routing" in the "Select Import Type"
  16. Select "Update Existing Report" in the "New or Existing Report" field
  17. From the "Existing Report" field drop down list, select the report added in step 4
  18. Validate the "Report Description" field is the value set in step 4
  19. Validate the "Additional ODBC Connections" text box is populated with the connection for [DataSourceA]
  20. Close the form
Scenario 3: 'Import Reports' Form (Avatar NX) - Validate "Import Report for Document Routing" requiring an External "ODBC" connection
Specific Setup:
  • An external cache database exists on [ServerA] that contains data in a table [TableA].
  • Using form "NX External ODBC Data Sources", have an "ODBC Data Source" created [DataSourceA] configured to use an ODBC driver to connect to the external database server [ServerA]
  • Have a Crystal Report [ReportA] created that connects to the external database [ServerA] using [DataSourceA] to display data in [TableA].
Steps
  1. Open form "Import Reports"
  2. Select "Import Report for Document Routing" in the "Select Import Type"
  3. Select "Import New Report" in the "New or Existing Report" field
  4. Set the "Report Description" field to a desired report name
  5. Click the [Select Report for Import] button
  6. Navigate to the location of [ReportA]
  7. Select the report
  8. Select "Yes" in field "Does This Report Require ODBC Connections In Addition To The Current Database" field
  9. In the "Connection Type" field, select "myAvatar NX"
  10. In the "myAvatar NX Connection" field, select [DataSourceA]
  11. Click [Add New Connection] button
  12. Validate the Additional ODBC Connections text box is populated with the [DataSourceA] connection
  13. Click [Submit]
  14. Return to the form
  15. Select "Import Report for Document Routing" in the "Select Import Type"
  16. Select "Update Existing Report" in the "New or Existing Report" field
  17. From the "Existing Report" field drop down list, select the report added in step 4
  18. Validate the "Report Description" field is the value set in step 4
  19. Validate the "Additional ODBC Connections" text box is populated with the connection for [DataSourceA]
  20. Close the form
Topics
• Query/Reporting • NX • Import Reports
Update 8 Summary | Details
Prepared for future functionality.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Scrolling Free Text Templates (CWS)
Scenario 1: Product Scrolling Free Text Templates- Validate functionality
Specific Setup:
  • In form "Product Scrolling Free Text Templates", have a templates set up for a text field in any product form. For this test the "Notes" field of the "Ambulatory Progress Notes" form is used
Steps
  1. Open the product form.
  2. Right click in the "Notes Text" field.
  3. Select one of the "System" templates created.
  4. Validate the text populated is as expected for that template.
  5. Right click in the "Notes" field.
  6. Select the "System" template created.
  7. Validate the text populated, is as expected for that template.
  8. Submit the form.
  9. Re-open the product form.
  10. Select the row just submitted.
  11. Validate all template data filed in the text field is present on the form.
  12. Close the form.
Scenario 2: Modeled Form - Validate Table Row Data
Specific Setup:
  • In the parent namespace "Avatar PM", have modeled form [PMFormA] that contains a table [PMTableA] which includes a binary storage field, for example a picture or signature field. [PMFormA]
  • In a child application for example "Avatar CWS", have an envelope [CWSEnvelopeA] that is set with prompt "Include Envelope in CDR" set to "Yes" and contains a form [CWSFormA], that includes a [CWSTableA] which includes a binary storage field
  • Have a report [PMReportA] to display data filed in [PMTableA]
  • Have a report [CWSReportA] to display data filed in [CWSTableA]
  • Have a report [CWSReportB] set up to display data filed in [CWSTableA] but using the "CDR" table in "Avatar PM" to display the data
  • [UserA] has access to [PMFormA] and [CWSFormA]
  • Have two clients [ClientA] and [ClientB] who are enrolled in an open episode
Steps
  1. Select [ClientA]
  2. Open [PMFormA]
  3. Select an episode
  4. Populate data in all fields, including the picture and/or signature fields. [Note the values populated in each field]
  5. Submit the form
  6. Validate the form files successfully
  7. Repeat step 2 a thru c, two or more times. [Note the total amount of times the form was submitted]
  8. Select [ClientB]
  9. Open [CWSFormA]
  10. Select an episode
  11. Populate data in all fields, including the picture and/or signature fields. [Note the values populated in each field]
  12. Submit the form
  13. Validate the form files successfully
  14. Repeat step 2 a thru 2c, two or more times. [Note the total amount of times the form was submitted]
  15. Run [PMReportA] to display table rows filed in the [PMTableA]
  16. Validate the total row count display is consistent with total amount of times the form was submitted, noted in step 2
  17. Validate the values populated in each row is consistent with values noted after each submission in step 2
  18. Run [CWSReportA] to display data rows filed in the [CWSTableA] table
  19. Validate the total row count display is consistent with total amount of times the form was submitted, noted in step 4
  20. Validate the values populated in each row is consistent with values noted after each submission in step 4
  21. Run [CWSReportB] to display data rows filed in the [CWSTableA] table using the "CDR" table in "Avatar PM"
  22. Validate the total row count display is consistent with total amount of times the form was submitted, noted in step 4
  23. Validate the values populated in each row is consistent with values noted after each submission in step 4
Topics
• Cache • Modeling • NX
Update 19 Summary | Details
'Team Assignment' form, 'My Clients' Widget', and 'Order Entry Console- Consult Teams
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Team Definition
  • Dictionary Update (CWS)
  • Order Code Setup
  • Order Entry User Role
  • Orders This Episode
  • Order Entry User Definition
Scenario 1: 'Team Definition' form - adding a Physician Team
Specific Setup:
  • A User Role must exist in the system. (User Role A)
  • A User must exist in the system. (User A)
Steps
  1. Access the ‘Team Definition’ form.
  2. Set the ‘Team ID’ field to "TeamIDA".
  3. Set the ‘Team Description’ field to "Team A".
  4. Select “Yes” in the ‘Active’ field.
  5. Select “Yes” in the ‘Physician Team’ field.
  6. Select “Yes” in the ‘Team Accepts Consult Orders’ field.
  7. Click [Select Roles].
  8. Select “User Role A” and click [OK].
  9. Validate the ‘Team Information’ field contains “User Role A”.
  10. Click [File].
  11. Validate a message displays stating “Filed” and click [OK].
  12. Set the ‘Team ID’ field to any value.
  13. Set the ‘Team Description’ field to "Team B".
  14. Select “Yes” in the ‘Active’ field.
  15. Select “Yes” in the ‘Physician Team’ field.
  16. Select “Yes” in the ‘Team Accepts Consult Orders’ field.
  17. Click [Select Roles].
  18. Select “User Role A” and click [OK].
  19. Validate a message is displayed stating “The following Roles are assigned to other Physician Teams. Role: User Role A Team(s): TeamIDA Do you wish to continue?” and click [Cancel].
  20. Validate a message is displayed stating “Cancelled” and click [OK].
  21. Set the ‘Team ID’ field to any value.
  22. Set the ‘Team Description’ field to "Team C".
  23. Select “Yes” in the ‘Active’ field.
  24. Select “Yes” in the ‘Physician Team’ field.
  25. Select “Yes” in the ‘Team Accepts Consult Orders’ field.
  26. Click [Select Users].
  27. Select “User A” and click [OK].
  28. Validate the ‘Team Information’ field contains “User A”.
  29. Click [File].
  30. Validate a message displays stating “Filed.” and click [OK].
  31. Set the ‘Team ID’ field to any value.
  32. Set the ‘Team Description’ field to "Team D".
  33. Select “Yes” in the ‘Active’ field.
  34. Select “Yes” in the ‘Physician Team’ field.
  35. Select “Yes” in the ‘Team Accepts Consult Orders’ field.
  36. Click [Select Users].
  37. Select “User A” and click [OK].
  38. Validate a message is displayed stating “The following Users are assigned to other Physician Teams. Users: User A Team(s): Team C Do you wish to continue?” and click [Cancel].
  39. Validate a message is displayed stating “Cancelled” and click [OK].
  40. Close the form.
Scenario 2: 'Admission' form - admission of a new client with a 'Team Assignment' filed
Specific Setup:
  • The 'RADplus->System Security->Team Definition->->->Update Physician Team Caseload based on Admitting or Attending Practitioner' registry setting must be set to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • Avatar PM 2021 Update 118 and RADplus 2021 Update 116 must be installed to utilize full functionality.
  • A Physician team must exist via the 'Team Definition' form with two Practitioners (Practitioner A and Practitioner B)
  • The user must have access to the 'SYSTEM.RADplus_caseload' table.
  • The user must have access to Crystal Reports or SQL tool.
Steps
  1. Access the 'Admission' form.
  2. Admit a new client (Client A) ensuring that "Practitioner A" is selected in the 'Admitting Practitioner' field.
  3. Create a report using the ‘SYSTEM.RADplus_caseload’ table with the following fields included: 'PATID', 'USERID', 'caseload_type_csm_code', and 'caseload_type_csm_value' .
  4. Filter the report by selecting "Client A's PATID" in the 'PATID' field.
  5. Validate there are two rows displayed for the team assignment for the new client created.
  6. Validate the ‘USERID’ field contains the USERID for the user logged into the application.
  7. Validate the 'caseload_type_CSM_code' field contains a row with "ADMITTING" and two rows with "TEAM".
  8. Validate the 'caseload_type_CSM_value' field contains a row with "Admitting Practitioner Caseload" and two rows with "Team Caseload Assignment".
  9. Close the report.
  10. Access the 'Admission' form.
  11. Admit a new client (Client B) ensuring that "Practitioner B" is selected in the 'Admitting Practitioner' field.
  12. Create a report using the ‘SYSTEM.RADplus_caseload’ table with the following fields included: 'PATID', 'USERID', 'caseload_type_csm_code', and 'caseload_type_csm_value' .
  13. Filter the report by selecting "Client A's PATID" in the 'PATID' field.
  14. Validate there are two rows displayed for the team assignment for the new client created.
  15. Validate the ‘USERID’ field contains the USERID for the user logged into the application.
  16. Validate the 'caseload_type_CSM_code' field contains a row with "ATTENDING" and two rows with "TEAM".
  17. Validate the 'caseload_type_CSM_value' field contains a row with "Attending Practitioner Caseload" and two rows with "Team Caseload Assignment".
  18. Close the report.
Scenario 3: OE NX - Orders This Episode - Create a new 'Consult' order, copy order, modify order and DC order.
Specific Setup:
  • Avatar OE 2021 Update 61, RADplus 2022 Update 19, RADplus 2021 Update 116 and myAvatar NX Release 2021.11.00 are required in order to utilize full functionality.
  • An 'Order Type' of "Consult Order" must exist in the Order Entry Tabled Files '(500) Order Types' dictionary with the following extended attributes set:
  • '(501) Order Type Category' extended attribute = "Consult"
  • '(506) Default Orders To Open-Ended When No Default Duration' = "No"
  • '(561) Display/Require Consult Clinician Name/Team prompts' = "Show both, require neither"
  • '(565) Default Consult 'Clinician Team' prompt based on 'Clinician Name' = "Yes"
  • Please log out of the application and log back in after completing the above configuration.
  • A user role must exist that has the ability to perform actions for "Consult Orders". This is done in the 'Order Entry User Role' form. (OE User Role A)
  • A user must exist who is associated with "OE User Role A". (User A)
  • A team must be defined in 'Team Definition' with the following configuration (Team A):
  • 'Physician Team' set to "Yes"
  • 'Team Accepts Consult Orders' is set to "Yes"
  • "User A" must be selected after clicking [Select Users]
  • 'Disable Adding Client to Caseload' is set to "No"
  • 'Use Team Finalizer as Default Supervisor for Document Routing' is set to "No"
  • A consult-type order code must exist that has "Team A" selected in the 'Limit Consult 'Clinician Team' prompt to the following Team' field and the 'Limit Consult 'Clinician Name' Prompt to Staff members having the following Category' field must have multiple values selected and must have the value associated with the Staff Member associated with "User A" selected. (Consult Order Code A)
  • A client must have an active episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
  • "User A" is logged in to the application.
Steps
  1. Select “Client A” and access the Order Entry Console.
  2. Search for and select “Consult Order Code A” in the ‘New Order Field’.
  3. Select “Team A” in the ‘Clinician Team’ field.
  4. Search for and select “User A” in the ‘Clinician Name’ field.
  5. Set the ‘Frequency’ field to “AS NEEDED”.
  6. Set the ‘Duration’ field to “48” and click [Hours].
  7. Click [Add to Scratchpad] and [Sign].
  8. Validate the ‘Order grid’ contains an order for “Consult Kidneys ClinicianTeam: Team A Clinician Name: User A AS NEEDED”.
  9. Select the order and click [Copy].
  10. Validate the ‘Clinician Team’ field contains “Team A”.
  11. Validate the ‘Clinician Name’ field contains “User A”.
  12. Validate the ‘Frequency’ field contains “AS NEEDED”.
  13. Validate the ‘Duration’ field contains “48” and [Hours] is selected.
  14. Click [Add to Scratchpad] and [Sign].
  15. Validate the ‘Interactions’ dialog displays.
  16. Override all interactions and click [Save Override and Exit].
  17. Validate the ‘Order grid’ contains two orders for “Consult Kidneys ClinicianTeam: Team A Clinician Name: User A AS NEEDED”.
  18. Select the 2nd order and click [Modify].
  19. Set the ‘Frequency’ field to “3 TIMES A DAY”.
  20. Click [Add to Scratchpad] and [Sign].
  21. Validate the ‘Interactions’ dialog displays.
  22. Override all interactions and click [Save Override and Exit].
  23. Validate the ‘Order grid’ contains an order for "Consult Kidneys ClinicianTeam: Team A Clinician Name: User A 3 TIMES A DAY” and an order for “Consult Kidneys ClinicianTeam: Team A Clinician Name: User A AS NEEDED”.
Scenario 4: 'My Clients' widget - Add to My Caseload, Remove From My Caseload
Specific Setup:
  • Avatar PM 2021 Update 118, RADplus 2021 Update 116, and myAvatar Client Update 2513-003 or 3201-001 must be installed in order to utilize full functionality.
  • The 'RADplus->Database Management->Client Lookup->->->Enable enhanced caseload management from the 'Clients and Data' widget' registry setting must be set to the User Role associated to the user logged into the application.
  • Please log out of the application and log back in after completing the above configuration.
  • "User A" must have access to all tables.
  • "User A" must be logged into the application.
Steps
  1. Access the ‘Admission’ form.
  2. Fill out all required fields and click [Submit]. This will be "Client A"
  3. Validate that "Client A" displays in the ‘Recent Clients’ list.
  4. Right click "Client A" and select [Add to My Caseload].
  5. Validate the ‘My Clients’ widget contains “Client A”.
  6. Right click "Client A" under 'My Clients' and select [Remove From My Caseload].
  7. Validate that “Client A” no longer displays in the ‘My Clients’ widget.
  8. Create a report using the 'SYSTEM.radplus_caseload' table using the following fields: 'PATID', 'USERID' and 'caseload_type_CSM_value, hidden'.
  9. Filter the report by selecting "Client A's PATID" in the 'PATID' field.
  10. Validate the report contains no rows of data for "Client A".
  11. Access the ‘Team Definition’ form.
  12. Click [Select Team].
  13. Select “PT1 (Physician Team Test)” in the ‘Select one of the following’ field and click [OK].
  14. Select the ‘Individual Client Assignment’ section.
  15. Search for and select “Client A” in the ‘Client ID’ field.
  16. Select the ‘Team Definition’ section and click [File].
  17. Validate a "Filed" message is displayed and click [OK].
  18. Close the form.
  19. Validate that “Client A” does not display in the ‘My Clients’ widget.
  20. Refresh the report using the 'SYSTEM.radplus_caseload' table
  21. Validate a row is displayed for "Client A".
  22. Validate the 'caseload_type_CSM_value' field contains "Team Caseload Assignment".
  23. Validate the 'hidden' field contains "X"
  24. Right click "Client A" in 'Recent Clients' and select [Add to My Caseload].
  25. Validate the ‘My Clients’ widget contains “Client A”.
  26. Refresh the report using the 'SYSTEM.radplus_caseload' table
  27. Validate the report contains two rows of data for "Client A".
  28. Validate the 'caseload_type_CSM_value' field contains "Individually Selected" for the new row added.
  29. Validate the 'hidden' field contains no value for both rows.
  30. Right click "Client A" and select [Remove From Physician Team].
  31. Validate the ‘My Clients’ widget contains “Client A”.
  32. Refresh the report using the 'SYSTEM.radplus_caseload' table
  33. Validate there is only one row of data for "Client A" that has "Individually Selected" in the 'caseload_type_CSM_value' field.
  34. Right click "Client A" under 'My Clients' and select [Remove From My Caseload].
  35. Validate that “Client A” no longer displays in the ‘My Clients’ widget.
  36. Refresh the report using the 'SYSTEM.radplus_caseload' table.
  37. Validate the report contains no rows of data for "Client A"
  38. Close the report.
Topics
• Team Definition
2021 Update 150 Summary | Details
'SYSTEM.RADplus_dict_user_def_stateform' table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form and Table Documentation (PM)
Scenario 1: Validate table 'SYSTEM.RADplus_dict_user_def_stateform'
Specific Setup:
  • UserA has access to the 'SYSTEM.RADplus_dict_user_def_stateform' table
  • UserA has access to the "Form and Table Documentation" form
  • Have a Crystal Report or other SQL query program to query the 'SYSTEM.RADplus_dict_user_def_stateform' table
  • Log in as [UserA]
Steps
  1. Open form "Form and Table Documentation"
  2. Select "Table" in the "Type of Documentation" field
  3. In the "Table(s) to be Documented" table list, select the " RADplus_dict_user_def_stateform" table
  4. Click [Process]
  5. Validate the "Facility" field contains the following:
  6. "Type" field value is "Integer"
  7. "Max Length" field value is "50"
  8. Validate the "dictionary_code" field contains the following:
  9. "Type" field value is "String"
  10. "Max Length" field value is "40"
  11. Validate the "dictionary_value" field contains the following:
  12. "Type" field value is "String"
  13. "Max Length" field value is "50"
  14. Validate the "field_description" field contains the following:
  15. "Type" field value is "String"
  16. "Max Length" field value is "40"
  17. Validate the "field_number" field contains the following:
  18. "Type" field value is "String"
  19. "Max Length" field value is "40"
  20. Validate the "inactive_codes" field contains the following:
  21. "Type" field value is "String"
  22. "Max Length" field value is "5"
  23. Using a Crystal Report or other SQL program, execute a query to display the fields in the "RADplus_dict_user_def_stateform" table. For example query: "SELECT * FROM RADplus_dict_user_def_stateform"
  24. Validate the "Column", "Type" and "Max Length" field values validated in steps 5 thru 10, are present in the results as expected
Add/Remove State Form Processing Flags' form
Scenario 1: Add/Remove State Form Processing Flags - form field validations
Specific Setup:
  • Have two state form definition files created
  • FileA has two records rec1 and rec2, each record has a "different" primary table
  • FileB has two records rec1 and rec2, each record has a "same" primary table
  • Each file has been compiled in form "State Form File Definition" with prompt "Generate Flag on Compile" set to "Y"
Steps
  1. Open the 'Add/Remove State Form Processing Flags' form
  2. In the "Action" field, select "Add Flags"
  3. In the "State Form" field, select the 'FileA' definition
  4. Click the "Record" field
  5. Validate, "ALL" is not an available for selection, since all records in the definition do not have the same primary table
  6. In the "State Form" field, select the 'FileB' definition
  7. Click the "Record" field
  8. Validate, "ALL" is listed, as this definition does contain all records with the same primary table
  9. Select the value
  10. In the "Properties to Display" list box, select the fields in the file to display for selection
  11. Click [Select Table Rows]
  12. In the "Row Data" selection list box, select any desired row [RowA]
  13. Click [OK]
  14. Click [Submit] to file the form
  15. Validate the form files successfully
  16. Open the 'Add/Remove State Form Processing Flags' form
  17. In the "Action" field, select "Remove Flags"
  18. In the "State Form" field, select the 'FileA' definition
  19. Click the "Record" field
  20. Validate, "ALL" is not an available for selection, as expected
  21. In the "State Form" field, select the definition Select the 'FileB' definition
  22. Click the "Record" field
  23. Validate, "ALL" is listed, as expected
  24. Select the value
  25. In the "Properties to Display" list box, select the same fields selected in step 5
  26. Click [Select Table Rows]
  27. In the "Row Data" selection list box, deselect the row selected in step 6, [RowA]
  28. Click [OK]
  29. Click [Submit] to file the form
  30. Validate the form files successfully
Topics
• NX • State Form Tools
2021 Update 151 Summary | Details
Document Routing - Tiff Image display
Scenario 1: "Document Routing" - Document display validations
Specific Setup:
  • Have a system that has the (Internal only) Registry Setting 'Enable Fixed-Width Font' set to the default setting of "Y". Please contact your Netsmart representative to enable this setting.
  • A form must be defined that has document routing enabled [FormA]
  • [UserA] is a staff member with the "My To Do's" widget on their home view
  • Log in as [UserA]
Steps
  1. Access [FormA]
  2. Populate all desired fields on the form, including the "Time" field
  3. Select "Final" in the 'Draft/Final' field.
  4. Click "OK"
  5. Click [Submit]
  6. In the "Confirm Document" screen:
  7. Verify document is displayed in the expected format, including proper spacing between characters and lines on the form
  8. Verify characters are displayed in the proper 'Font', in this test the "Lucida Sans Typewriter" font is validated
  9. Validate field heading characters are bold, when applicable
  10. Click [Accept and Route].
  11. Enter the user's password in the 'Password' field.
  12. Click [OK].
  13. In the "Route Document To" screen, select and add an approver
  14. Click [Submit].
  15. Click "No" to not return to the form
  16. Navigate to the 'My To Do's' widget.
  17. Locate the document in the "My To Do's" widget for [FormA]
  18. Click [Approve Document]
  19. In the "Confirm Document" screen:
  20. Verify document is displayed in the expected format, including proper spacing between characters and lines on the form
  21. Verify all text characters are displayed in the proper 'Font'
  22. Validate field heading characters are bold, when applicable
  23. Click [Accept].
  24. Enter the user's password in the 'Password' field.
  25. Click [OK].
  26. Validate the "To Do" accepted successfully and is removed from the 'My To Do's' widget.
Add User Signature - Tiff display
Scenario 1: "Append Documents" - Document display validations
Specific Setup:
  • Have a system that has the (Internal only) Registry Setting 'Enable Fixed-Width Font' set to the default setting of "Y". Please contact your Netsmart representative to enable this setting.
  • Have a document [DocumentA] for [ClentA] routed to [UserA]
  • Login as [UserA]
Steps
  1. Open the "Append Documents" form
  2. Select the form type used for one of the documents from the "Form Type" drop down list.
  3. Select [ClientA] in the "Entity" field
  4. Populate the "From Date" and "End Date" fields
  5. Click the drop down list in the "List of Documents" field
  6. Select [DocumentA] to append to
  7. Enter free text in the "New Comments to Be Appended in the Original Document" field
  8. Click [Submit]
  9. In the "Confirm Document" screen:
  10. Verify document is displayed in the expected format, including proper spacing between characters and lines on the form
  11. Verify all text characters are displayed in the proper 'Font', in this test the "Lucida Sans Typewriter" font is validated
  12. Validate field heading characters are in bold, when applicable
  13. Click [Accept]
  14. Enter the user's password
  15. Click [Verify]
  16. Validate the form files successfully
Append Document - Tiff Image display
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Add Non-User Signature (PM)
Scenario 1: Add Non User Signature - Document display validations
Specific Setup:
  • Have a system with registry setting "Enable Military Time" set to "Y"
  • Have documents created and routed using any form. For example a modeled form enabled for document routing
  • Have a user who is not a staff member with access to form "Add Non-User Signature"
Steps
  1. Open the "Add Non User Signature" form
  2. Select the form type used for one of the documents from the "Form Type" drop down list.
  3. Select [ClientA] in the "Entity" field
  4. Populate the "From Date" and "End Date" fields
  5. Click the drop down list in the "List of Documents" field
  6. Select [DocumentA]
  7. Enter free text in the "New Comments to Be Appended in the Original Document" field
  8. Populate any other required fields
  9. Click [Submit]
  10. In the "Confirm Document" screen:
  11. Verify document is displayed in the expected format, including proper spacing between characters and lines on the form
  12. Verify all text characters are displayed in the proper 'Font', in this test the "Lucida Sans Typewriter" font is validated
  13. Validate field heading characters are in bold, when applicable
  14. Click [Accept]
  15. Enter the user's password
  16. Click [Verify]
  17. Validate the form files successfully
Topics
• Document Routing • NX