Skip to main content

RADplus 2023 Update 88

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2022 Update 101
RADplus 2023 Monthly Release 2023.03.01

Product Update Description

The following issues are resolved: 1) The error '[SUBSCRIPT]File1+37^GUIObjectT1', which can occur in 'Table Definition'. 2) Setting the value of a search field with ScriptLink may not trigger the field's event logic. 3) No final approval todo is generated when the final approver of a document cosigns the document for another user.

Required Updates

None

Included Updates

2, 4, 6, 7, 12, 13, 14, 22, 25, 26, 29, 33, 35, 39, 49, 55, 56, 58, 59, 64, 69, 71, 75, 80, 85, 86

Details
NEW0 CHANGED0 FIXED3
Fixed (3)
Table Definition
An issue is resolved to ensure that tables configured with "Table Alias" column mappings defined, can be submitted successfully in form "Table Definition".
Topics
• Modeling • Table
 
ScriptLink and event logic
An issue is resolved to ensure that event logic set on a search type field can be triggered successfully, when the value needed to trigger the event, is set by a "ScriptLink" script set to trigger via another field on the form.
Topics
• Modeling
 
To Do's - Cosigner final approver
An issue is resolved to ensure that the final approval todo is generated, when the final approver of a document cosigns the document for another user.
Topics
• Document Routing
 
Acceptance Tests
AV-89814 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,
Topics
• Modeling • Table
AV-90732 Summary | Details
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.
Topics
• Modeling
AV-91124 Summary | Details
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
• Document Routing