Skip to main content

RADplus 2024 Update 18

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2022 Update 33
RADplus 2023 Update 62
RADplus 2024 Monthly Release 2024.01.00

Product Update Description

The following issues are resolved: 1) Form designer changes for myAvatar NX may not be applied to multiple-iteration sections during envelope import. 2) The error '[SUBSCRIPT]zBuildServiceDocEvents+37^User.RadPlusCSMOption.1', which may occur when submitting 'Form Definition' for forms containing service documentation.

Required Updates

None

Included Updates

None

Details
NEW0 CHANGED0 FIXED2
Fixed (2)
Form Definition - Service Documentation forms
Ensure the ability to submit 'Form Definition' for modeled forms containing service documentation. KB0076477 v0.01
Topics
• Document Routing • Service Documentation
 
Envelope Import with Form Designer changes
Ensure form designer changes for multiple-iteration sections of forms are imported properly in Avatar NX during 'Envelope Import'.
Topics
• Envelope Export • Envelope Import • Form Designer
 
Acceptance Tests
AV-94305 Summary | Details
Form Definition - Service Documentation forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Copy Form to Different System Code (CWS)
  • Form Definition (CWS)
  • Table Definition (CWS)
Scenario 1: Service Documentation Notes form creation
Specific Setup:
  • Multiple root system codes are defined (System Code A & System Code B).
  • Must be logged in with "System Code A".
  • An envelope must be defined in the 'Envelope Definition' CWS form (Envelope A).
  • A CWS table must be defined (Table A) associated to "Envelope A" with the following table columns:
  • 'Progress Note For' - Single Select Dictionary
  • 'Note Addresses Which Existing Service/Appointment' - Single Select Dictionary
  • 'Service Program' - Single Select Dictionary
  • 'Service Practitioner' - Staff Lookup
  • 'Service Date' - Date
  • This table must have "Yes" selected in the 'Service Documentation Table' field.
  • The above table columns must be mapped to the respective Progress Note prompts in the 'Service Documentation' section of the 'Table Definition' form.
  • A CWS form must be defined (Form A) associated to "Envelope A" and "Table A" that does not yet have the 'Service Documentation' table columns added to the form.
  • The logged in user must have access to "Form A".
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Copy Form to Different System Code' CWS form.
  2. Select "Form A" in the 'Select Form' dialog and click [OK].
  3. Enter "System Code B" in the 'Target System Code' field.
  4. Enter the desired user in the 'Target System Username' field.
  5. Enter the password for the user in the 'Target System Password' field.
  6. Select the desired value in the 'Target System Menu to Place Form Under' field.
  7. Select the desired value in the 'Copy unlocked dictionary values' field.
  8. Populate any other desired fields.
  9. Submit the form.
  10. Access the 'Form Definition' CWS form for "Form A".
  11. Navigate to the "Object Def." section.
  12. Click [Add New Item].
  13. Add the 'Progress Notes For' and 'Note Addresses Which Existing Service/Appointment' table columns.
  14. Populate any required and desired fields.
  15. Submit the form.
  16. Access the 'Form Definition' CWS form for "Form A".
  17. Navigate to the "Object Def." section.
  18. Validate the 'Progress Notes For' and 'Note Addresses Which Existing Service/Appointment' table columns added in the previous steps are displayed.
  19. Click [Add New Item].
  20. Add the 'Service Program', 'Service Date', and 'Service Practitioner' table columns.
  21. Populate any other required and desired fields.
  22. Submit the form.
  23. Select "Client A" and access "Form A".
  24. Validate the form displays as expected with the following fields:
  25. 'Progress Notes For'
  26. 'Note Addresses Which Existing Service/Appointment'
  27. 'Service Program'
  28. 'Service Date'
  29. 'Service Practitioner'
  30. File a new service for the client.
  31. Verify successful submission.
  32. Access Crystal Reports or other SQL Reporting Tool.
  33. Create a report using the 'SYSTEM.billing_tx_history' SQL table.
  34. Validate a row is displayed for "Client A" for the service created via "Form A".
  35. Close the report.
Topics
• Service Documentation
AV-94727 Summary | Details
Envelope Import with Form Designer changes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (PM)
  • Form Designer (PM)
Scenario 1: Envelope Export/Import - 'Include Form Design Changes' in the file set to "Y"
Specific Setup:
  • Have a modeled form (Form A), contained in (Envelope A), that will be used to make form designer changes.
  • "Form A" must have a primary/secondary table and a multi-iteration table associated.
Steps
  1. Access the 'Form Designer' form.
  2. Select "Form A" from the 'Forms' field.
  3. Make any type of form designer change in the section [FDchange1]. For example, a field is moved to different location.
  4. Save the changes and exit the form.
  5. Access the 'Envelope Export' form.
  6. Select "Envelope A".
  7. In the "Include Form Design Changes? field, select "Yes".
  8. Click [Begin Export].
  9. Validate export is completed successfully (Export A).
  10. Access the 'Form Designer' form.
  11. Select "Form A" from the 'Forms' field.
  12. Make another form designer change in the section [FDchange2].
  13. Save the changes and exit the form.
  14. Access "Form A".
  15. Validate [FDchange1] and [FDchange2] are both present in the form.
  16. Access the 'Envelope Import' form.
  17. Click [Select Envelope For Import].
  18. Navigate the location "Export A".
  19. Select the file and select "Overwrite Existing".
  20. In the "Include Form Design Changes? field, select "Yes". [Note: "Yes" implies that any form designer changes contained in the import file, 'will' be imported and/or overwrite any existing changes already made on the form].
  21. Click [Begin Import Scan].
  22. Validate there are no errors/warnings found within the import file scan results.
  23. Click [Begin Import].
  24. Validate import is completed successfully.
  25. Access "Form A".
  26. Validate [FDchange1] is present on the form.
  27. Validate [FDchange2] is not present on the form.
  28. Close the form.
Topics
• Envelope Export • Envelope Import • Form Designer