Skip to main content

RADplus 2022 Monthly Release 2022.00.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 1 Summary | Details
Avatar RADplus 2022 is Installed
Scenario 1: Validate Upgrading RADplus 2021 to 2022 is successful when 2021.04.00 is loaded
Specific Setup:
  • Latest Monthly Release is installed.
Steps
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. Click [Close Form].
Topics
• Upgrade
2021 Update 100 Summary | Details
'System Security Defaults' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Security Defaults
Scenario 1: 'System Security Defaults' Form - Verification of 'Identity Manager Settings' Section/Fields
Specific Setup:

Avatar Identity Manager module must be installed

Steps
  1. Open the 'System Security Defaults' form (under 'Avatar PM / RADPlus Utilities / System Security / System Administration' path).
  2. Navigate to the 'Identity Manager Settings' section of form.
  3. Enter value including up to 150 characters in the 'Admin DN' configuration field.
  4. Enter value including up to 150 characters in the 'Identity Manager Base DN' configuration field.
  5. Enter/select values for all other 'Identity Manager Settings' configuration fields as required/desired.
  6. Click 'Submit' button to file 'System Security Defaults' form/values.
  7. Re-open 'System Security Defaults' form.
  8. Navigate to the 'Identity Manager Settings' section of form.
  9. Ensure that previously entered/filed value is present in the 'Admin DN' configuration field.
  10. Ensure that previously entered/filed value is present in the 'Identity Manager Base DN' configuration field.
Topics
• System Security Defaults • NX
2021 Update 119 Summary | Details
Avatar NX - URL Widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Widget Definition (PM)
Scenario 1: Validate creation and functionality of a "URL" type Widget
Specific Setup:
  • [UserA] has access to form "Widget Definition"
  • [UserA] is assigned to a home view [HomeviewA]
  • [UserA] has access to form "View Definition"
  • Login as [UserA]
Steps
  1. Launch form "Widget Definition"
  2. Click 'Select Widget'
  3. Select 'Add New Widget'
  4. Populate the "Title" field, with the name of the widget. For this example "WidgetA"
  5. In the "Widget Type" field select any other selection other than "URL"
  6. Validate the prompt "Launch URL in New Window in myAvatar NX" is disabled
  7. In the "Widget Type" field, select "URL"
  8. Set prompt "Launch URL in New Window in myAvatar NX" to "Yes"
  9. Select "Allow Re-fresh" and any other desired values in the "Widget Attributes" field
  10. Enter a valid URL in the "URL" field. [WebsiteA]
  11. Populate any other desired fields on the form
  12. Click [Submit] to create "WidgetA"
  13. Click "Yes" to return to the form
  14. Click 'Select Widget'
  15. Select "WidgetA"
  16. Validate all fields are populated as expected
  17. Close the form
  18. Open form "View Definition"
  19. Select the [HomeviewA]
  20. Drag and place "WidgetA" onto the view's layout
  21. Submit the form
  22. On the home view in the upper right-hand corner click "Customize" and click to "Reload" the home view
  23. Navigate to [WidgetA] on the home view
  24. Validate the widget contains a link that states, "Resource cannot be viewed in the widget, click here to open in a new tab." [Note: this only displays in "myAvatar NX", in "myAvatar" the results will always display within the widget]
  25. Click on the link
  26. Validate [WebsiteA] set as the "URL" in step 8, is displayed in a new window as expected
  27. Launch form "Widget Definition"
  28. Click 'Select Widget'
  29. Select [WidgetA]
  30. Set prompt "Launch URL in New Window in myAvatar NX" to "No"
  31. Click [Submit]
  32. Repeat step 14
  33. Navigate to [WidgetA] on the home view
  34. Validate [WebsiteA] set as the "URL" in step 8, is displayed within the widget
Topics
• Widget Definition • NX
2021 Update 123 Summary | Details
Acuity Compile - Domain score validation on the report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Acuity Compile
  • Avatar NX Report Viewer
  • Dictionary Update (PM)
  • Confirm Compile Completed
  • Acuity Rule Definition
  • Dynamic Form - Admission - Client
  • Admission (Outpatient)
  • Data Trail Configuration
  • Form and Table Documentation (PM)
  • Dictionary Update
  • User Definition
  • Admission
  • System Task Scheduler
  • Acuity Report
Scenario 1: Acuity Compile - Compile the acuity rule defined in the 'Acuity Rule definition' form.
Specific Setup:
  • Dictionary Update:
  • A 'Practitioner Category' must be defined in system for the 'Acuity Rule Definition' entry. Note the dictionary code/value.
  • A new dictionary code/value is created in the RADplus_Client file and 'Domain' data element (i.e. "HI - Homeless Indicator"). Note the dictionary code/value.
  • User definition:
  • Make sure the user has access to SYSTEM.admission_data_other SQL table.
  • Admission:
  • Two clients are admitted in the system as follows:
  • The 'Homeless indicator' on the 'Other Client Data' section is set to desired value for both the clients and is unique for each client. Note the value.
  • Acuity Rule Definition
  • Practitioner Category = Desired value defined in the 'Dictionary Update' section. Note the value.
  • Domain = Desired value defined in the 'Dictionary Update' section. Note the value.
  • Define Acuity Rules
  • Enter/select values in one or more Information Grid fields, ensuring that entered values are saved/present in grid.
  • Domain = Desired value. Note the value.
  • Subdomain = Desired value. Note the value.
  • System Table = Desired value. Note the value.
  • Field = Desired value. Note the value.
  • Conditional = Contains (CO)
  • Field Value = Desired value. Note the value.
  • Record Selection = Desired value. Note the value.
  • Weight = Desired value
Steps
  1. Open 'Acuity Compile' form.
  2. Select 'Compile' in the 'Options' field.
  3. Click [Submit].
  4. Click [Yes] to 'Form Return' message.
  5. Select 'Run Report' in the 'Options' field.
  6. Select the recently compiled 'Acuity File' from the drop down list.
  7. Verify the report launches successfully.
  8. Verify that the clients are included in the report with appropriate data and non-zero score.
Scenario 2: 'Acuity Rule Definition' form submission - The SYSTEM.acuity_rule table is setup in the 'Data Trail Configuration table for auditing
Specific Setup:
  • Data Trail Configuration:
  • The SYSTEM.acuity_rule table is selected for auditing.
  • Acuity Rule Definition:
  • An existing Acuity rule is identified or a new Acuity rule is created.
Steps
  1. Open the 'Acuity Rule Definition' form.
  2. Enter/select Practitioner Category/Domain combination for record entry/edit.
  3. Click [Define Acuity Rules].
  4. Ensure that Acuity Rules information grid is opened for entry/edit.
  5. Ensure existing Acuity Rules entries are present in Information Grid for display/edit.
  6. Select existing row for edit.
  7. Enter/edit/delete additional Acuity Rules information grid entries as desired, ensuring that all entered values are saved/present in grid.
  8. Click [Save].
  9. Ensure user is presented with dialog noting 'Save Successful'.
  10. Click [OK].
  11. Click [Submit].
  12. Verify the form submitted successfully.
Scenario 3: System Task Scheduler - Compile and Post Acuity scores
Specific Setup:
  • Dictionary Update:
  • A 'Practitioner Category' must be defined in system for the 'Acuity Rule Definition' entry. Note the dictionary code/value.
  • A new dictionary code/value is created in the RADplus_Client file and 'Domain' data element (i.e. "HI - Homeless Indicator"). Note the dictionary code/value.
  • User definition:
  • Make sure the user has access to SYSTEM.admission_data_other SQL table.
  • Admission:
  • An existing inpatient client is identified, or a new client admitted in the inpatient program as follows:
  • The 'Homeless indicator' on the 'Other Client Data' section is set to desired value. Note Client id/Name, Admission Unit.
  • Acuity Rule Definition
  • Practitioner Category = Desired value defined in the 'Dictionary Update' section. Note the value.
  • Domain = Desired value defined in the 'Dictionary Update' section. Note the value.
  • Define Acuity Rules
  • Enter/select values in one or more Information Grid fields, ensuring that entered values are saved/present in grid.
  • Domain = Desired value. Note the value.
  • Subdomain = Desired value. Note the value.
  • System Table = SYSTEM.admission_data_other. Note the value.
  • Field = SYSTEM.admission_data_other.holeless_code. Note the value.
  • Conditional = Contains (CO)
  • Field Value = Desired value. Note the value.
  • Record Selection = Desired value. Note the value.
  • Weight = Desired value
Steps
  1. Open the 'System Task Scheduler' form.
  2. Select the 'Compile and post Acuity Score' from the 'Schedule(s)' field.
  3. Set the 'Recurrence Pattern to 'Daily'.
  4. Set 'Start By' to current date.
  5. Set 'Start Time' to current time plus 5 minutes.
  6. Set 'Inactive Task to 'No'.
  7. Click [Schedule Task].
  8. Close the form.
  9. Open the 'Acuity report' form after 6 minutes from the 'Start Time' defined in the 'System Task Scheduler'.
  10. Set the 'Acuity date' to desired date.
  11. Select client's admission unit from the 'Unit' drop down.
  12. Click [Submit].
  13. Review the report.
  14. Verify the client is displayed in the report with correct scores as defined in the 'Acuity Rule Definition' form.
Topics
• RADplus Utilities • NX • Client Acuity
2021 Update 128 Summary | Details
Avatar NX - ScriptLink
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
Scenario 1: Avatar NX - Form designer 'ScriptLink' configuration, functionality and logging
Specific Setup:
  • Have a form [FormA] containing one or more fields, For this example a modeled form is used with dictionary field [FieldA], containing several values
  • Have a "ScriptLink" script created and added to the system. For example, a script that will display a message when a value is selected in a field. For this example, [ValueB] in [FieldA] is used
  • Have the "WSDL" for the script exported and ready for import
Steps
  1. Open "Form Designer" and select [FormA]
  2. In the "Tabs" field, select the tab
  3. Click [Show Tab]
  4. Click "Settings"
  5. Populate the "Import WSDL for ScriptLink" field
  6. Click "Import" and click [OK]
  7. Click the 'Verbose' radio button 12
  8. Uncheck the 'Disable All Scripts for Form' checkbox
  9. Uncheck the 'Disable All Scripts for Error' checkbox
  10. Click [Return To Designer]
  11. Click the [Save] button and then click [Yes]
  12. Click the [OK]
  13. Select the field [FieldA], on the form that will be used to trigger the script
  14. In the 'Properties' pane on the left side, double-click "ScriptLink"
  15. Click [Edit]
  16. Select the script from the "Available Scripts" drop down list
  17. Populate the 'Script Parameter' input box with the parameter needed to trigger the script (if applicable)
  18. Click [Apply]
  19. Click [Save]
  20. Click [Submit]
  21. Open [FormA]
  22. Navigate to [FieldA], set with the "ScriptLink" script
  23. Select the value in the field needed to trigger the script. In this example [ValueB]
  24. Validate the message configured in the script, is displayed as expected. (Note the date and time the message was displayed)
  25. Close the form
  26. Repeat steps 1 thru 4
  27. Click the 'Print Scripts for This Form' button
  28. Validate the report contains script name imported on step 6
  29. Close the report
  30. Back on the "Settings" page, navigate to the "ScriptLink Logs" section
  31. Populate the "From Date & Time" field and the "To Date & Time" field with the date and time noted in step 24
  32. Click and select the row in the drop down list
  33. Validate the "Radplus Script Log" report contains the expected run date/time and script execution logging information, for the event triggered in step 24
Topics
• Forms Designer • NX
2021 Update 132 Summary | Details
Launching Hyperlinks from a modeled form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
  • Form Definition (CWS)
Scenario 1: Validate launching "Hyperlinks" from a Modeled Form
Specific Setup:
  • Have a modeled form [FormA], that contains a "Label" object configured in "Form Definition" with a valid hypertext link, for example " https://www.google.com/"
  • [UserA] has access to the modeled form
  • [UserA] has access to "Form Designer"
  • [UserA] has access to "Form Definition"
  • Login as [UserA]
Steps
  1. Open [FormA]
  2. Navigate the label containing the hyperlink
  3. Click on the hyperlink
  4. Validate the expected web page is launched successfully
  5. Open "Form Designer"
  6. Select [FormA]
  7. Navigate to the label containing the hyperlink
  8. Move the hyperlink to a new location on the form
  9. Submit the form
  10. Repeat steps 1 thru 3
  11. Validate results are as expected
  12. Open "Form Definition"
  13. Select [FormA]
  14. Navigate to the label containing the hyperlink
  15. Change the hyperlink to a new web page
  16. Submit the form
  17. Repeat steps1 thru 3
  18. Validate results are as expected
  19. Open "Form Designer"
  20. Select [FormA]
  21. Navigate to the label containing the hyperlink
  22. Edit the HTML code for the label. For this example "<html><font face=SansSerif style="font-size: 12pt;", is used to change the font size
  23. Submit the form
  24. Open [FormA]
  25. Navigate the label containing the hyperlink
  26. Validate the font size of the text is as expected
  27. Click on the hyperlink
  28. Validate the expected web page is launched successfully
Topics
• Modeling • Forms Designer • NX
2021 Update 133 Summary | Details
Documents- console widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
  • Delete Document
Scenario 1: "Documents" type Console widget - validate functionality
Specific Setup:
  • Have the system configured with a sub system code [SubcodeA]
  • [SubcodeA] is assigned only to [ProgramA]
  • [UserA] only has access to [SubCodeA]
  • [UserA] has access to form "User Definition" and form "Delete Document"
  • [ClientA] is admitted to [ProgramA] in "Episode1"and also to [ProgramB] in "Episode2"
  • [FormA] is enabled for document routing with document type [DocA], assigned in form "Document Routing Setup"
  • A document "DocumentA", has been created for [ClientA] in "Episode1", using [FormA]
  • Another document "DocumentB", has been created for [ClientA] in "Episode2", using [FormA]
  • Have a "Documents" console widget created using form, "Console Widget Definition" with document type [DocA] included to display in the widget
  • Have the "Documents" widget placed on the home view for [UserA]
  • Have the "My To Do's widget placed on the home view for [UserA]
  • [UserA] has logged into [SubcodeA]
Steps
  1. Select [ClientA]
  2. In the 'Episode Selection' at the top of the home view, select "All" episodes
  3. Validate "DocumentA" filed in [Episode1] is displayed in the "Documents" widget
  4. Validate "DocumentB" filed in [Episode2] is 'not' displayed in the "Documents" widget, as sub system code does not have access to the program used to generate
  5. Open form "User Definition" and select [UserA] for edit
  6. In the "Document Management" section, click on field "Specify Forms", deselect document type [DocA]
  7. Submit the form
  8. Re-fresh the "Documents" widget
  9. Validate "DocumentA" filed in [Episode1] is no longer displayed in the "Documents" widget as access to document type [DocA] used in "DocumentA" has been removed
  10. Validate "DocumentB" filed in [Episode2] is 'not' displayed in the "Documents" widget, as sub system code does not have access to the program used to generate
  11. Repeat step 5 thru 7, this time returning access to [DocA] for [UserA]
  12. Re-fresh the "Documents" widget
  13. Validate "DocumentA" filed in [Episode1] is displayed in the "Documents" widget
  14. Validate "DocumentB" filed in [Episode2] is 'not' displayed in the "Documents" widget, as sub system code does not have access to the program used to generate
  15. Open form "Delete Document"
  16. Select "Client" in the "Entity Type" field
  17. Select "Individual" in the "Include" field
  18. In the "Entity" field, select the [ClientA]
  19. Select [EpisodeA] in the "Episode" field where the document was filed
  20. Click [Form Search]
  21. Select the [FormA] in the "Select a Form" screen
  22. Click "OK"
  23. Click the "Select Form" drop down list
  24. Select the row pertaining to the document in "Episode1" for [UserA]
  25. Click [Delete]
  26. Click [Yes], confirming the deletion
  27. In the 'Episode Selection' at the top of the home view, select "All" episodes
  28. Click the "Refresh" button on the "Documents Widget"
  29. Validate "DocumentA" filed in [Episode1], is no longer present in the list
Topics
• Document Management • NX
2021 Update 134 Summary | Details
Export Reports Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Export Crystal Report File (PM)
  • Export Crystal Report File (MSO)
  • Export Crystal Report File (CFMS)
Scenario 1: Validate form "Export Crystal Report File"
Steps
  1. Open form "Export Crystal Report" form in application "PM"
  2. In the "Report Type" field, select the "Command Button Report"
  3. Click the "Select Report" field drop down list
  4. Select any desired report from the list [ReportA] (Note: A system may not have any reports for export)
  5. Click [Export Report]
  6. In the "Save" dialog, click the "Save In" field and navigate to a desired folder location [FolderA],
  7. Click [Save]
  8. Open "File Explorer" and navigate to [FolderA]
  9. In the "File Name" column, double click on [ReportA] to open the report
  10. Validate the report opens successfully
  11. Close the report
  12. In the "Report Type" field, select "Disclosure Management Report"
  13. Repeat steps 2 and 3
  14. Validate results are as expected
  15. In the "Report Type" field, select "Menu Report"
  16. Repeat steps 2 and 3
  17. Validate results are as expected
  18. In the "Report Type" field, select "Document Routing Report"
  19. Repeat steps 2 and 3
  20. Validate results are as expected
  21. In the "Report Type" field, select "Report Definition Report"
  22. Repeat steps 2 and 3
  23. Validate results are as expected
  24. In the "Report Type" field, select "RADplus Report"
  25. Repeat steps 2 and 3
  26. Validate results are as expected
  27. Close the form
  28. Open form "Export Crystal Report" form in application "CWS" (If applicable)
  29. Repeat steps 2 thru 9
  30. Validate results are as expected
  31. Open form "Export Crystal Report" form in application "MSO" (If applicable)
  32. Repeat steps 2 thru 9
  33. Validate results are as expected
  34. Open form "Export Crystal Report" form in application "CFMS" (If applicable)
  35. Repeat steps 2 thru 9
  36. Validate results are as expected
Topics
• Query/Reporting • NX
2021 Update 140 Summary | Details
State Form Tools - Import Data
Scenario 1: State Form Tools - Data Import functionality
Specific Setup:
  • Have two modeled forms, for this example one is called 'Parent Form' and the other 'Child Form' each form.
  • Have a "State Form Definition" [Defintion1], set up by Netsmart, that is configured to execute a data import from the "Child" form to the "Parent form" when the "Child" form is submitted. (For this test, [Definition1] uses the "Program" field (which exists on both forms) as a link to update the data filed in "Date" and "Time" fields on the "Parent" form)
  • Have Netsmart set up a "Programmer Override" on the "Child" form that will compile [Definition1] which then executes the data import
Steps
  1. Select a client [ClientA]
  2. Open the 'Parent Form' form
  3. Click on the "Program" field and select a program [ProgramA]
  4. Populate the "Date" and "Time" fields on the form. (Note the date and time values)
  5. Submit the form
  6. Open the 'Child Form' form for [ClientA]
  7. In the "Program" field, select the same program filed in the "Parent" form, [ProgramA]
  8. Populate other desired fields on the form
  9. Submit the form. (Note the date and time of the submission)
  10. Open the 'Parent Form' form
  11. Select the row filed in step 5
  12. Validate the "Date" and "Time" fields are now populated with the date and time noted in step 9
Topics
• NX • State Form Tools
2021 Update 147 Summary | Details
Form Definition
Scenario 1: Modeling- validate event logic 'Focus' functionality
Specific Setup:
  • Have a modeled form[FormA] with two tables a "Primary" table and a "Multiple Iteration" table
  • [FormA] has three sections:
  • [SectionA] contains a single select dictionary field "SingleA" and scrolling text field "ScrA" from the "Primary" table
  • [SectionB] contains a single select dictionary field "SingleB" and scrolling text field "ScrB" from the "Primary" table
  • [SectionM] contains a single select dictionary field "SingleM" and scrolling text field "ScrM" from the "Multiple Iteration" table
  • In [SectionA]
  • Have a "Set Focus on Specific Object on Event" type event set on field "SingleA", to set cursor focus on field "ScrA" when "ValueA" is selected in field "SingleA"
  • Have a "Set Focus on Specific Object on Event" type event set on field "SingleA", to set cursor focus on field "ScrB" when "ValueB" is selected in field "SingleA"
  • In [SectionB]
  • Have a "Set Focus on Specific Object on Event" type event set on field "SingleB", to set cursor focus on field "ScrB" when "ValueA" is selected in field "SingleB"
  • Have a "Set Focus on Specific Object on Event" type event set on field "SingleB", to set cursor focus on field "ScrA" when "ValueB" is selected in field "SingleB"
  • In [SectionM]
  • Have a "Set Focus on Specific Object on Event" type event set on field "SingleM", to set cursor focus on field "ScrM" when "ValueA" is selected in field "SingleM". [Note: For "Multiple Iteration" sections, focus events can only be set to focus on fields on the multiple iteration section itself, not on fields that exist in other sections of the form]
  • [Please Note: "Focus" event functionality in Modeling is not yet supported in "Avatar NX"]
Steps
  1. Access [FormA].
  2. Select [SectionA]
  3. In field "SingleA", select "ValueA"
  4. Validate cursor focus is set on field "ScrA"
  5. In field "SingleA", select "ValueB"
  6. Validate cursor focus jumps to "SectionB" and is set on field "ScrB", as expected
  7. Select [SectionB]
  8. In field "SingleB", select "ValueB"
  9. Validate cursor focus jumps to "SectionA" and is set on field "ScrA", as expected
  10. In field "SingleB", select "ValueA"
  11. Validate cursor focus is set on field "ScrB"
  12. Select [SectionM]
  13. In field "SingleM", select "ValueA"
  14. Validate cursor focus is set on field "ScrM".
Modeled Forms - with 'Table Alias' configured
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Diagnosis
Scenario 1: Modeled Forms - "Table Alias" field and data validations
Specific Setup:
  • Have a client [ClientA], with an existing inpatient episode [EpisodeA]
  • The registry setting 'Require Present on Admission Indicator on Inpatient Episodes' is set to "Yes".
  • Have a modeled form [FormA], that includes a "Diagnosis-IMO Mapped Search" field [FieldA], that is mapped to the "Diagnosis Search" field on the "Diagnosis" form set by using the "Table Alias" and "Column Mapping" functionality in "Table Definition
  • FormA also includes these field mapped from the "Diagnosis" using "Table Alias" functionality
  • A dictionary field [FieldB] mapped to the "Type Of Diagnosis" field.
  • A dictionary field [FieldC] mapped to the "Present on Admission Indicator" field
  • A dictionary field [FieldD] mapped to the "Status" field
  • A dictionary field [FieldE] mapped to the "Diagnosing Practitioner" field
  • Have a crystal report [ReportB] to display the data filed in the "SYSTEM.client_diagnosis_record" table
  • Have access to the "Diagnosis" form
Steps
  1. Open [FormA]
  2. Select [ClientA]
  3. Select [EposideA]
  4. Select a value [FieldA]
  5. Select a value [FieldB]
  6. Don't select a value in [FieldC]
  7. Select a value [FieldD]
  8. Select a value [FieldE]
  9. Submit [FormA]
  10. Validate a submission error stating "Present On Admission Indicator" is missing" is displayed
  11. Click [OK]
  12. Select a value [FieldC]
  13. Submit the form
  14. Validate the form files successfully
  15. Open the "Diagnosis" form
  16. Select [ClientA]
  17. Select [EposideA]
  18. Select the diagnosis row in the "Diagnosis" grid
  19. Validate the "Type of Diagnosis" field at the top of the form contains the value filed in [FieldB]
  20. Below the "Diagnosis" grid, validate the "Diagnosis Search" field contains the value filed in [FieldA]
  21. Validate the "Status" field contains the value filed in [FieldD]
  22. Validate the "Present on Admission Indicator" field contains the value filed in [FieldC]
  23. Validate the "Diagnosing Practitioner" field contains the value filed in [FieldE]
  24. Generate the [ReportB] to display the data filed in the "SYSTEM.client_diagnosis_record" table
  25. Locate the record for [ClientA]. [EpisodeA]
  26. Validate data displayed contains the field values selected and submitted in steps 4 thru 12
Console Widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView - Console Widget Viewer
Scenario 1: Validate "Console" widget column data
Specific Setup:
  • Have a "Console" widget [WidgetA] created in form "Console Widget Configuration" for any form [FormA], For example the "Inpatient Progress Notes" form.
  • Include the field "Practitioner (7000)" and any other desired fields in the widget
  • Have the [WidgetA] placed on a home view for [UserA]
  • Have the "Console Widget Viewer" widget on a home view for [UserA]
  • Log in as [UserA]
Steps
  1. Open [FormA]
  2. Select [EpisodeA]
  3. Select [ClientA]
  4. Click to add a new row
  5. Populate all required fields
  6. In the "Practitioner" field, populate the field with a valid practitioner.
  7. Populate any other desired fields
  8. Submit the form
  9. Validate the form files successfully
  10. Select [EpisodeA] in the "Episodes" drop down list on the home view
  11. Click the [WidgetA] refresh button
  12. Validate the "Practitioner" column contains the practitioner name along with the practitioner's staff ID number.
  13. Validate all other columns chosen for the widget in the set up are populated, as expected
  14. Click the [View] button
  15. Validate the "Console Widget Viewer" widget, is populated with all the expected field values
Topics
• Modeling • NX • Diagnosis
2021 Update 149 Summary | Details
To Do's Widget - reassigning routed documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Approver Override
Scenario 1: My To Do's Widget - Reassign a To Do routed for Approval
Specific Setup:
  • Have a form enabled for document routing [FormA]
  • [FormA] has been submitted today for [ClientA] and routed to [UserA], who is a staff member
  • Have a second user who is also a staff member [UserB]
  • [UserA] and [UserB] have the "My To do's" widget on their home view"
  • Log in as [UserA]
Steps
  1. Navigate to the "My To Do's" widget and click on the "New" tab
  2. In the "Client" column,
  3. Locate the To Do routed in form [FormA], for [ClientA]
  4. Validate the "Sent" column, validate the date
  5. Right-click on the "Approve Document" link and then click Reassign"
  6. In the "Continue" dialog, click [OK] to proceed to the "Approver Override" form
  7. In the "Approver Override" form
  8. Validate the "Entity" field contains [ClientA]
  9. Validate the "From Date" and the "To Date" contains today's date
  10. Click the drop down list in the field "List of Document" and select the row
  11. Validate the row contains the "Option" field populated with "FormA" and the "Date Created" field populated with today's date, as expected
  12. Click [Update Approvers]
  13. In the "Route Document To" dialog, deselect [UserA] as an approver in the approver list
  14. In the "Add Approver" field search for [UserB] and then click [Add] to add the user to approver list
  15. Click [Submit]
  16. Close the form
  17. Validate the To Do reassigned, is removed from the "My To do's" widget for [UserA]
  18. Log out as [UserA] and then log in as [UserB]
  19. Navigate to the "My To Do's" widget and click on the "New" tab
  20. Click the "Refresh" button in the widget
  21. Validate the To Do reassigned to [UserB] for approval in the step 2, is present in the list
  22. Click [Approve Document]
  23. In the "Approve Document" form, click [Sign] to approve the document
  24. Validate the To Do is removed from the "My To Do's" widget for [UserB]
Document Management Definition - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field
  6. Select the desired entity in the "Entity" field
  7. Populate any other desired fields in the "Form" section
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report"
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section
  19. Click [File].
  20. Validate the form files successfully
  21. Click [Select Form].
  22. Select the form just submitted in 5
  23. Validate all fields populated in steps 1 thru 5, are populated as expected
  24. Click back to the [Form] section
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list
  29. Click [Select Form].
  30. Select the form "Inbox Attachments"
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed."
  33. Click [OK]
  34. Click [Select Form].
  35. Select the form "Results Document"
  36. Click [Delete]
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed."
  38. Click [OK]
  39. Close the form
Topics
• NX • My To Do's
2021 Update 155 Summary | Details
'Change User Role ID' - support for other modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
  • User Permissions for Multiple Iteration Tables
  • Change User Role ID
  • User Definition
  • User Merge
Scenario 1: User Permissions for Multiple Iteration Tables - Change User Role ID
Specific Setup:
  • The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
Steps
  1. Access the 'User Role Definition' form.
  2. Enter "PermissionsNEW" in the 'User Role ID' field.
  3. Populate all required fields.
  4. Click [Submit] and [No].
  5. Access the 'User Permissions for Multiple Iteration Tables' form.
  6. Select "PermissionsNEW" in the 'User Role' field.
  7. Select "Add" in the 'Add/Edit/Delete Permission' field.
  8. Select "Family Registration (Family Members)" in the 'Forms' field.
  9. Select "Add" in the 'Select Permissions' field.
  10. Click [Update Table].
  11. Validate a message is displayed stating "Filed Successfully".
  12. Click [OK] and validate the 'Permissions Table' contains the permission added.
  13. Close the form.
  14. Access the 'Change User Role ID' form.
  15. Select "PermissionsNEW" in the 'User Role' field.
  16. Validate the 'Current User Role ID' field contains "PermissionsNEW".
  17. Enter "PermissionsTEST" in the 'New User Role ID' field.
  18. Click [Submit].
  19. Validate a message is displayed stating "Change User Role ID has completed. Do you wish to return to form?"
  20. Click [No].
  21. Access the 'User Permissions for Multiple Iteration Tables' form.
  22. Validate the 'User Role' field contains "PermissionsTEST" and no longer contains "PermissionsNEW".
  23. Select "PermissionsTEST" in the 'User Role' field.
  24. Validate the 'Permissions Table' contains the permission filed in the previous steps indicating the user role ID has been updated successfully.
  25. Close the form.
Scenario 2: User Permissions for Multiple Iteration Tables - Change User ID
Specific Setup:
  • The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
Steps
  1. Access the 'User Definition' form.
  2. Enter "TestPermissions1" in the 'User ID' field.
  3. Enter "Test Permissions 1" in the 'User Description' field.
  4. Select "Yes" in the 'Is this user a system administrator' field.
  5. Select "No" in the 'Associate User with a User Role' field.
  6. Select the "Forms and Tables" section.
  7. Select the desired system codes in the 'System Code(s)' field.
  8. Click [Submit] and [No].
  9. Access the 'User Permissions for Multiple Iteration Tables' form.
  10. Select "TestPermissions1" in the 'User' field.
  11. Select "Add" in the 'Add/Edit/Delete Permission' field.
  12. Select "Financial Eligibility (Guarantor Selection)" in the 'Forms' field.
  13. Select "Add" in the 'Select Permissions' field.
  14. Click [Update Table].
  15. Validate a message is displayed stating "Filed Successfully".
  16. Click [OK] and validate the 'Permissions Table' contains the permission added.
  17. Close the form.
  18. Access the 'Change User ID' form.
  19. Select "Test Permissions 1 (TestPermissions1)" in the 'User' field.
  20. Enter "TestPermissions" in the 'New User ID' field.
  21. Validate the 'Old User ID' field contains "TestPermissions1".
  22. Click [Submit].
  23. Validate a message is displayed stating "Change User ID has completed. Do you wish to return to form?"
  24. Click [No].
  25. Access the 'User Permissions for Multiple Iteration Tables' form.
  26. Validate the 'User' field contains "TestPermissions" and no longer contains "TestPermissions1".
  27. Select "TestPermissions" in the 'User' field.
  28. Validate the 'Permissions Table' contains the permission filed in the previous steps indicating the user ID has updated successfully.
  29. Close the form.
Scenario 3: User Permissions for Multiple Iteration Tables - User Merge
Specific Setup:
  • The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
Steps
  1. Access the 'User Definition' form.
  2. Enter "Merge1" in the 'User ID' field.
  3. Enter "Merge Test 1" in the 'User Description' field.
  4. Select "Yes" in the 'Is this user a system administrator' field.
  5. Select "No" in the 'Associate User with a User Role' field.
  6. Select the "Forms and Tables" section.
  7. Select the desired system code(s) in the 'System Code(s)' field.
  8. Click [Submit] and [No].
  9. Access the 'User Permissions for Multiple Iteration Tables' form.
  10. Select "Merge1" in the 'User' field.
  11. Select "Add" in the 'Add/Edit/Delete Permission' field.
  12. Select "Financial Eligibility (Guarantor Selection)' in the 'Forms' field.
  13. Select "None" in the 'Select Permissions' field.
  14. Click [Update Table].
  15. Validate a message is displayed stating "Filed Successfully".
  16. Click [OK] and validate the 'Permissions Table' contains the permission added.
  17. Close the form.
  18. Access the 'User Merge' form.
  19. Select "New" in the 'Merge Into New Or Existing User' field.
  20. Enter "Merge2" in the 'New User ID' field.
  21. Enter "Merge Test 2" in the 'New User Description' field.
  22. Select "Merge Test 1 (Merge1)" in the 'Source User 1' field.
  23. Click [Submit] and [No].
  24. Access the 'User Permissions for Multiple Iteration Tables' form.
  25. Validate the 'User' field contains "Merge2" and no longer contains "Merge1".
  26. Select "Merge2" in the 'User' field.
  27. Validate the 'Permissions Table' contains the permission filed in the previous steps indicating the user permissions have been merged successfully.
  28. Close the form.
Topics
• Change User Role Id • User Permissions for Multiple Iteration Tables • Change User ID • User Merge
2021 Update 156 Summary | Details
State Form Tools
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: State Form Definition - Field and data validation's
Specific Setup:
  • Have any existing state form definition defined in form "State Form Definition" [DefinitionA] that contains a main record [Main] and a sub record [Sub]
  • The main record contains data fields from the "SYSTEM.patient_current_demographics" table that includes the "patient_name" field
  • Have a client on the system with a name that includes an "underscore". [ClientA]
Steps
  1. Open the 'State Form Definition' form
  2. Select "Existing" in the 'New or Existing' field
  3. Select the [DefinitionA] from the 'Select State Form' field drop down list
  4. Click the [Record Definition] section
  5. Select "Update" in the "Add or Update Record" field
  6. Select the [Main] record in the "Select Record" field
  7. Click [Define Record Data Elements]
  8. Select the row that contains the clients name field
  9. Double-click in the "Format" column input field
  10. In the search results grid, scroll down the "Code" column and select the code "TXT9" (Remove Underscores)
  11. Click [Save] to save the changes
  12. Select the [Sub] record in the "Select Record" field
  13. Click [Define Record Data Elements]
  14. Double-click in the "Force Error Condition" field
  15. Populate the field, for this example, "p2.PATID=1"
  16. Double-click in the "Default Error Message" field
  17. Populate the field with a value, for this example "Test"
  18. Click [Save] to save the changes
  19. Click [Define Record Data Elements] to return to the grid
  20. Validate the "Force Error Condition" field contains the expected value
  21. Double-click in the "Force Error Condition" field, remove the current value and click [OK]
  22. Validate the field is empty
  23. Validate the "Default Error Message" field contains the expected value
  24. Double-click in the "Default Error Message" field, remove the current value and click [OK]
  25. Validate the field is empty
  26. Click [Save] to save the changes
  27. Open form "State Form File Generation" form
  28. In the field "State Form", select [DefinitionA]
  29. In the "File Generation Options" field, select "Compile"
  30. Click [Process]
  31. In the "File Generation Options" field, select "Create File on Server"
  32. Click [Process]
  33. In the "Save In" dialog, select a folder location to save the file [LocationA]
  34. Set the "File Name" field to desired file name [DefinitionFileA]
  35. Click [Save]
  36. Open "Windows Explorer", and navigate to the location of the file [LocationA]
  37. Right-click on [DefinitionFileA] to open the file
  38. Search for [ClientA]
  39. Validate the name displayed for [ClientA] does not contain any underscores, as expected
Topics
• State Form Tools