Skip to main content

RADplus 2022 Update 110

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Recommended Update Level

RADplus 2018 Update 80
RADplus 2022 Update 12

Product Update Form Description

The following issues are addressed: Upon editing an event in Form Definition, the 'Left Operand' prompt does not repopulate when a Dictionary type prompt was selected. MAXSTRING escapeHTML+11^UICHARTHTML3 occurs in Client Chart on forms using a Selection Leaf type prompt. The prohibition on including the Program dictionary introduced by RADplus2021 Update 15 is extended to cover mapping to other user modeled prompts which are mapped to Program. Fetching User List Management workflow lists is revised for better processing on the 'Display User' report.

Included Updates

12, 37

Required Updates

None

Details
NEW0 CHANGED0 FIXED5
Fixed (5)
Form Definition - Event Logic
An issue is resolved setting up event logic on field in "Form Definition" to ensure the "Left Operand" field remains populated after the form was submitted.
Topics
• Modeling • NX
 
Chart View - Data display
An issue is resolved in "Chart View" to ensure text data filed in a "Selection Leaf" type field in a "Modeled" form is displayed.
Topics
• Chart Review • Forms
 
Envelope Import - Mapped Dictionaries

To address an issue that could occur during "Envelope Import", the current functionality that excludes importing values contained in a "Dictionary" field mapped to the "(10011) Program" dictionary, is extended to include a "Dictionary" fields that is mapped to another dictionary field that's mapped to the "(10011) Program" dictionary
Topics
• Envelope Import • NX
 
Form "Display User"
An issue is resolved to ensure the "User Display" report is generated if the user was assigned to a role and that role was assigned in form "User List Management" as a workflow user role
Topics
• NX • User Definition • User Role Definition
 
Importing Images in Forms
An issue is resolved to ensure images are imported successfully in forms containing a "Multiple Iteration" grid, when two or more rows that contain an image have been added
Topics
• Auto Save • NX
 
Acceptance Tests
AV-78585 Summary | Details
Form Definition - Event Logic
Scenario 1: Form Definition - Event Logic setup and validations
Specific Setup:
  • Have a "Modeled" form [ModeledForm], that contains three fields that will be used to set up a "Calculation Type" event in "Form Definition". For this test, the following fields are set up:
  • [FieldA] - a "Dictionary" field
  • [FieldB] - an "Integer" field
  • [FieldC]- a "Decimal" field
Steps
  1. Open "Form Definition" and select the [ModeledForm]
  2. Click the "Section Def" tab and select the section with fields defined in the setup
  3. Click the "Object Def" tab
  4. Select [FieldB]. This will be the field that will trigger the calculation event
  5. Click to the "Event" section and click the [Add Item] button
  6. Set the "Type of Event" field to "Result of Input with Value Checking"
  7. Set the "Compare with for Event" field, select "Specific Value"
  8. Set the "Specific Value" field to a desired value that will be used to trigger the event. For this test "!0" is used
  9. Set the "Relationship to Comparison Value to Trigger Event" select "Equal To"
  10. Set the "Set Value to Specific Table Value on Event" to "Yes"
  11. Set the "Table Value to Have Value Changed on Event" to [FieldC]. (This will be the field populated with the result of the calculation)
  12. Set the "Table Column Value To" to "Calculation Result"
  13. Set the Calculation Type" to "Addition"
  14. Click the "Left Operand" field
  15. Validate [FieldC] is present and select that value
  16. Click "Submit" to file the form
  17. Validate the form files successfully
  18. Re-open "Form Definition"
  19. Click the "Section Def" tab and select the section with fields defined in the setup
  20. Click the "Object Def" tab
  21. Select [FieldB]
  22. Click to the "Event" section
  23. Validate each field value selected in step 1d is populated as expected
  24. Close the form
  25. Open the [ModeledForm]
  26. Navigate to [FieldA] and enter any value. For this test "4" is used
  27. Navigate to [FieldB] enter a value other than "10", which was the trigger value set up
  28. Validate [FieldC] is not populated
  29. Navigate back to [FieldB] and enter "10"
  30. Validate [FieldC] is populated with addition result of [FieldA] plus [FieldB], as expected. In this test, "14" was validated
  31. Submit the form
  32. Return to the [ModledForm]
  33. Select the row just submitted in step 3
  34. Validate all fields are populated as expected
Topics
• Modeling • NX
AV-81254 Summary | Details
Chart View - Data display
Scenario 1: Chart View - Form data validations
Specific Setup:
  • Have a copy of the "Treatment Plan" form [TPlanCopy] created using form "Create New Treatment Plan"
  • Have a modeled table[MTable] that includes any desired field types and also includes the "Selection Leaf" field that points to [TPlanCopy]. For this example: "Selection Leaf: TPlanCopy" would be listed for selection.
  • Create a "Modeled" form [MForm] that includes all the fields table [MTable]
  • Have a treatment plan filed in treatment plan[TPlanCopy] for a client [TestClient], that includes "Problem", "Goal", "Objective" and an "Intervention" tree view items submitted in the form
  • Have the user with access to the modeled form [MForm]
  • Have the modeled form [MForm] added to the users chart view
Steps
  1. Select client [TestClient]
  2. Open modeled form [MForm]
  3. Click the [Select Treatment Plan Item] button
  4. Validate a "Tab" is opened named with the name of the treatment plan copy created in the set up [TPlanCopy]
  5. Validate the data displayed contains the "Problems", "Goals", "Objective", "Interventions" tree view data submitted in the setup
  6. Validate the data displayed for each tree item is as expected and listed in a readable format
  7. Select the last tree item, "Interventions", this will bring in all connected tree items
  8. Click the [Return] button
  9. In the "Selection Leaf" field text box
  10. Validate the "Problems", "Goals", "Objective", "Interventions" tree view data is displayed as expected, and in a readable format
  11. Submit the form
  12. Validate the form files successfully
  13. Re-open [MForm] for client [TestClient]
  14. Select the row just submitted
  15. Validate all fields are populated, as expected
  16. Close the form
  17. Open "Chart" view for client [TestClient]
  18. Select [MForm] on the left side forms list
  19. Validate the data under the "Select Leaf:" field includes the "Problems", "Goals", "Objective", "Interventions" tree view data as expected
  20. Validate the data is in a readable paragraph format, with each item (Problem, Goal, Objective, etc) starting on a separate line.
  21. Validate data in any other fields are displayed as expected
Topics
• Chart Review • Forms
AV-81893 Summary | Details
Envelope Import - Mapped Dictionaries
Scenario 1: Envelope Export/Import - Validate forms that contain "Mapped" dictionary fields
Specific Setup:
  • Have a server with two Avatar instances setup [SystemA] and [SystemB]
  • [SystemA] has several programs set up in form "Program Maintenance" that include programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)"
  • [SystemB] has several programs set up in form "Program Maintenance" but they do not include programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)"
  • [SystemA] contains two modeled "Envelopes"
  • [EnvelopeA] contains [FormA], it includes a dictionary field [FormA_Dict1] which is mapped to the "(10011) Program" dictionary
  • [EnvelopeB] contains [FormB], it contains a dictionary field [FormB_Dict1] that is mapped to the mapped dictionary "[FormADict1]" set up in [FormA]
  • Both envelopes have been exported from [SystemA] and the export files have saved on the server
  • User has logged in [SystemB]
Steps
  1. Open form "Envelope Import"
  2. Click [Select Envelope Import File]
  3. Navigate to the location of [EnvelopeA] and select the file
  4. Select "Create New"
  5. Click "Begin Import Scan"
  6. Validate there are no errors or warnings in the scan results
  7. Click [Begin Import]
  8. Validate the envelope imports successfully
  9. Repeat steps 1 for [EnvelopeB]
  10. Validate the results are as expected
  11. Open [FormA]
  12. Navigate to field [FormADict1]
  13. Validate programs "ProgramA(800)", "ProgramB(900) and "ProgramC(950) are not displayed in the field, as expected
  14. Select any other program
  15. Submit the form
  16. Return to [FormA]
  17. Select the row just submitted
  18. Validate field [FormADict1] contains the expected value
  19. Close the form
  20. Open [FormB]
  21. Navigate to field [FormBDict1]
  22. Validate programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)" are not displayed in the field, as expected
  23. Select any other program
  24. Submit the form
  25. Return [FormB]
  26. Select the row just submitted
  27. Validate field [FormBDict1] contains the expected value
  28. Close the form
Topics
• Envelope Import • NX
AV-82408 Summary | Details
Form "Display User"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Display User
  • User Display Report
Scenario 1: "Display User" Form - "User Display" report data validations
Specific Setup:
  • Have a user [UserA] who is not assigned to a user role
  • Have another user [UserB] who is assigned to a user role [RoleA]
  • Have another user [UserC] who is assigned to a user role [RoleB]
  • In form "User List Management", have or create a new user list [Userlisttest] with following users submitted in the form
  • In the "Workflow Users" section, add [UserA]
  • In the "Workflow User Roles" section, add [RoleA] but do not add [RoleB]
  • Logged in user has access to form "Display User"
Steps
  1. Open form "Display User"
  2. In field "Individual or All Users", click the "Individual" radio button
  3. In the "Select User" field, select [UserA]
  4. Click the [Display User(s)] button
  5. Validate the "User Display" report generates successfully and in a timely manner
  6. Validate the "User ID" field is populate with [UserA]
  7. Validate the "User Description" field is populated as expected
  8. Validate the "Associate With User Role" field is set to "No", as expected
  9. Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
  10. Close the report
  11. In the "Select User" field, select [UserB]
  12. Click the [Display User(s)] button
  13. Validate the "User Display" report generates successfully and in a timely manner
  14. Validate the "User ID" field is populate with [UserB]
  15. Validate the "User Description" field is populated as expected
  16. Validate the "Associate With User Role" field is set to "Yes"
  17. Validate the "User Role" field is populated with [RoleA], as expected
  18. Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
  19. Close the report
  20. In the "Select User" field, select [UserC]
  21. Click the [Display User(s)] button
  22. Validate the "User Display" report generates successfully and in a timely manner
  23. Validate the "User ID" field is populate with [UserC]
  24. Validate the "User Description" field is populated as expected
  25. Validate the "Associate With User Role" field is set to "Yes"
  26. Validate the "User Role" field is populated with [RoleB], as expected
  27. Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
  28. Close the report
Topics
• NX • User Definition • User Role Definition
AV-84095 Summary | Details
Importing Images in Forms
Scenario 1: Validate Images imported and submitted in a forms
Specific Setup:
  • Have a form that contains a "Primary" and a "Multiple Iteration" section, with each section containing a "Picture" field and any other desired fields.
  • Have "Autosave" is enabled on the form
  • Have three image files(for example ".JPG" images) available for import, [ImageA], [ImageB] and [ImageC]
  • A client [TestClient], is admitted in an active episode
Steps
  1. Open the form
  2. Select [TestClient] and then select the episode
  3. Select the primary section of the form
  4. Navigate to the "Picture" field and import [ImageA]
  5. Populate any other desired fields in the section
  6. Navigate to the multiple-iteration section of the form
  7. Click [Add] to add a row [Row1]
  8. Navigate to the "Picture" field and import [ImageB]
  9. Populate any other desired fields
  10. Click [Add] to add another row [Row2]
  11. Navigate to the "Picture" field and import [ImageC]
  12. Populate any other desired fields
  13. Wait for "Autosave" to automatically trigger or click the [Backup] button
  14. Validate an "Autosave" message is displayed indicating the time of the backup
  15. Close the form
  16. Open the form
  17. Select [TestClient] and then select the episode
  18. Validate a message displays: "You have an unsubmitted backup of this data record. Do you wish to restore from the backup?"
  19. Click [Yes]
  20. Navigate to primary section of the form
  21. Validate the "Picture" field is populated with [ImageA]
  22. Validate all other fields are populates as expected
  23. Navigate to the multiple-iteration section of the form
  24. Select [Row1]
  25. Validate the "Picture" field is populated with [ImageB]
  26. Validate all other fields are populated as expected
  27. Select [Row2]
  28. Validate the "Picture" field is populated with [ImageC]
  29. Validate all other fields are populated as expected
  30. Click [Submit]
  31. Validate the form files successfully
  32. Return to the form
  33. Select [TestClient] and then select the episode
  34. Navigate to primary section of the form
  35. Validate the "Picture" field is populated with [ImageA]
  36. Validate all other fields are populates as expected
  37. Navigate to the multiple-iteration section of the form
  38. Select [Row1]
  39. Validate the "Picture" field is populated with [ImageB]
  40. Validate all other fields are populates as expected
  41. Select [Row2]
  42. Validate the "Picture" field is populated with [ImageC]
  43. Validate all other fields are populates as expected
  44. Close the form
Topics
• Auto Save • NX