Skip to main content

RADplus 2023 Monthly Release 2023.02.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 8 Summary | Details
myClients widget - Room numbers removed after Discharge
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Admission
  • Discharge
  • Delete Last Movement
Scenario 1: 'Include Active Room Number with Client Name' Registry Setting - validate room number is omitted from myClient's widget when client is removed from bed
Specific Setup:
  • A room and bed must be configured via the 'Maintain Hospital Bed File' form.
  • The 'My Clients' widget must be added to the 'HomeView' of the user logged into the application.
Steps
  1. Access the ‘Registry Settings’ form.
  2. Set the ‘Select Registry Setting’ field to “Include Active Room Number”.
  3. Set the ‘RADplus->General->Facility->->->Include Active Room Number With Client Name’ registry to “3,1&BED”.
  4. Close the form.
  5. Log out of the application and log back in.
  6. Validate the 'My Clients' widget contains the room number and bed in the following format:
  7. Room number followed by a "." and the bed number.
  8. Select the test client in 'myClients' widget and access the ‘Admission’ form.
  9. Select the episode in the ‘Episode’ pre-display and click [Edit].
  10. Validate the client header contains the room number next to the client name.
  11. Close the form.
  12. Access the 'Discharge' form.
  13. Select the text client and submit the discharge.
  14. Access the 'Delete Last Movement' form.
  15. Select the test client and delete the last movement record (discharge).
  16. Validate room number doesn't display next to the client name when selected in 'myClients' widget.
Topics
• Widgets
Update 57 Summary | Details
Console Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Scheduling Calendar
Scenario 1: Scheduling Calendar - Delete Individual and Group Appointments
Specific Setup:
  • A client has an existing appointment scheduled (Client A).
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Validate the 'Appointment Grid' contains the appointments for "Client A" and "Group A".
  3. Right click on the appointment for "Client A" and click [Delete].
  4. Validate a "Delete Appointment" dialog is displayed stating: Are you sure?
  5. Click [Yes].
  6. Validate the 'Appointment Grid' no longer contains the appointment for "Client A".
  7. Click [Dismiss].
Topics
• Console Widget • NX • Scheduling Calendar
Update 71 Summary | Details
User Definition - User External Login
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
Scenario 1: User Definition (Field Validation) - Enable/Disable a "Netsmart Identity and Access Management(NIAM)" User
Specific Setup:
  • Have registry setting "Enable OpenID Connect Support" enabled in the system by Netsmart
  • The system has been configured for (NIAM) functionality with the appropriate settings configured in the "OpenID Connect Configuration" section of form "System Security Defaults"
  • An "(ODIC) Identity Provider" solution is enabled that will be used in conjunction with Avatar to authenticate a user set up as a "NAIM" user
  • [NIAMuser] has been assigned an external login ID and password by "(ODIC) Identity Provider" to enable login as a "NIAM" user, once they are configured in "myAvatar"
  • The logged in user has permissions to add and edit users in form "User Definition"
Steps
  1. Open form "User Definition"
  2. Enter a new user ID or existing user [NIAMuser] in "User ID" field, that will be enabled as a "NIAM" user
  3. Click the "Yes" in the "Use External Login" field
  4. Set the "External Login ID' field to the external login name assigned to [NIAMuser]
  5. Validate there is no value in "System Generated Password" field and the field is disabled
  6. Validate there is no value in "Password Term Duration (Days)" field and the field is disabled
  7. Validate there is no value in "Reminder Notice Number of Days" field and the field is disabled
  8. Validate the "Allow User Renewal" selection field is disabled
  9. Populate any other required and/or desired fields on the form
  10. Submit the form
  11. Validate the form files successfully
  12. Re-open form "User Definition"
  13. Select the [NIAMUser] just updated in step 1
  14. Validate the "Use External Login" field is set to "Yes"
  15. Validate there is no value in "System Generated Password" field and the field is disabled
  16. Validate there is no value in "Password Term Duration (Days)" field and the field is disabled
  17. Validate there is no value in "Reminder Notice Number of Days" field and the field is disabled
  18. Validate the "Allow User Renewal" selection field is disabled
  19. Validate the values of any other required and/or desired fields populated in step 1, are as expected
  20. Navigate back to the "Use External Login" field and set the value to "No"
  21. Validate the "System Generated Password" field is now enabled
  22. Populate the field with a desired password or click the [Generate New Password] button to auto generate a new password
  23. Validate the "Password Term Duration (Days)" field is now enabled
  24. Populate the field with a desired value
  25. Validate the "Reminder Notice Number of Days" field is now enabled
  26. Populate the field with a desired value
  27. Validate the "Allow User Renewal" selection field is now enable
  28. Select the desired value in the field
  29. Validate all other fields populated in step 2a, are still populated as expected
  30. Submit the form
  31. Validate the form files successfully
  32. Re-open form "User Definition"
  33. Select the [NIAMUser] just updated in step 2
  34. Validate all fields in step 2b are still enabled and populated as expected
  35. Validate all other fields populated as expected
  36. Navigate back to "Use External Login" field and set the value back to "Yes" again
  37. Validate the "External Login ID" field is populated with the login name assigned to [NIAMuser]
  38. Validate the value in "System Generated Password" field is cleared and the field is disabled
  39. Validate the value in "Password Term Duration (Days)" field is cleared and the field is disabled
  40. Validate the value in the "Reminder Notice Number of Days" field is cleared and the field is disabled
  41. Validate the "Allow User Renewal" selection field is still selected but the field is disabled
  42. Validate all other fields on the form are populated as expected
  43. Submit the form
  44. Validate the form files successfully
  45. Re-open form "User Definition"
  46. Select the [NIAMUser] just updated in step 3
  47. Validate all fields in step 3b are still populated as expected and disabled
  48. Validate all other fields populated as expected
  49. Close the form


Envelope Import - Doc Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (CWS)
  • Envelope Import (CWS)
  • Document Routing Setup (PM)
Scenario 1: Envelope Import - Validate importing "Document Routing" enabled forms
Specific Setup:
  • Have an envelope [DocEnvA] with a modeled form [DocFormA] that is enabled for document routing in form "Document Routing Setup' and has the following prompts set in the "Acknowledgments" section of the form:
  • Prompt 'Acknowledgement Allowed' set to 'Yes'
  • All other prompts in the section are not populated
  • Have an envelope [DocEnvB] with a modeled form [DocFormB] that is enabled for document routing in form "Document Routing Setup' and has the following prompts set in the "Acknowledgments" section of the form
  • Prompt 'Acknowledgement Allowed' set to 'No
  • All other prompts in the section are disabled, as expected
Steps
  1. Open form "Envelope Export".
  2. At the "Select Envelope" prompt, select [DocEnvA]
  3. Click [Begin Export].
  4. At "File Explorer" dialog, navigate to a desired folder location to save the export file
  5. In the "File_Name" field, enter the desired name for the export file or use the default name already populated
  6. Click [Save].
  7. Close the form.
  8. Open form "Envelope Import"
  9. Click [Select Envelope Import File]
  10. In "File Explorer, navigate to the location of [DocEnvA] and select the file
  11. Click [Overwrite Existing]
  12. Click [Begin Import Scan]
  13. Validate the import scan contains no errors or warnings related to "Acknowledgement" related fields
  14. Click [Begin Import]
  15. Validate the envelope imports successfully
  16. Open form "Document Routing Setup"
  17. Click [Select Form] and select [DocFormA]
  18. Navigate to the "Acknowledgement" section of the form
  19. Validate prompt 'Acknowledgement Allowed' set to 'Yes', as expected
  20. Validate all the other prompts in the section are not populated, as expected
  21. Open form "Envelope Export".
  22. At the "Select Envelope" prompt, select [DocEnvB]
  23. Click [Begin Export].
  24. At "File Explorer" dialog, navigate to a desired folder location to save the export file
  25. In the "File_Name" field, enter the desired name for the export file or use the default name already populated
  26. Click [Save].
  27. Close the form.
  28. Open form "Envelope Import"
  29. Click [Select Envelope Import File]
  30. In "File Explorer, navigate to the location of [DocEnvB] and select the file
  31. Click [Overwrite Existing]
  32. Click [Begin Import Scan]
  33. Validate the import scan contains no errors or warnings related to "Acknowledgement" related fields
  34. Click [Begin Import]
  35. Validate the envelope imports successfully
  36. Open form "Document Routing Setup'
  37. Click [Select Form] and select [DocFormB]
  38. Navigate to the "Acknowledgement" section of the form
  39. Validate prompt 'Acknowledgement Allowed' set to 'No', as expected
  40. Validate all the other prompts in the section are disabled, as expected
Console Widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
Scenario 1: Validate "Console" Widgets using a "SQL Query Override"
Specific Setup:
  • Have registry setting "Enable Console Widgets/Views" is set to "Y"
  • In form "Console Widget Configuration", create a console widget [TestWidget] for any desired form, for this test the "Admission" form is used:
  • In the "SQL Query Override" section, populate the field with a valid SQL query to display date. For this example, the following query is used: SELECT <LINK:PATIENT510:PATID:EPN_uniqueid:EPISODE_NUMBER>PATID,EPISODE_NUMBER, EPN_uniqueid, preadmit_admission_date FROM SYSTEM.episode_history WHERE FACILITY=?FACILITY AND PATID=?PATID
  • Have a client [TetClient] who is admitted in two active episodes. [EpisodeA] and [EpisodeB]
  • Have [TestWidget] and the "Console Widget Viewer" widget added to the logged in user's home view
Steps
  1. At the home view, select [TestClient]
  2. Select [EpisodeA] in the "Episodes" drop down list
  3. Navigate to [TestWidget]
  4. Validate a row is display with admission data for [TestClient] for the [EpisodeA], as expected
  5. Click the [Open Record] button.
  6. Validate the "Admission" form opens for edit and displays the data for [EpisodeA], as expected.
  7. Close the form
  8. Click the [View] button in the row
  9. Validate the "Console Widget Viewer" display data for [EpisodeA], as expected
  10. Click the [Open Record] button in the console viewer
  11. Validate the "Admission" form opens for edit display data for [EpisodeA], as expected
  12. Close the form
  13. Navigate back to the home view
  14. Select [EpisodeB] in the "Episodes" drop down list
  15. Navigate to [TestWidget]
  16. Validate a row is display with admission data for [TestClient] for the [EpisodeB], as expected
  17. Click the [Open Record] button.
  18. Validate the 'Admission" form opens for edit and displays the data for [EpisodeB], as expected.
  19. Close the form
  20. Click the [View] button in the row
  21. Validate the "Console Widget Viewer" display data for [EpisodeB], as expected
  22. Click the [Open Record] button in the console viewer
  23. Validate the "Admission" form opens for edit display data for [EpisodeB], as expected
  24. Close the form
Envelope Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
  • Envelope Export (PM)
Scenario 1: Envelope Import - Importing an envelope containing "Form Designer" and "Form Definition" changes
Specific Setup:
  • Create a new modeled envelope [TestEnvelope] containing a form [TestForm] with two or more sections containing any desired field types

Steps
  1. Open form "Form Designer"
  2. Select [TestForm]
  3. Select [Section1]
  4. Make any kind of form designer change to the section and click [Save]
  5. Select [Section2]
  6. Make any kind of form designer change to the section and click [Save]
  7. Select [Section3]
  8. Make any kind of form designer change to the section and click [Save]
  9. Repeat the last step for any other sections
  10. Submit the form
  11. Validate submission is successful
  12. Open "Form Definition"
  13. Select [TestForm]
  14. Navigate to "Section Def" section
  15. Select any desired section and delete the section
  16. Submit the form
  17. Validate the form submits successfully
  18. Open form "Form Designer"
  19. Select [TestForm]
  20. Click the "Sections" field
  21. Validate the section deleted in the previous step is not present in the list, as expected
  22. Validate the other sections are still present in the list
  23. Close the form
  24. Open form "Envelope Export"
  25. Select [TestEnvelope]
  26. Set prompt "Include Form Designer changes?" to "Yes"
  27. Export the envelope and save the file
  28. Close the form
  29. Open form "Envelope Import"
  30. Select the file exported in the previous step
  31. Select "Overwrite Existing"
  32. Set prompt "Include Form Designer changes?" to "Yes"
  33. Click [Begin Import Scan]
  34. Validate there are messages blocking import
  35. Click [Begin Import]
  36. Validate import is successful
  37. Open form "Form Designer"
  38. Select [TestForm]
  39. Click the "Sections" field
  40. Validate the section deleted in step 2 is not present in the list, as expected
  41. Validate the other sections are still present in the list
  42. Open [TestForm]
  43. Validate the section removed in step 2 is no longer present, as expected
  44. Navigate to each of the other sections of the form
  45. Validate the form designer changes made in those sections in step 1 are present, as expected
  46. Populate fields on the other sections
  47. Submit the form
  48. Validate the form submits successfully
Modeled Form - Referral Sources
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Referral Source Contact
Scenario 1: Modeled Form (w/Primary Table "Date Sorted" )- field validations
Specific Setup:
  • In form "Envelope Definition" create or have an envelope [TestEnvelope], that is defined with "Referral Sources" entity database selected in the "Entity Database" field
  • In form "Table Definition" field create a table [TestTable], that is configured to used envelope [TestEnvelope] and has prompt "Is this Table Date or Order of Entry Sorted" set to "Date Sorted" and field "Column Name of Sort Date" populated with a desired column name [ReferralSortDate].
  • Include any other desired field types in the table
  • Have a modeled form [TestForm] created using table [TestTable] adding the desired columns from the table to the form. Note: the sort date column [RefferralSortDate] defined in step 2 will automatically be displayed as field on the form
  • In form "Referral Source Maintenance"
  • Have a "Referral Source" [RefSourceTestA] submitted that has a "Referral Source" code entered than includes an uppercase "P" character anywhere within its name along with any other desired characters
  • Have a "Referral Source" [RefSourceTestB] submitted that has a "Referral Source" code entered than does 'not' include an uppercase "P" character anywhere within its name along with any other desired character
Steps
  1. Open form [TestForm]
  2. In the "Select Referral Source" field, select [RefSourceTestA]
  3. Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
  4. Populate all other required and desired fields on the form
  5. Submit the form
  6. Validate the form submits successfully
  7. Re-open form [TestForm]
  8. In the "Select Referral Source" field, select [RefSourceTestA]
  9. At the "Pre-Display" screen, select the row just submitted in step 1
  10. Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
  11. Validate all other fields populated in step 1, are populated as expected
  12. Open form [TestForm]
  13. In the "Select Referral Source" field, select [RefSourceTestB]
  14. Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
  15. Populate all other required and desired fields on the form
  16. Submit the form
  17. Validate the form submits successfully
  18. Re-open form [TestForm]
  19. In the "Select Referral Source" field, select [RefSourceTestB]
  20. At the "Pre-Display" screen, select the row just submitted in step 3
  21. Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
  22. Validate all other fields populated in step 3, are populated as expected
Topics
• User Definition • NX • Document Routing • Envelope Import • Console Widget • Form Designer • Modeling • Referral
Update 72 Summary | Details
IRIS - updates
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • IRIS Terminal Session
  • IRIS System Management Portal
Scenario 1: Guardiant form - Field validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Have a user with access to the "Guardiant" form
Steps
  1. Open form "Guardiant"
  2. Click the "Guardiant Configuration" section
  3. Click [Test Connectivity]
  4. Validate message "Connectivity Test Successful" is displayed
  5. Click [OK]
  6. Click [Test Daily Collection]
  7. Click [Yes] to the warning message
  8. Validate message "Test Succeeded" is displayed
  9. Click [Test Metrics Collection]
  10. Click [Yes] to the warning message
  11. Validate message "Test Succeeded" is displayed
  12. Click "Export Configuration"
  13. In "File Explorer", select a directory to save file
  14. Click [Save]
  15. Go to the directory where the file was saved
  16. Open the "GuardiantConfiguration.txt" file
  17. Validate data is present in the file
Scenario 2: Windows "ODBC Data Source Administrator" - Validate successfully ODBC connection to Avatar database
Specific Setup:
  • Have a "Cache 2017" or "IRIS" Avatar database for testing
  • Have the "Host" name or "IPaddress" assigned to that system available for testing
  • Have a user [TestUser] who has ODBC SQL table access assigned in form "User Definition" or "User Role Definition"
Steps
  1. Open the Windows "ODBC Data Source Administrator" utility program
  2. Click "Add"
  3. Select the desired "ODBC" driver
  4. In the ODBC set up screen
  5. Populate the "Name" and "Description" fields with the desired value
  6. Populate the "Host", "Port" and "Cache Namespace" fields with the appropriate values to connect to the Avatar Database
  7. Populate the user name field with system code and user [TestUser] who has "ODBC" table access. For example "SBOX:Testuser"
  8. Populate the "Password" field with password assigned to [TestUser]
  9. Click [Test Connection]
  10. Validate the connections is successful
Topics
• Cache • Guardiant • NX • Database Management
Update 74 Summary | Details
Modeled Forms with 'Treatment Plan' selection leaf fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Drug Testing
  • Dynamic Forms - Document Routing - Route Document To
  • TO DO'S
  • DOCUMENTS TO REVIEW
  • Dynamic Form - Document To Review - Verify Password
  • Document Routing Setup (PM)
  • Table Definition (PM)
  • Dictionary Update (PM)
Scenario 1: Modeled forms - Validate Modeled form with 'Treatment Plan' selection leaf
Specific Setup:
  • A modeled form must be configured with a 'Treatment Plan' selection leaf that is initially enabled and required (Form A).
  • A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
Steps
  1. Select "Client A" and access "Form A".
  2. Validate the 'Treatment Plan' field label is required.
  3. Populate all fields except the 'Treatment Plan' selection leaf field.
  4. Select "Final" in the 'Draft/Final' field.
  5. Validate a message is displayed stating: The following required prompt(s) do not contain information: Treatment Plan.
  6. Click [OK].
  7. Validate a message is displayed stating: "Final" cannot be selected until all of the required prompts within the form contain information.
  8. Click [OK].
  9. Click [Select Treatment Plan Item].
  10. Select the desired treatment plan item(s) and click [Return].
  11. Validate the 'Treatment Plan' field contains the selected item(s).
  12. Select "Final" in the 'Draft/Final' field.
  13. Validate a message is displayed stating: Selecting "Final" prevents future edits.
  14. Click [OK] and [Submit].
  15. Select "Client A" and access "Form A".
  16. Select the record filed in the previous steps and click [Edit].
  17. Validate a message is displayed stating: The selection is set to "Final". Data may be viewed only.
  18. Click [OK].
  19. Validate all previously filed data is displayed.
  20. Validate the 'Select Treatment Plan Item' button is disabled.
  21. Close the form.
Topics
• Modeling • Treatment Plan • NX
Update 78 Summary | Details
Documents Console Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView.Documents.Console Widget
Scenario 1: Documents Console Widget - Column data validations
Specific Setup:
  • Have a client [TestClientA] who has existing documents on the system that were created on various dates and with various document types
  • Have another client [TestClientB] who has existing documents on the system that were created in different episodes
  • Have a "Documents" widget created [TestWidget] set up in form "Console Widget Configuration", configured to include all document types available in the "Document Types to Display" field
  • [TestWidget] is included on the logged in user's Home View
Steps
  1. At the Home View, select [TestClientA]
  2. Navigate to "Documents" console widget [TestWidget]
  3. Click the "Document Description" column header
  4. Validate all documents are listed and sorted by document description in ascending alphabetical order, as expected
  5. Click the "Document Description" column header again
  6. Validate all documents are listed and sorted by document description in descending alphabetical order, as expected
  7. Click the "Document Date" column header
  8. Validate all documents are listed and sorted by document date in ascending date order, as expected
  9. Click the "Document Date" column header again
  10. Validate all documents are listed and sorted by document date in descending date order, as expected
  11. At the Home View, select [TestClientB]
  12. Navigate back to "Documents" console widget [TestWidget]
  13. Click the "Document Episode" column header
  14. Validate all documents are listed and sorted by episode number in ascending numerical order, as expected
  15. Click the "Document Episode" column header again
  16. Validate all documents are listed and sorted by episode number in descending numerical order, as expected
Topics
• Console Widget • NX
Update 80 Summary | Details
Modeling - 'SYSTEM.radplus_envelope_info' table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (PM)
  • Document Routing Setup (PM)
  • Data Element Help Message Definition (PM)
  • Envelope Merge (PM)
  • Form Designer (PM)
  • Form Deletion (PM)
  • Table Deletion (PM)
  • Import Reports (PM)
  • Caseload Type Definition (PM)
  • Dynamic Form - Caseload Type Definition - Select Existing Caseload Type
  • Notification Type Definition
  • Form Signature Authentication (PM)
  • Report Definition (PM)
  • Report Definition Export
  • Report Definition Import (PM)
  • Dictionary Update (PM)
  • Dictionary Export (PM)
  • Dictionary Import (PM)
  • Change Envelope Build Environment (PM)
Scenario 1: Validate (Audit Field) data in the 'SYSTEM.radplus_envelope_info' SQL Table View
Specific Setup:
  • Have the following "modeled" envelopes created:
  • [TestEnvelopeA] contains a modeled table [TestTable] and modeled form [TestForm] that includes a "Scrolling Free Test" field, a "Draft/Final" field, a "Dictionary" field and any other desired field types
  • [TestEnvelopeB] contains a modeled table [TestTableB] and modeled form [TestFormB] that includes any desired field types and no data has been filed in the form yet
  • [TestEnvelopeC] contains a modeled table and modeled form that includes any desired field types
  • In form "Envelope Export", export [TestEnvelopeB] and store the export file in a folder
  • The user [TestUser] has permissions assigned to query table view 'SYSTEM.radplus_envelope_info' in their user definition
  • Have a report [TestReport] created to display field data in the 'SYSTEM.radplus_envelope_info': table
  • In form "Import Reports", have a report [ImportReport] imported as import type "Import Report for command button launch
  • Log in as [TestUser]
Steps
  1. Open form "Envelope Definition"
  2. Select [TestEnvelopeA]
  3. Make any change and submit the form or just submit the form without any changes
  4. Validate submission is successful. (Note the current date and time)
  5. Run [TestReport]
  6. Validate the following audit fields are populated as expected for the form just submitted, based on the submission date/time noted and the user submitting the form:
  7. "data_entry_by", "data_entry_by_option", "data_entry_user_id", "data_entry_user_name", "data_entry_option", "data_entry_source", "data_entry_date", "data_entry_time"
  8. In addition, if "UTC" time is enabled on the system, validate the following fields are populated as expected:
  9. "data_entry_utc", "data_entry_timezone_info_all", "data_entry_time_j", "data_entry_offset", "data_entry_timezone_short"
  10. Open form "Form Definition"
  11. Select the modeled form [TestEnvelopeA]
  12. Make any change to the form or just submit the form without any changes
  13. Validate submission is successful. (Note the current date and time)
  14. Repeat step 2
  15. Validate results are as expected
  16. Open form "Table Definition"
  17. Select the modeled table [TestTableA]
  18. Make a change and submit the form or just submit the form without any changes
  19. Validate submission is successful. (Note the current date and time)
  20. Repeat step 2
  21. Validate results are as expected
  22. Open form "Document Routing Setup"
  23. Select [TestFormA]
  24. If the form is already enabled for document routing, just submit the form, if not, then enable the form for document routing and submit the form
  25. Validate the form submits successfully (Note the current date and time)
  26. Repeat step 2
  27. Validate results are as expected
  28. Open form "Data Element Help Message Definition"
  29. In the "File" field, select the "File" used in envelope [TestEnvelopeA]. For example, the "User Defined Client" file
  30. In the "Data Element" field, select one of fields used on form [TestFormA]. For example, the dictionary field
  31. Enter any text in the "Data Element Help Message'
  32. Submit the form
  33. Validate the form submits successfully (Note the current date and time)
  34. Repeat step 2
  35. Validate results are as expected
  36. Open form "Scrolling Free Text Templates"
  37. Select the modeled table [TestTableA]
  38. In the "Template Definition" section add a row and select the "Scrolling Text Field"
  39. Populate the required fields and submit the form
  40. Validate the form submits successfully (Note the current date and time)
  41. Repeat step 2
  42. Validate results are as expected
  43. Open form "Envelope Merge"
  44. Select [TestEnvelopeA]
  45. In field "Envelope to Merge into Current Envelope", select [TestEnvelopeC]
  46. Submit the form
  47. Validate the form submits successfully (Note the current date and time)
  48. Repeat step 2
  49. Validate results are as expected
  50. Open form "Form Designer"
  51. Select the modeled form [TestFormA]
  52. Select a section of the form in the "Sections" field and click [Show Section]
  53. Either make a change in the section and submit the form or just submit the form without any changes
  54. Validate the form submits successfully (Note the current date and time)
  55. Repeat step 2
  56. Validate results are as expected
  57. Open form "Form Deletion"
  58. Select modeled form [TestFormB]
  59. Populate the required fields and submit the form
  60. Validate submission is successful. (Note the current date and time)
  61. Repeat step 2
  62. Validate results are as expected
  63. Open form "Table Deletion"
  64. Select modeled table [TestTableB]
  65. Populate the required fields and submit the form
  66. Validate submission is successful. (Note the current date and time)
  67. Repeat step 2
  68. Validate results are as expected
  69. Open form "Envelope Import"
  70. Click "Select Envelope"
  71. Navigate to location of the export file saved for [TestEnvelopeB]
  72. Select to import the envelope as an "Overwrite"
  73. Submit the form
  74. Validate submission is successful. (Note the current date and time)
  75. Repeat step 2
  76. Validate results are as expected
  77. Open form "Form Definition" again
  78. Select the form [TestForm]
  79. Go to the "Object Def" section and add a "Report" object
  80. In the "Report" field select report [ImportReport] imported in the set up
  81. Submit the form
  82. Open form 'Import Reports
  83. Click "Update Existing Report"
  84. Select the report [ImportReport] imported in the setup
  85. Click [Select Report for Import] and select a new report
  86. Submit the form (Note the current date and time)
  87. Repeat step 2
  88. Validate results are as expected
  89. Open form 'Caseload Type Definition' to define a new modeled caseload type
  90. Submit the form
  91. Open form 'Table Definition'
  92. Select [TestTable]
  93. Add a column to the table using the caseload type just created in the previous step
  94. Submit the form
  95. Return to 'Caseload Type Definition'
  96. Select the caseload type just added in step 15 any change any field on the form.
  97. Submit the form (Note the current date and time)
  98. Repeat step 2
  99. Validate results are as expected
  100. Open form 'Notification Type Definition' to define a notification type.
  101. Submit the form
  102. Open form 'Table Definition'
  103. Select [TestTable]
  104. Add a column to the table using the "Notification" type just created in the previous step
  105. Submit the form
  106. Return to 'Notification Type Definition'
  107. Select the notification type just added in step 28 any change any field on the form.
  108. Submit the form (Note the current date and time)
  109. Repeat step 2
  110. Validate results are as expected
  111. Open form 'Form Signature Authentication'
  112. Select [TestFormA]
  113. Set "Require Signature at Form Filing" to "Yes" and populated any require fields
  114. Submit the form
  115. Validate submission is successful. (Note the current date and time)
  116. Repeat step 2
  117. Validate results are as expected
  118. Open form 'Report Definition' to create a new report
  119. Select any report in the "Select Report" field
  120. Set 'Associate Report with Modeling Envelopes' to 'Yes' and select [TestEnvelopeA] in the "Envelopes" field
  121. Populate any other required fields
  122. Submit the form (Note the current date and time).
  123. Repeat step 2
  124. Validate results are as expected
  125. Open form "Report Definition Export"
  126. Export the report definition created in previous step
  127. Open form "Report Definition Import"
  128. Import the report definition exported in the previous step as an "Overwrite"
  129. Submit the form (Note the current date and time)
  130. Repeat step 2
  131. Validate results are as expected
  132. Open form 'Dictionary Update'
  133. Select the dictionary field used in form [TestFormA]
  134. Make a change to field, for example the dictionary description
  135. Submit the form (Note the current date and time)
  136. Repeat step 2
  137. Validate results are as expected.
  138. Open form "Dictionary Export"
  139. Select the dictionary field modified in the previous step and export the file
  140. Open form "Dictionary Import"
  141. In the "Select file" field, select the file just exported in the previous step
  142. Submit the form (Note the current date and time)
  143. Repeat step 2
  144. Validate results are as expected. It will record that the envelopes were modified by 'Dictionary Import'
Topics
• Modeling • SQL Data Access • NX
Update 84 Summary | Details
Cache - prepared for future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • cache - System Management Portal [ServerA]
  • cache - System Management Portal [ServerA] - Globals
  • Processes
  • View Global Data
  • cache - System Management Portal [ServerB]
  • cache - System Management Portal [ServerB] - Globals
  • Cache Terminal Session (ServerA)
  • Cache Terminal Session (ServerB)
Scenario 1: Validate "Results Queue" and "Garbage Collector" (Internal) processes - (Standard System Environment)
Steps
  • Internal Testing Only
Topics
• Cache
 

RADplus_2023_Monthly_Release_2023.02.02_Details.csv