Skip to main content

RADplus 2023 Update 121

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2020 Update 125
RADplus 2020 Update 68
RADplus 2022 Update 70
RADplus 2023 Monthly Release 2023.04.00

Product Update Description

Several issues related to forms attached from other application in the myAvatarNX All Documents Widget are addressed: Incorrect data, or no data, appeared for the form in the widget because the processing occurred in the wrong application; inside the All Documents Widget Definition form, 'Forms Assigned' dialog, multiple forms would appear selected when only one was selected, and forms could not be de-selected. Also, an issue with the 'Time' column on the widget defaulting to 12:00 AM on blank values is resolved. Issues where the widget may not collect all data rows, or may not show all data rows collected are resolved.

Required Updates

None

Included Updates

24, 30, 53, 67

Details
NEW0 CHANGED0 FIXED3
Fixed (3)
All Documents Widget Definition- Select/Deselect forms
The "All Documents Widget Definition" form is updated to ensure that if a form that was attached from another application's menu (via the 'Attach Other Application Form to Menu' form) is selected or deselected for assignment the widget, that the form is still selected/deselected after submission and any other forms that were all already selected or not selected before submission, are still in their original state
Topics
• All Documents Widget • All Documents Widget Definition • Forms
 
All Document Widget - forms
An issue is resolved to ensure that when a form has been attached from another application's menu (via the 'Attach Other Application Form to Menu' form) has been assigned to tab on the "All Document Widget, that the form displays in the tab and the row submitted displays data, as expected i
Topics
• All Documents Widget • All Documents Widget Definition • Forms
 
All document Widget - form data rows
An issue is resolved where the "All Document Widget" may not display all the data rows submitted in a form, when many rows were submitted. In addition, an issue where a data row "Time" column value would default to a value of "12:00 AM when the value should have been blank, is resolved
Topics
• All Documents Widget
 
Acceptance Tests
AV-89767 Summary | Details
All Documents Widget Definition- Select/Deselect forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
Scenario 1: 'All Documents Widget Definition' Form- (Forms attached to a menu from another application) - 'Forms Assigned' Validations
Specific Setup:
  • Have two forms in an application that can be used for testing. For this test, "Avatar PM" is used. [PMForm1] and [PMForm2]
  • In another application, (e.g. Avatar CWS), open form "Attach Other Application Form to Menu"
  • In the "Application" field select the 'Avatar PM' application and in the "Form To Attach" choose the form [PMForm1]
  • In the" Menu to Place Form Under" field choose a desired " CWS" menu for the "PM" form
  • Update "Form Description' field with a new desired name, that will appear on the "CWS" menu [PMForm1CWS]
  • Submit the form
  • Repeat the previous step for [PMForm2], assigning the form a different name [PMForm2CWS], in the 'Form Description' field
  • The logged in user has the [AllDocWidget] is their home view
  • The logged in user has access to form "All Document Widget Definition"
Steps
  1. Open the "All Documents Widget Definition" form.
  2. Select the "Multi-Form Tab" section and select "Add" to create a new tab
  3. Populate the "Tab ID" with a desired value and enter a desired name for the tab [CrossNamespaceTab], in the "Tab Name" field
  4. Click the 'Forms Assigned" button.
  5. Validate both forms PM forms that were attached to a CWS menu in the set up, [PMForm1CWS] and [PMForm2CWS], are available for selection
  6. Validate neither of the forms are currently selected
  7. Select [PMForm1CWS] and leave [PMForm2CWS] unselected
  8. Select any other form [TestForm] leaving any others unselected
  9. Click [OK] to save the changes
  10. Click the "Forms Assigned" button
  11. Validated [PMForm1CWS] is selected and [PMForm2cws] is not, as expected
  12. Validate [TestForm] is still selected and all other forms are still unselected, as expected
  13. Now deselect form [PMForm1CWS] and select [PMForm2CWS]
  14. Click [OK] to save the changes
  15. Click the "Forms Assigned" button
  16. Validated [PMForm2CWS] is selected and [PMForm1CWS] is not, as expected
  17. Validate [TestForm] is still selected and all other forms are still unselected, as expected
  18. Click [OK]
  19. Click [File] to create the tab and save the changes made
  20. Validate submission is successful and exit the form
  21. Open the "All Documents Widget Definition" form.
  22. Select the "Multi-Form Tab" section and select "Edit"
  23. Select tab [CrossNamespaceTab] for edit
  24. Click the 'Forms Assigned" button
  25. Validated [PMForm2CWS] is selected and [PMForm1CWS] is not, as expected
  26. Validate [TestForm] is still selected and all other forms are still unselected, as expected
  27. Click [OK]
  28. Exit the form
Topics
• All Documents Widget • All Documents Widget Definition • Forms
AV-91264 Summary | Details
All Document Widget - forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
Scenario 1: 'All Document Widget"- (Form attached to a menu from another application) - "Tab" Form/Data validations
Specific Setup:
  • Have a form in any application that can be used for testing. For this testing "Avatar CWS" is used. [CWSForm]
  • In another application, (e.g. Avatar PM), open form "Attach Other Application Form to Menu'
  • In the "Application" field select the 'Avatar CWS' application and in the "Form To Attach" choose [CWSForm]
  • In the "Menu to Place Form Under" choose a desired "PM" menu for the "CWS" form
  • Update "Form Description" field as a desired distinguishable name for "CWS" form that will appear on the "PM" menu [CWSFormPM]
  • Submit the form
  • In form "All Documents Widget Definition", have an all document widget defined [AllDocWidget]
  • The logged in user has the [AllDocWidget] as their home view
  • The logged in user has access to form "All Document Widget Definition" and [CWSForm] and [CWSFormPM]
Steps
  1. Open the "All Documents Widget Definition" form.
  2. Select the "Multi-Form Tab" section and select "Edit"
  3. From the "Select Tab" field, select any existing Tab [CrossNamespaceTab]
  4. Click the "Forms Assigned" button
  5. Select [CWSFormPM], the form attached from a "PM" forms list
  6. Do not select [CWSForm] from the "CWS" forms list, the form used to attach to the other application menu
  7. Click [OK]
  8. Click the "Forms Assigned" button
  9. Validate [CWSformPM] is selected and [CWSForm] is not, as expected
  10. Click [OK] to save the changes
  11. Click [File] to save the tab changes
  12. Navigate the home view
  13. Select a desired client [TestClient]
  14. From the "PM" menu open form [CWSFormPM]
  15. Populate the desired fields and submit the form
  16. At the homeview, click to refresh the [AllDocWidget]
  17. Click the [CrossNamespaceTab] tab
  18. Validate a data row is present in the widget for the row submitted in step 2
  19. Validate "Form Description" field for the row is [CWSForm] as expected. [Note: the name from the original form name used to attach to the other application menu, will always display]
  20. Validate all other column data is displayed, as expected
  21. Navigate back to the home view
  22. Select a desired client [TestClient]
  23. This time from the "CWS" menu, open form [CWSForm]
  24. Populate the desired fields and submit the form
  25. Navigate back to the [AllDocWidget] and click to refresh the widget
  26. Click the [CrossNamespaceTab] tab
  27. Validate a data row is present in the widget for the row submitted in step 4
  28. Validate "Form Description" field for the row is [CWSForm] as expected.
  29. Validate all other column data is displayed, as expected
Topics
• All Documents Widget • All Documents Widget Definition • Forms
AV-92271 Summary | Details
All document Widget - form data rows
Scenario 1: 'All Documents' widget - Form data row validations
Specific Setup:
  • A client is enrolled in an existing episode [TestClient]
  • Have two modeled forms [FormA] and [FormB]
  • [FormA] is based on a table that is "Date" sorted. [Note: this is configured with prompt "Is This Table Date Sorted" set to "Yes" in "Table Definition"]
  • [FormB] is not based on a table that is "Date Sorted"
  • Have any other desired form [FormC],
  • [FormC] has many rows of data submitted for a client[TestClient], for example four hundred rows or more
  • Have the registry setting "Enable Risk Level Functionality" enabled
  • Have access to the "Risk Level Update" for [TestClient].
  • Have an "All Documents Widget" created [AllDocsWidget], in form " All Documents Widget Definition"
  • Have [FormA], [FormB], [FormC] and the "Risk Level Update" from, added for selection in any tab in the widget, For this test, the "All Forms" tab is used
  • The logged in user has access to all forms in the setup above and the "All Documents Widget Definition" form
  • The logged in user has the "All Document Widget" on their home view
Steps
  1. Select a client [TestClient]
  2. Open [FormA] (Modeled Form 'Date Sorted')
  3. Select an episode
  4. Populate the required "Date Sorted" date field with a date other than the current date
  5. Populate any desired fields
  6. Submit the form
  7. Validate the form files successfully
  8. Note the current date and the "Date Sorted" date entered in step 2b
  9. Open [FormB] (Modeled form not 'Date Sorted')
  10. Select an episode
  11. Populate any desired fields
  12. Submit the form
  13. Validate the form files successfully
  14. Note the submission the date and time
  15. Open the "Risk Level Update" form
  16. Add a row the "Risk Level Change" grid
  17. Populate the "Date of Change" field. Make note of the date value.
  18. Populated other fields, as required
  19. Submit the form
  20. Validate the form submits successfully
  21. At the home view, select [TestClient]
  22. Navigate to the "All Documents Widget" and click the "Refresh" button
  23. Click the "All Forms" tab
  24. Select [FormA] from the 'Form Description' field.
  25. Validate the "Form Description" field is populated with the form name for [FormA]
  26. Select the episode from the "Episode" field
  27. Validate the "Date" column field value, is populated with the "Date Sorted" date noted in step 2d
  28. Validate the "Time" column field value is 'not' populated. [This modeled form based on a table that is "Date Sorted". By design, for tables that are date sorted, the "Date" field will be populated with the sort date instead of the "Date Entry Date" and the "Time" field will be left unpopulated]
  29. Validate each of the columns are populated, as expected
  30. Select [FormB] from the 'Form Description' field.
  31. Validate the "Form Description" field is populated with the form name for [FormB]
  32. Select the episode from the "Episode" field
  33. Validate the "Date" column is populated with the date noted in step 3, which is the 'Date Entry Date'
  34. Validate the "Time" field is populated, as expected with time noted in step 3, which is the "Date Entry Time"
  35. Validate each of the columns are populated, as expected
  36. Select the "Risk Level Update" from the 'Form Description' field.
  37. Validate the "Form Description" field is populated with the form name for [FormA]
  38. Select the episode from the "Episode" field
  39. Validate the "Date" column is populated with "Date of Change" date noted in step 4.[Note: This product form is based on a table that is "Date Sorted". By design, for tables that are date sorted, the "Date" field will be populated with the sort date instead of the "Date Entry Date" and the "Time" field will be left unpopulated]
  40. Validate the "Time" field is 'not' populated, as expected. [Note: as the date displayed in "Date" column field is the data sorted date not the date entry date, by design, the "Time" field value will be blank]
  41. Validate other columns are populated, as expected
  42. Select [FormC] from the 'Form Description' field.
  43. Validate in the right-hand corner of the widget, a counter is displayed indicting "50 of xxx rows"
  44. For example, for this test "50 of 450 rows" is displayed
  45. Validate all "50" rows are displayed, as expected
  46. In the center of the widget, at the bottom
  47. Validate there are left arrow and right arrow navigation buttons bracketing the number of pages of data. For example: < 1 2 3 4 5 >
  48. Validate the page "1" navigation link is currently highlighted
  49. Click the right arrow navigation button again
  50. Validate the next 50 rows are displayed along with previous rows, as expected
  51. Validate in the lower right corner, the counter changes to "100 of 450 rows"
  52. Validate the page "2" navigation link is currently highlighted
  53. Click the right arrow navigation button again
  54. Validate the next 50 rows are displayed along with previous rows, as expected
  55. Validate the counter changes to "200 of 450 rows"
  56. Validate the page "3" navigation link is currently highlighted
  57. Click the right arrow navigation button again
  58. Validate the next 50 rows are displayed along with previous rows, as expected
  59. Validate the counter changes to "250 of 450 rows"
  60. Validate the page "4" navigation link is currently highlighted
  61. If applicable, repeat the last step by clicking the right arrow till the last page is displayed
  62. Validate the next 50 rows are always displayed along with previous rows, as expected
  63. Validate the counter changes to "300 of 450", "350 of 450", "400 of 450" etc., as expected
  64. Validate the page number navigation link increments by one for each page, and is highlighted
Topics
• All Documents Widget