Skip to main content

RADplus 2023 Monthly Release 2023.03.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 88 Summary | Details
Table Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
Scenario 1: Table Definition - Validate creating table configured with "Table Alias" column mappings
Specific Setup:
  • Have access to form "Table Definition" in "CWS".
  • Have an existing envelope created in form "Envelope Definition" [TestEnvelope].
Steps
  1. Open form "Table Definition".
  2. In the "Select Table" field, enter a desired new table name [AliasTable].
  3. Click [New Avatar Table].
  4. At the 'Table Definition" prompt, select [TestEnvelope] from the drop down list.
  5. Click [OK].
  6. In the "Table Description" field , enter a desired table description.
  7. In the "Is This Table Date or Order of Entry Sorted".
  8. Populate the "Column Name of Sort Date", Column Description of Sort Date and the Column Label of Sort Date with desired values.
  9. Click to the "Table Alias" section:
  10. Click [Add New Item].
  11. From the 'Alias Table Entity Database' field.
  12. Select "Client".
  13. From the "Alias Table' field.
  14. Select "Diagnosis History (ICD-100).
  15. At the "Table Alias" dialog, click [OK].
  16. Click to the "Column Definition" section:
  17. Click [New Avatar Item].
  18. Add the following columns:
  19. "Type of Diagnosis", using column type "Dictionary - Single Response".
  20. "Diagnosis Time", using column type of "Time".
  21. "Diagnosing Practitioner", using column type "Other entity Lookup", selecting "Staff File" in the "Entity field.
  22. "Status", using with column type "Dictionary - Single Response".
  23. "Diagnosis Search", using column type "Diagnosis - IMO Mapped Search".
  24. "Ranking", using "Dictionary - Single Response".
  25. Click to the "Column Mapping" section:
  26. Click [Add New item].
  27. Select "Type of Diagnosis" from the "Table Column" field.
  28. Select "Type of Diagnosis" in the "Alias Table Column" field.
  29. Click [Add New item].
  30. Select ""Diagnosis Time" from the "Table Column" field.
  31. Select "Time of Diagnosis" in the "Alias Table Column" field.
  32. Click [Add New item].
  33. Select "Diagnosing Practitioner" from the "Table Column" field.
  34. Select "Diagnosing Practitioner" in the "Alias Table Column" field.
  35. Click [Add New item].
  36. Select "Diagnosis Search" from the "Table Column" field.
  37. Select "Diagnosis Search" in the "Alias Table Column" field.
  38. Click [Add New item].
  39. Select "Status" from the "Table Column" field.
  40. Select "Type of Diagnosis" in the "Alias Table Column" field.
  41. Click [Add New item].
  42. Select "Ranking" from the "Table Column" field.
  43. Select "Type of Diagnosis" in the "Ranking" field.
  44. Click [Submit].
  45. Validate submission is successful.
  46. Return to 'Table Definition:
  47. In the "Select Table" field, enter [AliasTable] to edit the table just created.
  48. Click the "Table Definition" section.
  49. Validate all fields populated in step 3, are populated as expected.
  50. Click to the "Table Alias" section:
  51. Validate all fields populated in step 4, are populated as expected,
  52. Click to the ""Column Definition"" section:
  53. Validate all fields populated in step 5, are populated as expected,
  54. Click to the "Column Mapping" section:
  55. Validate all fields populated in step 6, are populated as expected,
  56. Close the form,
ScriptLink and event logic
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form with ScriptLink and Event Logic
Scenario 1: Validate functionality of forms with "Scriptlink" and field "Event Logic" defined on a form
Specific Setup:
  • Have form [TestForm] for testing. For this test, a modeled form is used that contains three fields of any type: [FieldA], [FieldB] and [FieldC] and any other desired fields.
  • [FieldA] is a search type field, "SQL Query Search".
  • [FieldB] is an "Integer" field and [FieldC] is a "Date" type field.
  • Using form "Form Definition", have event logic set on [FieldA], so that when a specific value [TestValue] is selected in the field, it will make a change to [FieldB]. For this test, [TestValue] is set to disable [FieldB].
  • Have a "ScriptLink" script [TestScript] created, that will pass a value to a field based on two parameters, the field number, and the value.
  • Using form "Form Designer", edit [TestForm] and import the script [TestScript].
  • Navigate to and click field [FieldC] on the form:
  • On the left side panel, click to edit the "ScriptLink" properties for the field.
  • From the "Available Scripts" field, select [TestScript].
  • In the "Script Parameter" field, enter the two parameters, "Field Number" for the [FieldC], followed by a comma and then the trigger value for the event logic [TestValue], For example: "123.46,99". [Note: field numbers for fields on forms, can be found by using "Form and Table Documentation"].
  • Save the changes and submit the form.
Steps
  1. Launch [TestForm]:
  2. Do not populate [FieldC].
  3. Populate [FieldB].
  4. Populate [FieldA] with a value other than [TestValue] stated in the setup.
  5. Validate the value is accepted.
  6. Validate [FieldB] is still enabled.
  7. Now populate [FieldA] with value [TestValue].
  8. Validate the value is accepted.
  9. Validate [FieldB] is now disabled, as expected based on the event logic set in the setup.
  10. Populate any other desired fields on the form.
  11. Submit the form.
  12. Validate the form files successfully.
  13. Return to [TestForm]:
  14. Edit the row just submitted in step 1.
  15. Validate [FieldB] is now enabled and populated as expected.
  16. Validate all other fields are populated, as expected.
  17. Close the form.
  18. Return to [TestForm]:
  19. Click to add a new row.
  20. Populate [FieldB].
  21. Navigate to [FieldC] and populate the field with any value.
  22. Validate [FieldA] is automatically populated with [TestValue].
  23. Validate [FieldB] is now disabled, as expected based on the event logic set in the setup.
  24. Populate any other desired fields on the form.
  25. Submit the form.
  26. Validate the form files successfully.
  27. Return to [TestForm]:
  28. Click to edit the row submitted in step 3.
  29. Validate [FieldB] is now enabled and populated as expected.
  30. Validate all other fields are populated, as expected.
  31. Close the form.
To Do's - Cosigner final approver
Scenario 1: My To Do's Widget - Validate a user approving documents as a Co-Signer and a Final Approver
Specific Setup:
  • Have two users [UserA and [UserB] who are staff members and have the "My To Do's" widget on their home view.
  • Enable document routing for any form [TestForm].
  • In form 'User Definition' , [UserA] is set to be a "Final Approver" for form [TestForm] and is set with prompt "Co-signer for other Practitioners" set to "Yes".
  • Have a report or query to display field values in the "DocR.Document" table.
  • Log in as [UserA].
Steps
  1. Open [TestForm]:
  2. Select any client.
  3. Populate the form and submit as "Final".
  4. At the routing screen, add just [UserA] as the approver.
  5. Submit the form.
  6. Navigate to the "My To Do's" widget.
  7. Validate the to do sent in step 1 is present.
  8. Click to approve the document [DocA].
  9. Validate submission is successful.
  10. Validate to do is removed from the to dos list.
  11. Return to [TestForm]:
  12. Select any client.
  13. Populate the form and submit as "Final".
  14. At the routing screen, add [UserA] and [UserB] as the approver's.
  15. Submit the form.
  16. Navigate to the "Sign" tab of the "My To Do's" widget:
  17. Validate there is no to do sent yet for [DocB], as the document needs to signed by [UserB] first,
  18. In the "Staff" search field, search and select [UserB],
  19. Validate the To Do sent in step 3 is now present,
  20. Select and approve the To Do document [DocB],
  21. Validate the to do is removed,
  22. In the "Staff" search field, search for [StaffA],
  23. Validate there is a to do now for final approval, as [UserB] has approved the To Do,
  24. Select and final approve the To Do document [DocB],
  25. Validate the to do is removed from the to do list,
  26. Run the the report or query for "DocR.Document" table:
  27. Locate the row for [DocA]:
  28. Validate the document "Status" field is populated with "Final", as expected.
  29. Locate the row for [DocB]:
  30. Validate the document "Status" field is populated with "Final", as expected.
Topics
• Modeling • Table • Document Routing
Update 100 Summary | Details
Avatar RADplus 'Event Log Definition' Data Archive/Purge
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Event Log Definition
  • System Task Scheduler
Scenario 1: 'Event Log Definition' - Verification of Event Log SQL Table information Archive/Purge
Specific Setup:
  • RADplus Event Auto Archiving must be enabled, with values selected/defined for 'Purge data from SYSTEM.radplus_event_log_audit after selected duration', 'Create file of archived/purged data', 'Minimum Number of Days to Keep' and 'Directory to Place Archive Files In' fields (via 'Event Log Definition' form)
  • 'Event Log Archiving' task must be enabled/scheduled in system (via 'System Task Scheduler' form)
  • Crystal Reports or other SQL reporting tool
Steps
  1. Where RADplus Event Log 'Enable Auto Archiving' is enabled (and archive/purged file settings defined via 'Event Log Definition' form), verify the following items after occurrence and completion of 'Event Log Archiving' scheduled system task:
  2. Open Crystal Reports or other SQL reporting tool.
  3. In SQL table 'SYSTEM.radplus_event_log', ensure that records/rows where difference of system task date and 'event_date' exceeds value defined for 'Minimum Number of Days to Keep' Event Log Definition setting are removed from table (to be added to 'SYSTEM.radplus_event_log_audit').
  4. In SQL table 'SYSTEM.radplus_event_log_audit', ensure that records/rows moved from 'SYSTEM.radplus_event_log' are present.
  5. Where 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' Event Log Definition setting is 'Yes', ensure that existing 'SYSTEM.radplus_event_log_audit' records/rows where difference of system task date and 'audit_date' exceeds value defined for 'Minimum Number of Days to Keep' setting are removed from table.
  6. Where 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' Event Log Definition setting is 'No', ensure that existing 'SYSTEM.radplus_event_log_audit' records/rows are not removed from/remain in SQL table.
  7. Navigate to server output directory defined for 'Directory to Place Archive Files In'.
  8. If SQL table 'SYSTEM.radplus_event_log' is selected in the 'Create file of archived/purged data' Event Log Definition setting, ensure that output file is created on server containing information for archived rows/records.
  9. File Name Example: 'EventLogArchive_SBOXSBOX_98_10312023'
  10. If SQL table 'SYSTEM.radplus_event_log' is not selected/deselected in the 'Create file of archived/purged data' Event Log Definition setting, ensure that no output file is created.
  11. If SQL table 'SYSTEM.radplus_event_log_audit' is selected in the 'Create file of archived/purged data' Event Log Definition setting, ensure that output file is created on server containing information for audit rows/records which were purged/deleted.
  12. File Name Example: 'EventLogAuditArchive_SBOXSBOX_98_10312023'
  13. If SQL table 'SYSTEM.radplus_event_log_audit' is selected in the 'Create file of archived/purged data' Event Log Definition setting, ensure that no output file is created.
Scenario 2: 'Event Log Definition' - Form Verification
Steps
  1. Open RADplus 'Event Log Definition' form.
  2. Ensure that on opening form, existing/currently filed location for 'Directory to Place Archive Files In' field is present in form, and is not overwritten/re-defaulted where value defined.
  3. Note - 'Directory to Place Archive Files In' field may be read-only dependent on user login account/system configuration
  4. Ensure 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' field is present in form, set to 'Yes' by default.
  5. This field controls whether Event Log Audit SQL table 'SYSTEM.radplus_event_log_audit' information/records are removed from database upon exceeding the 'Minimum Number of Days to Keep' setting (default) or will remain in/are not removed from 'SYSTEM.radplus_event_log_audit' (if field set to 'No')
  6. Ensure 'Create file of archived/purged data' field is present in form, with selections for 'SYSTEM.RADplus_event_log' and 'SYSTEM.RADplus_event_log_audit' tables available
  7. This field controls whether/which Event Log SQL tables create information output files for 'SYSTEM.radplus_event_log'/'SYSTEM.radplus_event_log_audit' archived/deleted records in location specified for 'Directory to Place Archive Files In' (files for both tables created by default) or to not create these output files for either/both tables (if tables deselected)
  8. Update selected values in 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' and/or 'Create file of archived/purged data' fields if desired.
  9. Select/enter values for any other fields as required/desired.
  10. Click 'Submit' button to file 'Event Log Definition' form.
  11. Re-open 'Event Log Definition' form.
  12. Ensure that previously selected/filed values are present for all fields in 'Event Log Definition' form (including 'Directory to Place Archive Files In', 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' and 'Create file of archived/purged data' fields).
Avatar RADplus 'Event Log Definition' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Event Log Definition
Scenario 1: 'Event Log Definition' - Form Verification
Steps
  1. Open RADplus 'Event Log Definition' form.
  2. Ensure that on opening form, existing/currently filed location for 'Directory to Place Archive Files In' field is present in form, and is not overwritten/re-defaulted where value defined.
  3. Note - 'Directory to Place Archive Files In' field may be read-only dependent on user login account/system configuration
  4. Ensure 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' field is present in form, set to 'Yes' by default.
  5. This field controls whether Event Log Audit SQL table 'SYSTEM.radplus_event_log_audit' information/records are removed from database upon exceeding the 'Minimum Number of Days to Keep' setting (default) or will remain in/are not removed from 'SYSTEM.radplus_event_log_audit' (if field set to 'No')
  6. Ensure 'Create file of archived/purged data' field is present in form, with selections for 'SYSTEM.RADplus_event_log' and 'SYSTEM.RADplus_event_log_audit' tables available
  7. This field controls whether/which Event Log SQL tables create information output files for 'SYSTEM.radplus_event_log'/'SYSTEM.radplus_event_log_audit' archived/deleted records in location specified for 'Directory to Place Archive Files In' (files for both tables created by default) or to not create these output files for either/both tables (if tables deselected)
  8. Update selected values in 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' and/or 'Create file of archived/purged data' fields if desired.
  9. Select/enter values for any other fields as required/desired.
  10. Click 'Submit' button to file 'Event Log Definition' form.
  11. Re-open 'Event Log Definition' form.
  12. Ensure that previously selected/filed values are present for all fields in 'Event Log Definition' form (including 'Directory to Place Archive Files In', 'Purge data from SYSTEM.radplus_event_log_audit after selected duration' and 'Create file of archived/purged data' fields).
Topics
• RADplus Utilities
Update 101 Summary | Details
User Caseload - Add/Remove
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
Scenario 1: Enhanced Caseload Menu Functionality - Validate adding and removing clients from a user's caseload
Specific Setup:
  • Registry setting "Enable enhanced caseload management from the 'Clients and Data' widget" is enabled:
  • In the registry setting, have a user role [TestRoleA] submitted with access to this functionality.
  • [TestUserA] is assigned to [TestRoleA] in form "User Definition".
  • [TestUserB] is 'not' assigned to [TestRoleA] in form "User Definition".
  • Both users have the "My Clients" widget on their home view and have other clients already on their caseload present in the widget.
  • [TestUserA] has access to forms "Registry Settings" and "Discharge".
  • Log in as [TestUserB].
Steps
  1. At the home view:
  2. Navigate to the "My Clients" widget:
  3. Search for [ClientA], and select the client.
  4. Right-click on the client in the "Recent Clients" list:
  5. Validate there is no option to add the client to the caseload as expected, as the user is not assigned to the user role enabled with this functionality, in the setup.
  6. Select any existing client in the user's caseload:
  7. Right-click on the client.
  8. Validate there is no option to remove the client from their caseload as expected, as the user is not assigned to the user role enabled with this functionality, in the setup.
  9. Log out as [TestUserB].
  10. Log in as [TestUserA].
  11. At the home view:
  12. Navigate to the "My Clients" widget:
  13. Search for [ClientA] and select the client:
  14. In the "Recent Clients" list, right-click on the client.
  15. Validate "Add to Caseload" is a selection.
  16. Click 'Add to Caseload'.
  17. Validate the [ClientA] is added to the users "My Clients" list in the widget.
  18. Search for [ClientB]:
  19. Validate the [ClientB] is added to the users "My Clients" list in the widget.
  20. Navigate back to the "My Clients" widget.
  21. In the "My Clients" list:
  22. Right-click on [ClientA] a click "Remove form Caseload".
  23. Validate the [ClienA] is removed from to the users "My Clients" list in the widget.
  24. Right-click on the [ClientB] and click "Add to Caseload".
  25. Validate the [ClientB] is removed from the users "My Clients" list in the widget.
  26. Repeat step 4a to add [ClientA] and [ClientB] to client caseload again for [TestUserA].
  27. Open form "Discharge":
  28. Select [ClientB].
  29. Populate the required fields on the form.
  30. Submit the form.
  31. Validate the form files successfully.
  32. Navigate back to the "My Clients" widget:
  33. Right-click on [ClientB] the client discharged and click "Remove form Caseload".
  34. Validate the [ClientB] is removed from to the users "My Clients" list in the widget.
  35. Right-click on the [ClientA] and click "Remove to Caseload".
  36. Validate the [ClientA] is removed from the users "My Clients" list in the widget.
Site Specific Section Modeling - field values
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Authorization
Scenario 1: Validate values in "Site Specific" fields after adding or deleting a row in a form
Specific Setup:
  • Have a form [TestForm] that has a "Site Specific" section enabled in the form, via "Site Specific Section Modeling".
  • For this test, the "Service Authorization" form is used
  • Using the "Site Specific Section Modeling" enable one or more site specific fields on the site specific section.
Steps
  1. Open [TestForm]:
  2. Select any client [TestClient]:
  3. Click to add a new row [Row1]:
  4. Navigate to the site specific section.
  5. Populate the fields on that section with any desired values.
  6. Populate any desired fields on other sections of the form.
  7. Submit the form.
  8. Return to [TestForm]:
  9. Select [TestClient]:
  10. At the "Pre-Display" screen, select [Row1].
  11. Navigate to the site specific section.
  12. Validate the site specific fields are populated as expected.
  13. Validate any fields populated in step 1, are populated as expected.
  14. Close the form.
  15. Repeat step 1, adding a new row [Row2], and submitting the form.
  16. Repeat step 2, editing [Row2].
  17. Validate data results are as expected.
  18. Close the form.
  19. Return to [TestForm].
  20. Select [TestClient]:
  21. At the pre-display, select either [Row1] or [Row2] to be deleted. For this test, [Row1] is selected:
  22. Click [Delete].
  23. Validate [Row1] is removed from the pre-display row selection list.
  24. Click to [Add] a new row, [Row3].
  25. Navigate to the site specific section.
  26. Validate all site specific fields on the section are not populated, as expected.
  27. Populate the desired fields on the section.
  28. Navigate to any other desired section of the form.
  29. Populate the desired fields on that section.
  30. Submit the form.
  31. Return to [TestForm].
  32. Select [TestClient]:
  33. At the pre-display screen:
  34. Validate the [Row1] is not present as expected.
  35. Validate that [Row2] is present.
  36. Validate [Row3] is present:
  37. Click [Edit] to edit the row.
  38. Navigate to the site specific section:
  39. Validate the site specific fields are populated as expected.
  40. Navigate to the other sections of the form.
  41. Validate fields are populated as expected.
My To Do's widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (CWS)
  • Document Routing Setup (PM)
  • Scheduling Calendar
  • Progress Notes (Group and Individual) 4
  • TO DO'S
  • DOCUMENTS TO REVIEW
  • Registry Settings (PM)
  • Document Viewer
  • Clinical Document Viewer
Scenario 1: "My To Do' s" widget - Validate approving "Progress Note" Appointment To Do's
Specific Setup:
  • Have two existing appointments [TestApptA] and [TestApptB] scheduled for staff member [TestStaff] with client [TestClient].
  • Using any progress note form [TestForm] enabled for document routing:
  • Submit a row for any client [DocClient], selecting the existing appointment [TestApptA] and route the document to [TestStaff].
  • Submit a second row for [DocClient], selecting the existing appointment [TestApptB] and also route the document to [TestStaff]
  • In form "Scheduling Calendar", navigate to the appointment [TestApptA] in the grid.
  • Right-click on the appointment and either delete or reschedule the appointment to a new date and time
  • [TestStaff] has the "My To Do's" widget on their home view.
  • Log in as [TestStaff].
Steps
  1. Log in as [TestStaff].
  2. Navigate to the "My To Do's" widget.
  3. Locate the "To Do" sent for [TestApptA].
  4. Click to review the To Do.
  5. Validate the document [DocA] is displayed as expected.
  6. Click to "Accept" and then "Sign" the To Do.
  7. Validate submission is successful.
  8. Validate the To Do is removed from the To Do's list.
  9. Locate the "To Do" sent for [TestApptB].
  10. Click to review the To Do..
  11. Validate the document [DocB] is displayed as expected
  12. Click to "Accept" and then "Sign" the To Do.
  13. Validate submission is successful.
  14. Validate the To Do is removed from the To Do's list.
  15. Open form "Clinical Document Viewer".
  16. Select [TestClient].
  17. Click to display all documents.
  18. Select [DocA].
  19. Click [View].
  20. Validate the document is displayed as expected.
  21. Close the document.
  22. Select [DocA].
  23. Click [View].
  24. Validate the document is displayed as expected.
  25. Close the document.
Guardiant - progress note metrics
Scenario 1: Validate "Guardiant" (Internal) Metric processing time performance
Steps
  1. Internal Testing Only
Topics
• My Clients • Site Specific Section Modeling • Document Routing • My To Do's • Guardiant
Update 107 Summary | Details
Transfer Caseload
Scenario 1: Transfer Caseload - Client transfer validations
Specific Setup:
  • In form "Caseload Type Definition", have or create caseload type [TestCasetype]. [Note: Once created, caseload type created can be added as a field in any modeled table and used to add a client to user's caseload]
  • Have or create a modeled form [TestForm] and add the caseload type field [TestCasetype] to the form
  • Have two existing clients on the system for testing: [ClientA] and [ClientB]
  • Have two users [UserA] and [UserB]
  • Both users do not currently have [ClientA] and [ClientB] in their client caseload
  • Both users have the "My Clients" widget on their home view
  • [UserA] has access to [TestForm] and form "Transfer Caseload"
Steps
  1. Log in as [UserA]
  2. Open [TestForm]
  3. Select [ClientA] for any episode [EpisodeA]
  4. Click to add a row [RowClientA]
  5. In the"Add to Caseload" field, select [UserA]
  6. Submit the form
  7. Re-open [TestForm]
  8. Select [ClientB] for any episode [EpisodeA]
  9. Click to add a row [RowClientB]
  10. In the"Add to Caseload" field, select [UserA]
  11. Submit the form
  12. Navigate to the "My Clients" widget
  13. Validate [ClientA] and [ClientB] are displayed in their "My Clients" list
  14. Open [TestForm]
  15. Select either [ClientA] or [ClientB]. For this test [ClientA] is used
  16. Select [RowClientA] for edit
  17. Validate fields are populated as expected
  18. Leaving the form open, navigate back to the home view
  19. Open form "Transfer Caseload"
  20. In the "Transfer Caseload From" field, select [UserA]
  21. In the "Caseload Assignment Type" field, select the "[TestForm]:Add to Caseload" selection
  22. In the "All or Selected Caseload Entries" field, click the "Selected" radio button
  23. Click [Select Caseload Entries]
  24. Validate the rows, [RowClientA] and [RowClientB] are present, as expected
  25. Click [Cancel]
  26. In the "All or Selected Caseload Entries" field, this time click the "All" radio button
  27. Populate the "Reason For Transfer" text field
  28. Submit the form
  29. Validate a message is displayed indicating:
  30. You are about to transfer a caseload for [ClientA] in [EpisodeA] form [UserA] to [UserB]
  31. Click the [Transfer] button
  32. Validate submission is successful and the following message is displayed:
  33. Some records were locked by another user and have not been updated
  34. [ClientB] in [EpisodeA] from [UserA] to [UserB]
  35. Click [OK]
  36. Close the form
  37. Navigate to the "My Clients" widget
  38. Validate [ClientA] is no longer present in their "My Clients" list
  39. Validate [ClientB] is still present in their "My Clients" list
  40. Log out as [UserA]
  41. Log in as [UserB]
  42. Validate [ClientA] is not present in their "My Clients" list, as expected
  43. Validate [ClientB] is present in their "My Clients" list, as expected
Delete/Re-Assign To Do Items - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Escalate To Do Item
  • Delete/Re-Assign To Do Items
Scenario 1: Delete/Re-Assign To Do's - Validations
Specific Setup:
  • [UserA] has sent a notification To Do [NoteTodoA] to [UserB] via form "Send To Do Notification"
  • [UserA] has also sent a notification to do [NoteTodoB] to [UserC] via form "Send To Do Notification"
  • [UserD] does not have any To Do's in their "My To Do's" list
  • [UserE] has two To Do items [TestToDoA] and [TestToDoB] in their "My To Do's" list, not generated via form "Send To Do Notification"
  • Log in as [UserA]
Steps
  1. Navigate to the "My ToDo's" widget and click to refresh the widget
  2. Click the "Sent & Not Received" column in the widget
  3. Validate [NoteTodoA] generated in setup that was sent to [UserB] is present
  4. Validate [NoteTodoB] generated in setup that was sent to [UserC] is present
  5. Select [NoteTodoA] and click the "Escalate" column in the widget
  6. Click the "Escalate To Do Item" link in the column
  7. In the "Escalate To Do Item" form
  8. Search for [UserD], in the "Select User" search field
  9. Click [Add User]
  10. In the "Sent To" field, click the check box for [UserD]
  11. In the "Note" field, enter a desired message for [UserD]
  12. Click [Submit]
  13. At the "To Do Sent" message dialog, click [OK]
  14. Now select the row for the to do [NoteTodoB] click the "Escalate" column
  15. Click the "Escalate To Do Item" link in the column
  16. In the "Escalate To Do Item" form
  17. Search for [UserE], in the "Select User" search field
  18. Click [Add User]
  19. In the "Sent To" field, click the check box for [UserE]
  20. In the "Note" field, enter a message for [UserE].
  21. Click [Submit]
  22. At the "To Do Sent" message dialog, click [OK]
  23. At the Home View, open form "Delete/Re-Assign To Do Items"
  24. Select "Delete" in the "Delete/Re-assign" field
  25. In the "Select User" field, select [UserD]
  26. Validate a message stating "All To-Do Items for this user have been reviewed or deleted" is displayed
  27. Click [OK]
  28. Validate there are no to do's present in the "To Do's" list box as expected, including the escalated notification [NoteToDoA] sent to [UserD] in step1, [Please Note: Any To Do's generated via "Send Notification To Do" form, are excluded from the "Delete/Re-Assign To Do Items" form]
  29. Click [OK]
  30. Select "Re-Assign" in the "Delete/Re-assign" field
  31. In the "Select User" field, select [UserD] again
  32. Validate a message stating "All To-Do Items for this user have been reviewed or deleted" is displayed again
  33. Click [OK]
  34. Validate there are no To Do's present in the "To Do's" list box as expected, including the escalated notification [NoteToDoA] sent to [UserD] in step 1.
  35. Click [OK]
  36. Select "Delete" again in the "Delete/Re-assign" field
  37. This time in the "Select User" field, select [UserE]
  38. Validate the notification to do [NoteToDoB], escalated to [UserE] in step1 is not present in the "To Do's" list box, as expected
  39. Validate [TestToDoA] and [TestToDoB] that were not generated from the "Send To Do Notification" form are present in the "To Do's" list box
  40. Select [TestToDoA] in the "To Do's" list box
  41. Enter any desired comment in the "Comment" field
  42. Submit the form and return to the form
  43. Select "Re-Assign" in the "Delete/Re-assign" field
  44. In the "Select User" field, select [UserE]
  45. Validate [TestToDoA] just deleted is not present in the "To Do's" list box.
  46. Validate the notification [NoteToDoB], escalated to [UserE] is also not present in the "To Do's" list box
  47. Validate [TestToDoB] is present in the "To Do's" list box
  48. Select [TestToDoB]
  49. In the "Select Target User" field, select any other user [UserF] to re-assign the to do to
  50. Submit the form
  51. Validate the form submits successfully
  52. Closet the form
  53. Log out as [UserA]
  54. Log in as [UserF]
  55. Navigate to the "My To Do's" list
  56. Validate the to do reassigned to [UserF] is present in their to do's list as expected
  57. Click [Review To Do Item]
  58. Validate the to do information for [TestToDoB], is displayed as expected
  59. Select the "Review" check box
  60. Submit the form
  61. Validate the To Do is removed from the "My To Do's" widget
Document Routing - status information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Document Routing - Validate a document's routing "Status" displayed in "Chart" and "Console Widget Viewer"
Specific Setup:
  • [TestFormA] is a modeled form enabled for document routing
  • A console widget [WidgetA] has been created for the form in form "Console Widget Configuration"
  • [TestFormB] is a progress note form enabled for document routing
  • A console widget [WidgetB] has been created for the form in form "Console Widget Configuration"
  • [TestFormC] is a treatment plan form enabled for document routing
  • A console widget [WidgetC] has been created for the form in form "Console Widget Configuration"
  • [TestUser] has access all three widgets on their home view along with the "Console Widget Viewer" widget
  • [TestUser] has all three test forms added to their chart view
  • Have three users who are staff members:
  • [StaffA], [StaffB], and [StaffC]
  • Registry setting "Display Document Routing Status on Chart Items' has been set to "Y"
  • Log in as [TestUser]
Steps
  1. Select a client [TestClient]
  2. Open [TestFormA]
  3. Populate all the required and desired fields on the form
  4. Submit the form as "Final"
  5. Click [Accept and Rout]
  6. At the "Route to Document" screen
  7. In the "Supervisor" search field, select [StaffA]
  8. Click [Add] to add them to the list of approvers
  9. In the "Add Approver" search field, select [StaffB]
  10. Click [Add] to add them to the list of approvers
  11. In the "Add Members to Acknowledge" search field, select [StaffC]
  12. Click [Add] to add them to the list of approvers
  13. Click [Submit]
  14. Validate the form submits successfully
  15. Repeat step 1 for [TestformB] and [TestFormC]
  16. Validate results are as expected
  17. At the home view
  18. Select [TestClient] and right click to open their chart
  19. Select [TestFormA] on the left side panel
  20. Validate the row filed in step 1 is displayed
  21. Validate data is displayed as expected
  22. Scroll to the bottom of the document to the "Document Routing" section
  23. Validate the "Status" field is populated with "Pending"
  24. Validate the "Approvers" field contains
  25. [StaffA] with title "Supervisor (Pending)"
  26. [StaffB] with title "Staff (Pending)"
  27. Validate the "Acknowledgers" section contains
  28. [StaffC] (Pending Acknowledgment)
  29. Repeat step 4a selecting [TestFormB] on the left side panel
  30. Validate results are as expected
  31. Repeat step 4a selecting [TestFormC] on the left side panel
  32. Validate results are as expected
  33. Return to the home view, select [TestClient]
  34. Navigate to [WidgetA] and refresh the widget
  35. Validate the row filed in step 1 is present in the widget
  36. Click the [View] button
  37. Validate data for the row is displayed in the "Console Widget Viewer" as expected
  38. Scroll to the bottom of the document to the "Document Routing" section
  39. Validate the "Status" field is populated with "Pending"
  40. Validate the "Approvers" field contains
  41. [StaffA] with title "Supervisor (Pending)"
  42. [StaffB] with title "Staff (Pending)"
  43. Validate the "Acknowledgers" section contains
  44. [StaffC] (Pending Acknowledgment)
  45. Navigate to [WidgetB], refresh the widget and repeat step 4a for the widget
  46. Validate results are as expected
  47. Navigate to [WidgetC], refresh the widget and repeat step 4a for the widget
  48. Validate results are as expected
  49. Log out as [TestUser]
  50. Log in as [StaffA]
  51. Navigate to their "My To Do's" widget
  52. Click and approve the To Do for [TestFormA]
  53. Click and approve the To Do for [TestFormbB]
  54. Click and approve the To Do for [TestFormC]
  55. Log out as [StaffA]
  56. Log in as [StaffB]
  57. Repeat step 6 approving the To Do's
  58. Log out as [StaffB]
  59. Log in as [StaffC]
  60. Repeat step 6 approving the To Do's
  61. Log out as [StaffC]
  62. Log back in as [TestUser]
  63. At the home view
  64. Select [TestClient] and right click to open their chart
  65. Select [TestFormA] on the left side panel
  66. Validate the row filed in step 1 is displayed
  67. Validate data is displayed as expected
  68. Scroll to the bottom of the document to the "Document Routing" section
  69. Validate the "Status" field is populated with "Pending"
  70. Validate the "Approvers" field contains
  71. [StaffA] with title "Supervisor (Accepted)"
  72. [StaffB] with title "Staff (Accepted)"
  73. Validate the "Acknowledgers" section contains
  74. [StaffC] (Acknowledged)
  75. Return to the home view, select [TestClient]
  76. Navigate to [WidgetA] and refresh the widget
  77. Validate the row filed in step 1 is present in the widget
  78. Click the [View] button
  79. Validate data for the row is displayed in the "Console Widget Viewer" as expected
  80. Scroll to the bottom of the document to the "Document Routing" section
  81. Validate the "Status" field is populated with "Pending"
  82. Validate the "Approvers" field contains
  83. [StaffA] with title "Supervisor (Accepted)"
  84. [StaffB] with title "Staff (Accepted)"
  85. Validate the "Acknowledgers" section contains
  86. [StaffC] (Acknowledged)
  87. Navigate to [WidgetB], refresh the widget and repeat step 14a for the widget
  88. Validate results are as expected
  89. Navigate to [WidgetC], refresh the widget and repeat step 14a for the widget
  90. Validate results are as expected
Topics
• My Clients • Document Management • Document Routing
Update 112 Summary | Details
System Security Defaults form - 'Outlook 365 Integration Configuration'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Display User Role
  • System Security Defaults
  • Registry Settings (PM)
  • Microsoft Outlook Calendar
Scenario 1: System Security Defaults - 'Outlook 365 Integration Configuration' setting validations
Specific Setup:
  • The "Microsoft Azure" cloud computing platform or similar platform has been setup by the client's system administrators to integrate with "Microsoft 365", to provide the "Microsoft Outlook" application to users
  • "Microsoft Outlook 365" integration certificate values : "Client ID", "Client Secret" and "Tenant ID", have been generated by the client's system administration and provided to the logged in user
  • Logged in user has access to form, "Registry Settings" and form "System Security Defaults"
Steps
  1. Open form "Registry Settings"
  2. Search for registry setting "Enable Outlook 365 Integration"
  3. Entering a value of "Y" in the "Registry Settings Value" field will:
  4. Enables support for "Outlook 365 Integration" in the system
  5. Creates a new section in form "System Security Defaults", called "Outlook 365 Integration Configuration", where integration certificate values may be entered and submitted
  6. Entering a value of "N" in the "Registry Settings Value" field will:
  7. Disables support for "Outlook 365 Integration" in the system
  8. Removes section "Outlook 365 Integration Configuration" in form "System Security Defaults"
  9. Set the value in the "Registry Settings Value" field to a value other than "Y" or "N"
  10. Validate the error message "The selected value is not valid in the current system code for the following reason: Valid values are Y or N", is displayed
  11. Set the value in the "Registry Settings Value" field to "Y"
  12. Validate the value is accepted
  13. Submit the form
  14. Validate the form files successfully
  15. Click "Yes" to return to the form
  16. Search for registry setting "Enable Outlook 365 Integration"
  17. Validate the "Registry Setting Value" is set to "Y", as expected
  18. Close the form
  19. Open form "System Security Defaults"
  20. Validate a new section is displayed on the left side, called "Outlook 365 Integration Configuration"
  21. Click section "Outlook 365 Integration Configuration"
  22. Navigate to the "Client ID" field
  23. Attempt to enter a value greater than "50" characters
  24. Validate any characters entered over "50" characters does not display
  25. Enter any value up to "50" characters
  26. Validate all characters are displayed and accepted
  27. Enter the "Client ID" value provided, as noted in the setup
  28. Submit the form
  29. Validate an error is displayed
  30. 'The following fields are missing: "Client Secret" and "Tenant ID"'
  31. Click [OK]
  32. Navigate to the "Client Secret" field
  33. Attempt to enter a value greater than 50 characters
  34. Validate any characters entered over 50 characters do not display
  35. Enter a value up to 50 characters
  36. Validate all characters are displayed and accepted
  37. Enter the "Client Secret" value provided, as noted in the setup
  38. Navigate to the "Tenant ID"
  39. Attempt to enter a value greater than 50 characters
  40. Validate any characters entered over 50 characters do not display
  41. Enter a value up to 50 characters
  42. Validate all charters are displayed and accepted
  43. Enter the "Tenant ID" value provided, as noted in the setup
  44. Submit the form
  45. Validate submission is successful
  46. Return to the form "System Security Defaults"
  47. Select section "Outlook 365 Integration Configuration"
  48. Validate the values entered in the "Client ID", "Client Secret" and "Tenant ID" fields in step 2, are as expected
  49. Open form "Registry Settings"
  50. Search for registry setting "Enable Outlook 365 Integration"
  51. Entering a value of "N" in the "Registry Settings Value" field
  52. Submit the form
  53. Validate the form files successfully
  54. Return to the form "System Security Defaults"
  55. Validate the section "Outlook 365 Integration Configuration", is not longer present on the form as expected
  56. Open form "Registry Settings"
  57. Search for registry setting "Enable Outlook 365 Integration"
  58. Entering a value of "Y" in the "Registry Settings Value" field
  59. Submit the form
  60. Validate the form files successfully
  61. Return to the form "System Security Defaults"
  62. Validate the section "Outlook 365 Integration Configuration", is now present on the form again, as expected
Scenario 2: Avatar NX - 'Outlook 365 Integration" - User set up and "My Calendar" widget validations
Specific Setup:
  • The "Microsoft Azure" cloud computing platform or similar platform, has been setup by the client's system administrators to integrate with "Microsoft 365" to provide the "Microsoft Outlook" application to users
  • Registry setting '"Enable Outlook 365 Integration" has been set to "Y" to enable support for "Outlook 365" integration. [Note: this registry setting is introduced with "RADplus 2023 Update 112"]
  • In form "System Security Defaults", in the "Outlook 365 Integration Configuration" section, the "Client ID", "Client Secret" and "Tenant ID" field values needed for integration provided by the Admin team, have been populated and the form has been submitted successfully
  • [TestUser] has "Microsoft Outlook" installed on their desktop and has a "Microsoft Outlook" email account assigned to them [TestEmail]
  • [TestUser] has an appointment or meeting [TestApptA], scheduled in their "Microsoft Outlook" on [TestDateA]
  • [TestUser] is also a staff member and has a client appointment [TestApptB], already scheduled on [TestDateB], via form "Scheduling Calendar" in myAvatar
  • [TestUser] has the "My Calendar" widget on their home view
  • Log in as [TestUser]
Steps
  1. At the home view, select the "User Menu" icon in the top right corner
  2. Click "Preferences"
  3. Click the "Calendar" tab and then click "Add Source" and
  4. From the "Select Source Type" drop down list, select "Microsoft Outlook"
  5. Click [Add]
  6. At the "Microsoft Sign In", dialog enter the email address [TestEmail] for the logged in user
  7. Click [Next]
  8. At the "Enter Password" prompt, enter the email login password
  9. Click [Sign in]
  10. Validate message "Successfully linked Microsoft Outlook account to email [TestUser]"
  11. Click [OK]
  12. Validate "Microsoft Outlook" is added in the source list box
  13. Validate the check box next to the source is checked
  14. Click [Save]
  15. Click 'Preferences' to return to the form
  16. Validate "Microsoft Outlook" is added in the source list box
  17. Validate the check box next to the source is checked
  18. Close the form
  19. At the home view, navigate to the "My Calendar" widget
  20. Click the "Refresh" button on the widget
  21. On the calendar, navigate to [TestDateA]
  22. Validate [TestApptA] scheduled in "Microsoft Outlook" is displayed on the calendar for that day
  23. On the calendar, navigate to [TestDateB]
  24. Validate [TestApptB], the appointment scheduled in form "Scheduling Calendar', is displayed on the calendar for that day
  25. In "Microsoft Outlook"
  26. Open the calendar and delete [TestApptA]
  27. In Avatar
  28. Open form "Scheduling Calendar" and delete [TestAppB]
  29. Refresh the "My Calendar" widget
  30. Validate [TestApptA] and [TestApptB] have been removed from the calendar
  31. In "Microsoft Outlook"
  32. Schedule a new meeting [TestMeeting] on a desired date [TestDateC]
  33. In Avatar
  34. Schedule a new appointment [TestApptD] on a desired date [TestDateD]
  35. At the home view, navigate to the "My Calendar" widget
  36. Click the "Refresh" button on the widget
  37. On the calendar, navigate to [TestDateC]
  38. Validate [TestMeeting] scheduled in "Microsoft Outlook" is displayed on the calendar for that day
  39. On the calendar, navigate to [TestDateD]
  40. Validate [TestApptD], the appointment scheduled in form "Scheduling Calendar', is displayed on the calendar for that day
Topics
• User Role Definition • System Security Defaults • NX • My Calendar
Update 115 Summary | Details
DCI Import process
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Data Import (PM)
Scenario 1: Data Import - validate functionality when errors occur
Specific Setup:
  • A data import file containing a "SQL Query Custom Search" field must exist for import (File A).
Steps
  1. Access the 'Data Import' form.
  2. Click [Select Data Import File].
  3. Validate a dialog stating: "Warning!! The file upload process may take a few minutes to process." and click [OK].
  4. Select "File A" and click [Open].
  5. Validate the 'Select Data Import File' button is disabled.
  6. Click [Validate Data Import File].
  7. Validate a 'Confirm' dialog stating: "There are 1 or more errors within the file import." and click [OK].
  8. Validate the error(s) display in the 'Errors and Warnings' field.
  9. Validate the error states: Option contains a "SQL Query - Custom Search" object which is not eligible for data import.
  10. Note: "SQL Query - Custom Search" fields will only be supported when coming from Avatar CareFabric.
  11. Validate the 'Validate Data Import File' and 'Process Data Import File' buttons are disabled.
  12. Click [Download Data Import Error/Warning File].
  13. Validate the file downloads and the 'Download Data Import Error/Warning File' button is disabled.
  14. Close the form.
Topics
• Data Import • NX
Update 117 Summary | Details
Service Documentation Corrections - Delete Service Documentation Row
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
  • Service Documentation Corrections
Scenario 1: Service Documentation Corrections - Delete Service Documentation Row
Specific Setup:
  • A modeled form configured for 'Service Documentation' is defined (Form A).
  • Document routing is enabled for "Form A".
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access "Form A".
  2. Select "New Service" in the 'Data Row For' field.
  3. Enter the desired date in the 'Date' field.
  4. Enter the desired time in the 'Start Time' and 'End Time' fields.
  5. Populate all other required and desired fields.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password for the logged in user and click [OK].
  11. Access the 'Clinical Document Viewer' form.
  12. Select "Individual" in the 'Select All or Individual Client' field.
  13. Select "Client A" in the 'Select Client' field.
  14. Click [Process].
  15. Validate the 'Document List' displays the document filed via "Form A" with a 'Document Status' of "Final".
  16. View the document and validate the data displays as expected.
  17. Click [Close All Documents].
  18. Validate the document is no longer displayed.
  19. Close the form.
  20. Access the 'Client Ledger' form.
  21. Select "Client A" in the 'Client ID' field.
  22. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  23. Select "Simple" in the 'Ledger Type' field.
  24. Select "Yes" in the 'Include Zero Charges' field.
  25. Click [Process].
  26. Validate the 'Client Ledger' report is displayed and contains the service filed via "Form A".
  27. Close the form.
  28. Access the 'Service Documentation Corrections' form.
  29. Select "Form A" in the 'Form' field.
  30. Select "Client A" in the 'Client ID' field.
  31. Select the corresponding episode in the 'Episode Number' field.
  32. Click [Select Row to Correct].
  33. Select the service filed in the previous steps in the 'Select Row To Correct' dialog and click [OK].
  34. Select "Delete Service Documentation Row" in the 'Correction Action' field.
  35. Validate a message is displayed stating: PLEASE NOTE: Once the data has been deleted, it cannot be recovered. Are you sure you wish to continue?
  36. Click [OK].
  37. Enter the desired value in the 'Comments' field.
  38. Select "Yes" in the 'Delete Service' field.
  39. Click [Submit] and [No] to close the form.
  40. Access the 'Clinical Document Viewer' form.
  41. Select "Individual" in the 'Select All or Individual Client' field.
  42. Select "Client A" in the 'Select Client' field.
  43. Click [Process].
  44. Validate the 'Document List' displays the document filed via "Form A" with a 'Document Status' of "Void" since the service documentation row has now been deleted.
  45. Close the form.
  46. Access the 'Client Ledger' form.
  47. Select "Client A" in the 'Client ID' field.
  48. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  49. Select "Simple" in the 'Ledger Type' field.
  50. Select "Yes" in the 'Include Zero Charges' field.
  51. Click [Process].
  52. Validate the 'Client Ledger' report is displayed and does not contain the deleted service.
  53. Close the form.
Form Designer - 'Section Name' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
  • Form Designer (CWS)
  • Modeled form with Default Dictionary Values
Scenario 1: Form Designer - Validate changes to the 'Section Name' field
Specific Setup:
  • Please note: this is for Avatar NX systems.
Steps
  1. Access the 'Form Designer' PM form.
  2. Select "Admission" in the 'Forms' field.
  3. Select "(Demographics)" in the 'Sections' field.
  4. Validate the 'Section Name' field contains "Demographics".
  5. Enter "Demographics Test" in the 'Section Name' field.
  6. Click [Submit].
  7. Access the 'Form Designer' PM form.
  8. Select "Admission" in the 'Forms' field.
  9. Select "Demographics Test (Demographics)" in the 'Sections' field.
  10. Validate the 'Section Name' field contains "Demographics Test".
  11. Close the form.
  12. Select any existing client and access the 'Admission' form.
  13. Select any existing episode and click [Edit].
  14. Validate the 'Demographics Test' section displays as expected.
  15. Close the form.
  16. Access the 'Form Designer' PM form.
  17. Select "Admission" in the 'Forms' field.
  18. Select "Demographics Test (Demographics)" in the 'Sections' field.
  19. Validate the 'Section Name' field contains "Demographics Test".
  20. Enter "Demographics" in the 'Section Name' field.
  21. Click [Submit].
  22. Access the 'Form Designer' PM form.
  23. Select "Admission" in the 'Forms' field.
  24. Select "(Demographics)" in the 'Sections' field.
  25. Validate the 'Section Name' field contains "Demographics".
  26. Close the form.
  27. Select any existing client and access the 'Admission' form.
  28. Select any existing episode and click [Edit].
  29. Validate the 'Demographics' section displays as expected.
  30. Close the form.
Form Designer - 'Export Form Designer Copy' button
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
  • Form Designer (PM)
  • Modeled form with Default Dictionary Values
Scenario 1: Form Designer - Validate the 'Export Form Designer Copy' button is disabled when there are no changes to export
Specific Setup:
  • Please note: this is for Avatar NX systems.
  • Must have a form that does not have any 'Form Designer' changes (Form A).
Steps
  1. Access the 'Form Designer' form.
  2. Select "Form A" in the 'Forms' field.
  3. Select the desired section in the 'Sections' field.
  4. Validate the 'Export Form Designer Copy' button is disabled since there are no 'Form Designer' changes to export.
  5. Click [Show Section].
  6. Make any desired changes and click [Save].
  7. Validate a "Save layout?" dialog is displayed stating: Are you sure you wish to save your changes?
  8. Click [Yes].
  9. Validate a message is displayed stating: Form saved.
  10. Click [OK].
  11. Submit the form.
  12. Access the 'Form Designer' form.
  13. Select "Form A" in the 'Forms' field.
  14. Validate the 'Export Form Designer Copy' button is now enabled since 'Form Designer' changes are present.
  15. Click [Export Form Designer Copy].
  16. Validate a message is displayed stating: Export Complete.
  17. Click [OK] and close the form.
Topics
• Service Documentation • Form Designer • NX
 

RADplus_2023_Monthly_Release_2023.03.02_Details.csv