Skip to main content

RADplus 2022 Update 65

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Recommended Update Level

RADplus 2019 Update 81
RADplus 2022 Update 8

Product Update Form Description

The following issues are resolved: An issue where SQL field names do not appear in Form and Table Documentation, nor in the Form Designer dialog for ScriptLink. An issue where deactivated User Roles do not print in Display User Role although that option is selected. An issue where two widgets using the same title cannot both appear in View Definition.

Included Updates

8, 49

Required Updates

None

Details
NEW0 CHANGED0 FIXED4
Fixed (4)
View Definition - Form
An issue where two widgets using the same title would not display for selection in the "View Definition" form.
KB0069148 v0.01
Topics
• Console Widget
 
"SQL" table field name display
An issue where "SQL" table field names do not appear in "Form and Table Documentation" or in the "SQL Info" field properties section in "Form Designer"
Topics
• Form Designer • Forms • NX
 
Display User Role - Form
An issue where deactivated "User Roles" did not display in the report when the prompt "Include Deactivated User Roles" was selected
Topics
• NX • User Role Definition
 
Client Triggers - Form
An issue is resolved in form "Client Triggers" where the "Field" prompt on the "Field Based Triggers" section, would not display any field values for the table selected in the form
Topics
• Forms • My Clients • NX
 
Acceptance Tests
AV-72907 Summary | Details
View Definition - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
Scenario 1: View Definition - Validate Addition of a Widget
Specific Setup:
  • Have a view defined in form "View Definition" [TestViewA] with one or more widgets assigned to the view
  • Have two existing widgets [WidgetA] and [WidgetB] hat have the same widget name, that are not assigned yet to [TestViewA]. For this test:
  • [WidgetA] is the Netsmart product widget "Financial Eligibility (NTST_FINANCIAL ELIG)"
  • [WidgetB] is the console widget "Financial Eligibility [PATIENT500]". This widget can be created using the "Console Widget Configuration" form and selecting "Financial Eligibility [PATIENT500]" from the prompt "Form to Create Widget For" and then submitting the form
  • [ClientA] has data filed in form "Financial Eligibility"
  • Have two users [UserA] and [UserB]
  • [UserA] has access to form "View Definition"
  • [TestViewA] is assigned to a [UserB] as their home view
  • Log in as [UserA]
Steps
  1. Access the 'View Definition' form.
  2. Click [Select View].
  3. Select [TestViewA] from the "Select Views" list box
  4. Click [OK].
  5. Click [Launch View Designer]
  6. Validate [WidgetA] is present on the layout as expected
  7. In the "Available" widgets list, search for [WidgetA]
  8. Validate [WidgetA] is found and select the widget
  9. Click the right arrow icon to add it to the "Assigned" widget list
  10. Click and drag [WidgetA] to the layout section
  11. In the "Available" widgets list, search for [WidgetB]
  12. Validate [WidgetB] is found and select the widget
  13. Click the right arrow icon to add it to the "Assigned" widget list
  14. Click and drag [WidgetB] to the layout section
  15. Click [Submit] to return to exit the view designer and return to the main form and click [Submit].
  16. Validate that a 'Form Return' message is displayed stating: "Submitting has completed. Do you wish to return to form?"
  17. Click [No].
  18. Log out as [UserA] and login as [UserB]
  19. At the home view, click [Preferences] on the menu bar
  20. Select 'Widgets' from the tab selection.
  21. Click [Reload Home View].
  22. Validate that a 'Confirm Reload' message appears stating: "Are you sure you want to discard current changes and reload layout from server?"
  23. Click [Yes].
  24. Validate that [WidgetA] and [WidgetB] are no present on the view
  25. Click [Apply].
  26. At the home view
  27. Validate that [WidgetA] and [WidgetB] are now present on the home view
  28. Select [ClientA]
  29. Validate data is displayed in the widget, as expected
Topics
• Console Widget
AV-79555 Summary | Details
"SQL" table field name display
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
  • Form and Table Documentation (PM)
Scenario 1: "Form Designer - Validate the "SQL Info" table information
Specific Setup:
  • Have a product form [FormA] that contains an SQL Table [TableA] with one or more fields defined in the table. For example product form "Emergency Contact Information" containing table "SYSTEM.user_emergency_contact_information"
  • Have a modeled form [FormB] that contains an SQL Table [TableB] with one or more fields defined
  • Have access to form "Form Designer"
Steps
  1. Open form "Form Designer"
  2. Select the product form [FormA], from the "Forms" drop down list
  3. Select a section from the "Tabs" drop down list
  4. Click on [FieldA] in the form layout section.
  5. Click the "SQL Info" on the left side panel to display field and table name information
  6. Validate "Table Name" for the [TableA] reflects current SQL table name for example "SYSTEM.user_emergency_contact_information"
  7. Validate "Field Name" for the [FieldA] reflects current SQL table name, for example "Emergency_contact_name"
  8. Close the form
  9. Open form "Form Designer"
  10. Select the modeled form [FormB] from the "Forms" drop down list
  11. Select a section from the "Tabs" drop down list
  12. Click on [FieldB] in the form layout section.
  13. Click the "SQL Info" on the left side panel to display field and table name information
  14. Validate "Table Name" for the [TableB] reflects current SQL table name for example "SYSTEM.modeled_form"
  15. Validate "Field Name" for the [FieldB] reflects current SQL table name, for example "Clients_full_name"
  16. Close the form
Scenario 2: "Form and Table Documentation" - validate SQL table field names
Specific Setup:
  • Have a product form [FormA] that contains an SQL Table [TableA] with one or more fields defined in the table. For example product form "Emergency Contact Information" containing table "SYSTEM.user_emergency_contact_information"
  • Have a modeled form [FormB] that contains an SQL Table [TableB] with one or more fields defined
Steps
  1. Open 'Form and Table Documentation'.
  2. Set 'Type of Documentation' to 'Form'.
  3. Select "Individual" in the "Individual or All Forms" field
  4. Select [FormA] from the 'Form to be Documented' field
  5. Click [Process]
  6. Validate the "Form and Table Documentation" report, displays all field names and their associated SQL table names, as expected
  7. Click the "Page" field and go to the last page of the report
  8. Validate all field names and their associated SQL table names are listed, as expected
  9. Click [Close]
  10. Set 'Type of Documentation' to 'Form'.
  11. Locate and select [TableA] in field "Table(s) to be Documented"
  12. Click [Process]
  13. Validate the "Form and Table Documentation" report, displays all field names and their associated SQL table names, as expected
  14. Click [Close]
  15. Repeat step 1 for modeled [FormB] and [TableB]
  16. Validate results are as expected
Topics
• Form Designer • Forms • NX
AV-79910 Summary | Details
Display User Role - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Display User Role
  • Display User Role (Report)
Scenario 1: Display User Role - Include "Deactivated" Roles - Yes
Specific Setup:
  • Have a role defined in form "User Role Definition" with field "Deactivated" set to "No" [ActiveRoleA]
  • Have a role defined in form "User Role Definition" with field "Deactivated" set to "Yes" [DeactiveRoleA]
Steps
  1. Open form "Display User Role"
  2. Select "All" in the Individual or All User Roles" field
  3. Set field "Include Deactivated User Roles" to "Yes"
  4. Click [Process]
  5. Validate the "Display User Role" report is displayed
  6. Search for the active ole [ActiveRoleA]
  7. Validate the role is found
  8. Search for the deactivated role [DeactiveRoleA]
  9. Validate the role is found, as expected
  10. Close the report
  11. Select "Individual" in the Individual or All User Roles" field
  12. Click the "User Role" field
  13. Validate the drop down list contains [ActiveRoleA]
  14. Validate the drop down list also contains [DeactiveRoleA], as expected
Scenario 2: Display User Role - Include "Deactivated" Roles - No
Specific Setup:
  • Have a role defined in form "User Role Definition" with field "Deactivated" set to "No" [ActiveRoleA]
  • Have a role defined in form "User Role Definition" with field "Deactivated" set to "Yes" [DeactiveRoleA]
Steps
  1. Open form "Display User Role"
  2. Select "All" in the Individual or All User Roles" field
  3. Set field "Include Deactivated User Roles" to "No"
  4. Click [Process]
  5. Validate the "Display User Role" report is displayed
  6. Search for the "Active" role [ActiveRoleA]
  7. Validate the role is found
  8. Search for the "Active" role [DeactiveRoleA]
  9. Validate the role is not found, as expected
  10. Close the report
  11. Select "Individual" in the Individual or All User Roles" field
  12. Click the "User Role" field
  13. Validate the drop down list contains [ActiveRoleA]
  14. Validate the drop down list does not contain [DeactiveRoleA], as expected
Topics
• NX • User Role Definition
AV-80516 Summary | Details
Client Triggers - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Triggers (PM)
Scenario 1: Client Triggers (Form) - Field Validations
Specific Setup:
  • Have an "Alert" defined in form "Client Alerts" [AlertA]
Steps
  1. Open form "Client Triggers"
  2. Select [TableA] in the "Table" field
  3. Click to the "Table Based Triggers" section
  4. Click to "Add New Item"
  5. Select [AlertA] in the "Client Alert Type" field
  6. Select the desired value from the "Trigger On" field
  7. Select a value if desired from the "Offset Trigger Based On The Following Date Field"
  8. Populate the "Number of Days Alert Should be Active" field
  9. Populate the "Days Before/After Date Field to Offset Trigger" field
  10. Click to the "Field Based Triggers" section and
  11. Click to "Add New Item"
  12. Select [AlertA] in the "Client Alert Type" field
  13. Select the desired value in the "Trigger Alert for All Episodes" field
  14. Populate the "Number of Days Alert Should be Active" field
  15. Click the "Field" prompt
  16. Validate all the expected field valued for [TableA] are listed for selection
  17. Select a desired value
  18. Select the desired value in the "Type of Comparison" field
  19. Populate the "Comparison Value" field with the desired value
  20. Select a value if desired from the "Offset Trigger Based On The Following Date Field"
  21. Populate the "Days Before/After Date Field to Offset Trigger" field
  22. Submit the form
  23. Return to form "Client Triggers"
  24. Select [TableA] in the "Table" field
  25. Click to the "Table Based Triggers" section
  26. Validate all fields are populated as expected based on the value filed in step 1
  27. Click to the "Field Based Triggers" section
  28. Validate all fields are populated as expected based on the value filed in step 1
Topics
• Forms • My Clients • NX