Skip to main content

Avatar Cal-PM 2023 Update 70

Product Requirements and Recommendations

Avatar Cal-PM required
RADplus required

Recommended Update Level

Avatar Cal-PM 2023 Monthly Release 2023.03.02
RADplus 2023 Monthly Release 2023.03.02

Product Update Description

Storage for the 'Family Registration' form is optimized to improve performance for reporting purposes. This includes the tables "SYSTEM.family_current_demographics", "SYSTEM.family_umdap_info" and "SYSTEM.family_membership_information".

Required Updates

None

Included Updates

3, 5, 7, 8, 11, 13, 16, 17, 21, 24, 26, 28, 32, 38, 39, 43, 45, 46, 47, 48, 51, 52, 54, 56, 61, 63, 65, 66, 67, 69

Details

NEW1 CHANGED0 FIXED0
New (1)
Family Registration - cache storage table optimization.
Storage for the 'Family Registration' form is optimized to improve performance for reporting purposes.
Value Added: Performance of the cache storage tables for Family Registration form is optimized.
Topics
• Family Registration
 
Acceptance Tests

AV-53139 Summary | Details
Family Registration - cache storage table optimization.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Family Registration (CAL)
  • Change MR#
Scenario 1: Family Registration form - field validation - Successful registration.
Specific Setup:

Registry Settings:

  • Set the registry setting 'UMDAP Housing Adjustment Percentage' as any desired percentage value within the range of 1 to 100.

Form designer:

  • Add the hidden elements 'Housing Costs' and 'Housing Adjustment' under the Third Subsection of the UMDAP Information Tab.

Clients:

  • More than one existing client is identified or new ones are created to be used in the family registration process.
  • Client 1
  • Client 2

Family:

  • An existing family with no member(s) and with all the UMDAP data should be identified or created.
  • Family A
Steps
  1. Open the "Family Registration" form.
  2. Enter a desired name for the Family - 'Family B'.
  3. Click [New Family].
  4. Fill in all the needed field values in the "Family Registration" section.
  5. Click on the "Family Members" section.
  6. Select the [Add New Item].
  7. Add 'Client 1' and 'Client 2' as the members.
  8. Fill in all the needed field values in the "Family Members" section.
  9. Verify the "Type of Family Member" column displayed in the "Family Membership Information" grid. Note: as this grid contains many fields, you may need to drag the border between fields to widen the view of this, or any of the other, fields in the grid.
  10. Select the "UMDAP Information" section.
  11. Click [Add New Item].
  12. Validate that the fields "Housing Costs" & "Housing Adjustment" are present in the form.
  13. Fill in all the mandatory field values along with the other desired optional field values.
  14. Click [Submit].
  15. Create an SQL query to the below tables and validate that the above-filed data are saved and shown in the respective cache storage tables,
  16. Validate the Family Demographics information in "SYSTEM.family_current_demographics",
  17. Validate the Member information(s) in "SYSTEM.family_membership_information",
  18. Validate the UMDAP information in "SYSTEM.family_umdap_info".
  19. Close the SQL, return to the NX window, and open the 'Family Registration' form.
  20. Select 'Family A'.
  21. Click on the "Family Members" section.
  22. Verify that no members are existing in the grid.
  23. Select the [Add New Item].
  24. Add 'Client 1' as a member.
  25. Verify that we see an error message stating that there is a Date Range Overlap found with Another Family Assignment for the date range.
  26. Click [OK].
  27. Click [Discard].
  28. Click [Yes].
  29. Open the 'Family Registration' form.
  30. Select 'Family B'.
  31. Click on the "Family Members" section.
  32. Select 'Client 1' from the grid.
  33. Click [Edit Selected Item].
  34. Enter a future date value for the field 'End Date Of Family Membership date'.
  35. Click [Submit].
  36. Create an SQL query to the below table for 'Family B' and validate that 'Client 1' is updated with the 'fam_memb_end_date' value,
  37. "SYSTEM.family_membership_information".
  38. Close the SQL, return to the NX window, and open the 'Family Registration' form.
  39. Select 'Family A'.
  40. Click on the "Family Members" section.
  41. Verify that no members are existing in the grid.
  42. Select the [Add New Item].
  43. Add 'Client 1' as a member.
  44. Enter a date value that falls between the 'Start Date Of Family Membership date' and 'End Date Of Family Membership date' range of 'Client 1' in 'Family B'.
  45. Verify that we see an error message for 'Date Range Overlaps Another Family AssignmentFamily'.
  46. Click [OK].
  47. Enter a date value that is outside the 'Start Date Of Family Membership date' and 'End Date Of Family Membership date' range of 'Client 1' in 'Family B'.
  48. Click [Submit].
  49. Create an SQL query to the below table for Family A and validate that Client 1 is added as a member of the family.
  50. "SYSTEM.family_membership_information".
  51. Create an SQL query to the below table for Family B and validate that Client 1 is also showing with the 'fam_memb_end_date' value.
  52. "SYSTEM.family_membership_information".
  53. Close the SQL.
Scenario 2: Family Registration form - Delete/ Change MR#/ Merge - Clients.
Specific Setup:

Family Registration:

  • A family with more than one member and with all the UMDAP data should be identified or created.
  • Family A:
  • Member 1 (Client 1)
  • Member 2 (Client 2)

Clients:

  • Adding to the above clients, An existing client is identified or a new one is created for the Client Merge process. The client identified/created should have the same information (except for the program) as the member whom we want to merge with.
  • Client 3
Steps
  1. Open the "Family Registration" form.
  2. Enter the Family ID for - 'Family A'.
  3. Select Family A.
  4. Click on the "Family Members" item.
  5. Verify that the members exist and are shown in the grid.
  6. Select 'Member 2' from the grid.
  7. Click [Delete Selected Item].
  8. Click [Yes].
  9. Verify that the member we deleted is removed from the grid, upon successful delete.
  10. Select the "UMDAP Information" item.
  11. Verify that the existing UMDAP record(s) are shown in the grid.
  12. Click [Submit].
  13. Create an SQL query to the below table for Family A and validate that there are no records found for 'Client 2',
  14. "SYSTEM.family_membership_information".
  15. Create an SQL query to the below table for 'Family A' and validate that there are UMDAP data available, which is the same as the data we filed using the 'Family Registration form',
  16. "SYSTEM.family_umdap_info".
  17. Close the querying window and return to the NX window.
  18. Open the "Family Registration" form.
  19. Enter the Family ID for - 'Family A'.
  20. Select 'Family A'.
  21. Click on the "Family Members" item.
  22. Verify that the members exist and are shown in the grid.
  23. Click [Add New Item].
  24. Enter the 'Client ID' field with 'Client 1' and select it.
  25. Verify that we see a popup that says that there is a Date Range Overlap found with the Previous Entry For ClientStart and End Date(s).
  26. Click [OK].
  27. Enter the 'Client ID' field with 'Client 2' and select it.
  28. Fill in all the needed values.
  29. Verify that the new member is now added and shown in the grid.
  30. Select the "UMDAP Information" item.
  31. Select the existing record from the 'UMDAP Information' grid.
  32. Click [Delete Selected Item].
  33. Click [Yes].
  34. Verify that there are no records in the 'UMDAP Information' grid.
  35. Click [Submit].
  36. Create an SQL query to the below table for 'Family A' and validate that there is an existing record found for 'Client 2',
  37. "SYSTEM.family_membership_information".
  38. Create an SQL query to the below table for 'Family A' and validate that there are no UMDAP data available,
  39. "SYSTEM.family_umdap_info".
  40. Close the querying window and return to the NX window.
  41. Open the "Change MR#" form.
  42. Enter the 'Client ID' field with 'Client 2' and select it.
  43. Click [Assign MR#].
  44. Click [Yes].
  45. Validate that the 'New Client ID#' input box contains a new ID - 'New Client 2'.
  46. Click [Submit].
  47. Open the "Family Registration" form.
  48. Enter the Family ID for - 'Family A'.
  49. Select 'Family A'.
  50. Click on the "Family Members" item.
  51. Verify that the members exist and are shown in the grid.
  52. Select 'Member 2' from the grid.
  53. Click [Edit Selected Item].
  54. Validate that the Client ID is replaced with the new MR#. (i.e. 'New Client 2').
  55. Click [Discard].
  56. Click [Yes].
  57. Create an SQL query to the below table for Family A and validate that there are no records found for 'Client 2',
  58. "SYSTEM.family_membership_information".
  59. Verify that we do have a record for 'New Client 2' in the table for 'Family A'.
  60. Close the querying window and return to the NX window.
  61. Open the "Client Merge" form.
  62. Enter the 'Client ID' field with 'New Client 2' and select it.
  63. Select the Episode value from the 'Source Client Episode' dropdown field.
  64. Enter the 'Client ID' field with 'Client 3' and select it.
  65. Click [File].
  66. Click [Yes].
  67. Click [OK].
  68. Click [Discard].
  69. Click [Yes].
  70. Open the "Family Registration" form.
  71. Enter the Family ID for - 'Family A'.
  72. Select 'Family A'.
  73. Click on the "Family Members" item.
  74. Verify that the members exist and are shown in the grid.
  75. Select 'Member 2' from the grid.
  76. Click [Edit Selected Item].
  77. Validate that the Client ID is replaced with 'Client 3'.
  78. Click [Discard].
  79. Click [Yes].
  80. Create an SQL query to the below table for 'Family A' and validate that there are no records found for 'New Client 2',
  81. "SYSTEM.family_membership_information".
  82. Verify that we do have a record for 'Client 3' in the table for 'Family A'.
  83. Close the SQL.
Topics
• Family Registration
Table Changes

Table Column Change
family_umdap_info Changed to cahce storage
family_current_demographics Changed to cache storage
family_membership_information Changed to cache storage