Skip to main content

Avatar Cal-PM 2024 Update 7

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

Avatar Cal-PM required
RADplus required

Recommended Update Level

Avatar Cal-PM 2024 Monthly Release 2024.00.00
RADplus 2022 Update 96
RADplus 2024 Monthly Release 2024.00.00

Product Update Description

Avatar Cal-PM is enhanced to support the "Family Member(s)" 'Type of Column' in 'Table Definition' (Column Definition) which is introduced via RAD 2022 Update 96.

Required Updates

None

Included Updates

None

Details
NEW1 CHANGED0 FIXED0
New (1)
RADPlus - Family Entity Modeling
Avatar Cal-PM is enhanced to support a new "Family Member(s)" type column available in the 'Table Definition' form called "Family Member(s)". This column will be available for Modeled forms created using the "Family" Entity Database. Family member "PATID's" are associated to a family in the 'Family Registration' form. The column will display for selection, all the PATID's associated to the "Family" in a multi-select field called "Family Member(s)". Please Note: "RADplus 2022 Update 96" is required for full functionality
Value Added: Support for the "Family" entity database for modeling forms
Topics
• Change MR# • Family Registration • Modeling
 
Acceptance Tests
AV-86975 Summary | Details
RADPlus - Family Entity Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
  • Crystal Reports or other SQL Reporting tool (ReportA)
  • Delete Last Movement
  • Family Registration
  • High Utilizier
  • Table Definition (PM)
  • Delete Family
Scenario 1: Change MR# - "Family" Entity Data validations
Specific Setup:
  • Have an active test client on the system [ClientA], note their current PATID# [OrigPATID#].
  • In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing.
  • A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved.
  • Have a report [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
Steps
  1. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table.
  2. Validate there is a row displayed for [FamilyA] and [ClientA].
  3. Open "Change MR#" form in Avatar PM.
  4. Select [ClientA] in the "Client ID" field and note their current PATID [OrigPATID#].
  5. Click [Assign MR#].
  6. Note the new PATID# assigned, [NewPATID#].
  7. Click [Submit].
  8. Validate the form files successfully.
  9. At the home view, search for the [OrigPATID#] noted in step 3a.
  10. Validate there are no results.
  11. Now search for the [NewPATID#] noted in step 3b.
  12. Validate the [NewPATID#] is found and the associated client is [ClientA].
  13. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
  14. Validate there is a row displayed for [FamilyA] and with new PATID# [NewPATID#] displayed for [ClientA].
Scenario 2: Client Delete - "Family" Entity Data validations
Specific Setup:
  • Have an active test client on the system [ClientA].
  • In form "Family Registration", have a family created [FamilyA] with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing.
  • A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved.
  • Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table.
  • User has launched [ReportA] and has logged into the system.
Steps
  1. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table.
  2. Validate there is a row displayed for [FamilyA] and [ClientA].
  3. Open "Client Delete" form.
  4. Select [ClientA] in the "Client ID" field.
  5. Validate an error message is received "Client Must Be Removed From All Families Before Client Can Be Deleted."
  6. Click [OK].
  7. Close the form.
  8. Open form "Family Registration".
  9. Select [FamilyA].
  10. Click the "Family Members" section.
  11. Select the row for [ClientA].
  12. Click [Delete].
  13. Validate the client is removed as a family member.
  14. Submit the form.
  15. Open form "Delete Last Movement".
  16. Select [ClientA].
  17. Select the admission episode from the "Episode Number" field.
  18. Click [Submit].
  19. Click [Yes] to continue.
  20. Validate the form submits successfully.
  21. Open "Client Delete" form.
  22. Select [ClientA] in the "Client ID" field.
  23. Click [Submit].
  24. Validate the form submits successfully.
  25. At the home view, search for [ClientA].
  26. Validate there are no results.
  27. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table.
  28. Validate there is no longer a row displayed for [FamilyA] and [ClientA].
Scenario 3: "Family" Entity User Modeled Form - Create a new form
Specific Setup:
  • In form "Family Registration" have a family created [FamilyA] with one or more clients added as family member's in "Family Members" section of the form.
Steps
  1. Open form "Envelope Definition".
  2. Click [New Avatar Envelope].
  3. Set the "Envelope Description" field to the desired name [EnvelopeA], for the envelope.
  4. Select "Family" in the "Entity Database" field.
  5. Click the "Yes - Is Envelope Eligible for Export" field.
  6. Click the "Yes - Always Allow Export" field.
  7. Click [Submit].
  8. Validate the form files successfully.
  9. Open form "Table Definition".
  10. At the "Select Avatar Table" prompt enter the desired table name [TableA].
  11. Click [New Avatar Table].
  12. From the "Envelope" dialog field, select [EnvelopeA].
  13. Populate the "Table Name" field with the desired table name [TableA].
  14. Populate the "Table Description" field with the desired description of the table.
  15. Select the "Column Definition" section.
  16. Click [Add New Item].
  17. Select "Family Member(s)" column from the "Type of Column" field.
  18. Populate the "Column Name" field.
  19. Populate the "Column Description" field.
  20. Populate the "Column Label" field.
  21. Validate the "Column Definition" grid contains a row with values just populated.
  22. Click [Add New Item].
  23. Select "Draft/Final (Document Routing)" column from the "Type of Column" field.
  24. Populate the "Column Name" field.
  25. Populate the "Column Description" field.
  26. Populate the "Column Label" field.
  27. Validate the "Column Definition" grid contains a row with values just populated.
  28. Repeat step 4 for any other desired prompts to be added from the "Type of Column" field.
  29. Validate results are as expected.
  30. Click [Submit].
  31. Validate the form files successfully.
  32. Open form "Form Definition".
  33. At the "Select Avatar Table" prompt enter the desired form name [FormA]
  34. Click [New Avatar Form].
  35. From the "Envelope" dialog, select [EnvelopeA].
  36. Populate the "Table Name" field with the desired table name [TableA].
  37. Populate the "Table Description" field with the desired description of the table.
  38. Select a menu location for the form from the "Menu to Place Form Under" field.
  39. Populate the "Form Name" field [FormA].
  40. In the "Primary Table" field, select [TableA].
  41. Click the "Pre-display" section.
  42. Select one or more pre-display columns from the "Primary Table Pre-display" column prompts.
  43. Click the "Section Definition" section.
  44. Click [Add New Item] and populate the "Section Description" field.
  45. Click the "Object Definition" section.
  46. Click [Add New Item].
  47. From the "Table Column" field, select the "Family Member's" column.
  48. Validate the "Object Definition" grid reflect the column added.
  49. From the "Table Column" field, select the "Draft/Final" column.
  50. Validate the "Object Definition" grid reflect the column added.
  51. Repeat step b adding any other columns desired from the "Table Column" field.
  52. Validate the "Object Definition" grid reflect the columns added.
  53. Click [Submit].
  54. Validate the form files successfully.
  55. Open [FormA].
  56. At the "Select Family" prompt, select [FamilyA].
  57. Validate the form loads successfully.
  58. Verify the "Family Member's" field is present and contains each client added as a family member in the set up, along with a check box next to their name.
  59. Verify the "Draft/Final" field is present on the form.
  60. Verify any other fields added during "Form Definition" are present on the form, as expected.
  61. Select values for any desired fields on the form.
  62. Submit the form.
  63. Validate the form files successfully.
Scenario 4: "Family" Entity User Modeled Form - Form submission and Document Routing Validations
Specific Setup:
  • The "Document Management Defaults" form has "Family - User Defined Family" selected in the field "Select Entity Types Allowed".
  • The "Document Management Definition" form has been submitted with a "Form Name" [FName] associated to the "Family" entity in the "Entity Database" field.
  • In form "Family Registration" have a family created [Family] with family members added in "Family Members" section of the form. For the test [ClientA] and [ClientB].
  • Have a user modeled form [Form] created based on the "Family - User Defined Family" entity database.
  • [Form] contains fields from [Table] that include a "Family Member(s)" column type, a field using a "Draft/Final" column type and any other desired field types.
  • [Form] is enabled for document routing with form name [FName] selected in the "Select Type" field.
  • [User] is a staff member who has access to [Form] and [Table].
  • [User] has the "My To do's" widget on their home view.
  • Have a report [Report], set to display data in the "SYSTEM.user_modelled_fam_members" table.
  • Log in as [User].
Steps
  1. Access [Form].
  2. In the "Select Family" prompt, select [Family].
  3. Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB].
  4. Click "All", to select all members.
  5. Populate any other desired fields on the form.
  6. Select "Draft" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate the form files successfully.
  9. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table.
  10. Validate there is a row displayed for [Family] and [ClientA].
  11. Validate there is a row displayed for [Family] and [ClientB].
  12. Access [Form].
  13. In the "Select Family" prompt, select [Family].
  14. In the pre-display screen, click [Edit] to select the row filed in step 1.
  15. Validate all fields are populated, as expected.
  16. Close the form.
  17. Access [Form].
  18. In the "Select Family" prompt, select [Family].
  19. In the pre-display screen, select the row filed in step 1.
  20. Click [Delete].
  21. Validate the row is removed from the pre-display.
  22. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table.
  23. Validate the row field for [Family] and [ClientA], has been deleted.
  24. Validate the row field for [Family] and [ClientB], has been deleted.
  25. Access [Form].
  26. In the "Select Family" prompt, select [Family].
  27. Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB].
  28. Click "All", to select all members.
  29. Populate any other desired fields on the form.
  30. Select "Final in the 'Draft/Final' field.
  31. Click [Submit] and then [OK].
  32. Validate the "Confirm Document" screen displays all data submitted, including clients [ClientA] and [ClientB] listed in the "Family Member's field.
  33. Click [Accept and Route].
  34. Enter the password for the user in the 'Password' field and click [OK].
  35. At the "Route Document to" dialog, add [User] as an approver.
  36. Click [Submit].
  37. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table.
  38. Validate there is a row displayed for [Family] and [ClientA].
  39. Validate there is a row displayed for [Family] and [ClientB].
  40. Navigate to the "My To Do's" widget.
  41. Click the "New" tab.
  42. Validate the To Do for [Form] is present in the list.
  43. Validate the "Client" column indicates [Family].
  44. Click [Approve Document].
  45. Validate the document displays all data submitted, including clients [ClientA] and [ClientB] in the "Family Member's" field.
  46. Click [Accept].
  47. Validate the To Do is removed the widget, as expected.
Scenario 5: Delete Family - Form (Submission and Validations)
Specific Setup:
  • Have an active test client on the system [ClientA].
  • In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing.
  • File a row for [FamilyA], selecting [ClientA] selected in the "Family Members" field and routing the document to [UserA] to create To do.
  • [UserA] has the "My To do's" widget on their home view.
  • Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table.
  • [UserA] has launched [ReportA] and has logged into the system.
Steps
  1. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
  2. Verify a data row is displayed for the row filed in the set up for [FamilyA] that includes [ClientA].
  3. On the home view, validate a To do exists in the "My To do's" widget for the row filed in [FormA] in the set up.
  4. Open form "Delete Family".
  5. Select [FamilyA].
  6. Validate an error message is displayed stating "The Family has members on file. You must delete all family members in the Family Registration form prior to deleting the family".
  7. Click [OK].
  8. Open form "Family Registration".
  9. Select [FamilyA].
  10. Click the "Family Members" section.
  11. Select each family member row and click delete to remove the row.
  12. Submit the form.
  13. Open form "Delete Family".
  14. Select [FamilyA].
  15. Click [Submit].
  16. At the "Delete Family" dialog, click [Yes].
  17. Validate the message "Family has been Deleted" displays.
  18. Click [OK].
  19. Open form "Delete Family".
  20. Search for [FamilyA].
  21. Validate [FamilyA] is not found.
  22. Return to the "My To Do's" widget.
  23. Validate a To do is no longer present for [FormA] for [ClientA].
  24. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
  25. Verify there are no rows displayed for [FamilyA].
Topics
• Change MR# • Family Registration • Modeling
Table Changes
Table Column Change
SYSTEM.user_modelled_fam_members FACILITY new
SYSTEM.user_modelled_fam_members FAMID new
SYSTEM.user_modelled_fam_members PATID new
SYSTEM.user_modelled_fam_members form_namespace new
SYSTEM.user_modelled_fam_members parent_historic new
SYSTEM.user_modelled_fam_members parent_fld_num new
SYSTEM.user_modelled_fam_members data_entry_date new
SYSTEM.user_modelled_fam_members data_entry_by new
SYSTEM.user_modelled_fam_members data_entry_time new
SYSTEM.user_modelled_fam_members data_entry_by_option new
SYSTEM.user_modelled_fam_members data_entry_user_id new
SYSTEM.user_modelled_fam_members data_entry_user_name new
SYSTEM.user_modelled_fam_members option_desc new
SYSTEM.user_modelled_fam_members option_id new
SYSTEM.user_modelled_fam_members data_entry_utc new
SYSTEM.user_modelled_fam_members data_entry_timezone_info_all new
SYSTEM.user_modelled_fam_members data_entry_time_j new
SYSTEM.user_modelled_fam_members data_entry_offset new
SYSTEM.user_modelled_fam_members data_entry_timezone_short new
SYSTEM.audit_user_mod_fam_mem FACILITY new
SYSTEM.audit_user_mod_fam_mem FAMID new
SYSTEM.audit_user_mod_fam_mem PATID new
SYSTEM.audit_user_mod_fam_mem form_namespace new
SYSTEM.audit_user_mod_fam_mem parent_historic new
SYSTEM.audit_user_mod_fam_mem parent_fld_num new
SYSTEM.audit_user_mod_fam_mem data_entry_date new
SYSTEM.audit_user_mod_fam_mem data_entry_by new
SYSTEM.audit_user_mod_fam_mem data_entry_time new
SYSTEM.audit_user_mod_fam_mem data_entry_by_option new
SYSTEM.audit_user_mod_fam_mem data_entry_user_id new
SYSTEM.audit_user_mod_fam_mem data_entry_user_name new
SYSTEM.audit_user_mod_fam_mem option_desc new
SYSTEM.audit_user_mod_fam_mem option_id new
SYSTEM.audit_user_mod_fam_mem data_entry_utc new
SYSTEM.audit_user_mod_fam_mem data_entry_timezone_info_all new
SYSTEM.audit_user_mod_fam_mem data_entry_time_j new
SYSTEM.audit_user_mod_fam_mem data_entry_offset new
SYSTEM.audit_user_mod_fam_mem data_entry_timezone_short new