Skip to main content

RADplus 2022 Update 10

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Recommended Update Level

RADplus 2018 Update 80
RADplus 2018 Update 102

Product Update Form Description

The following issues are resolved: One instance of the error [SYNTAX]EVENT+31^GUILIB4 which occurs on User Modeled forms with an event setting a prompt value to a Summation result which is triggered with the 'Include' or 'Not Include' comparison. Data from tables joined to SYSTEM.appt_data or SYSTEM.appt_data_all may not appear in Schedule Widgets. The errors [UNDEFINED]Delete+12^GUIObjectALIAS or [UNDEFINED]EDIT+16^GUIObjectALIAS which occur when a User Modeled table with multiple table aliases has one table alias removed. Also, Multiple System Code validations are revised for performance improvement.

Included Updates

None

Required Updates

None

Details
NEW0 CHANGED2 FIXED2
Changed (2)
Modeled Form
An issue is resolved to ensure that a user modeled form with an event set on prompt to trigger a 'Summation' result, returns the expected value. KB0066892 v1.0
Value Added: Improved form modeling.
Topics
• Modeling • NX
 
Sub System Codes
Improvements are made to validations done when a user is logged in to a sub system code, in "Multiple System Code" enabled environments
Value Added: Improves the validation functionality used when user is logged into a sub system code
Topics
• NX
 
Fixed (2)
Scheduling Widgets
An issue is resolved to ensure that a "Scheduling Widget" containing a query that joins to the "SYSTEM.appt_data" or "SYSTEM.appt_data_all" tables in order to extract data, displays the data successfully KB0068873 v0.01
Topics
• Console Widget Configuration • Scheduling Calendar
 
Modeled form - with "Table" alias
An issue is resolved where an error could occur deleting a row submitted in a modeled form that contains fields mapped using a "Table" alias KB0067838 v0.01
Topics
• NX
 
Acceptance Tests
AV-72838 Summary | Details
Modeled Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ok - Cancel Dialog
Scenario 1: Modeled Form - Validate results of an "Event" defined on field using the "Sum" calculation type
Specific Setup:
  • A client with an existing episode is identified. [Client A].
  • Have access to a user modeled form [Form A] defined with:
  • Four 'Dictionary" fields, for this example: [FieldA], [FieldB], [FieldC] and [FieldD] are used
  • Each dictionary field has two or more numerical values for selection
  • One "Integer" type field [FieldE]
  • In 'Form Definition', for [FieldD], define an event that will sum the values in fields [FieldA], [FieldB], [FieldC] and [FieldD] and populate that value in [FieldE], when as specific value [TriggerValue] is selected in [FieldD].
  • This can be done with the following event setup on [FieldD]:
  • 'Type of Event' is "Result of Input With Value Checking".
  • 'Compare with For Event' is "Specific Value", with the "Specific Value (Dictionary)" field set to the [TriggerValue]
  • 'Relationship to Comparison Value' to Trigger Event ' is "Include"
  • 'Table Column to Have Value Changed on Event': [FieldE]
  • 'Set Table Column Value' is "Calculation Result".
  • 'Calculation Type' is "Sum".
  • 'Fields for Summation': [FieldA], [FieldB], [FieldC] and [FieldD]
Steps
  1. Select [ClientA]
  2. Access [FormA]
  3. In [FieldA], select a dictionary value
  4. In [FieldB], select dictionary value
  5. In [FieldC], select dictionary value
  6. In [FieldD], select a dictionary value other than the [TriggerValue] defined in the set up
  7. Validate [FieldE] is not populated with any summation value, as expected
  8. In [FieldD] select the [TriggerValue] defined in the set up
  9. Validate the expected summation value is populated in [FieldE] (sum of [FieldA] thru [FieldD]).
  10. Click [Submit]
  11. Validate the form files successful
  12. Access [FormA]
  13. Select the row filed in step 2
  14. Validate all fields are populated, as expected

"
Topics
• Modeling • NX
AV-73708 Summary | Details
Scheduling Widgets
Scenario 1: Scheduling Widget - Data validations
Specific Setup:
  • In form "Console Widget Configuration", have the following two "Scheduling" widgets defined:
  • [WidgetA] - Includes an "SQL Query" to display data in the "SYSTEM.appt_data" table and includes fields; "ApptDate", "StartTime", "ClientID", "StaffID", "Staff_Name" and "User Logged In"
  • [WidgetB] - Includes an "SQL Query" to display data in the "SYSTEM.appt_data_all" table and includes fields; "ApptDate", StartTime", "Staff_Name", StaffID and "User Logged In"
  • Have both widgets placed on the home view for [UserA]
  • Log in as [UserA]
Steps
  1. On the home view, refresh [WidgetA]
  2. Valid the "ApptDate" column contains the expected data
  3. Valid the "StartTime" column contains the expected data
  4. Valid the "ClientID" column contains the expected data
  5. Valid the "StaffID" column contains the expected data
  6. Valid the "Staff_Name" column contains the expected data
  7. Valid the "UserLoggedIn column contains the expected data
  8. On the home view, refresh [WidgetB]
  9. Valid the "ApptDate" column contains the expected data
  10. Valid the "StartTime" column contains the expected data
  11. Valid the "StaffID" column contains the expected data
  12. Valid the "Staff_Name" column contains the expected data
  13. Valid the "UserLoggedIn column contains the expected data
Topics
• Console Widget Configuration • Scheduling Calendar
AV-73772 Summary | Details
Modeled form - with "Table" alias
Scenario 1: Modeled form with table aliasing - validations
Specific Setup:
  • Have a modeled table, [TableA] that contains:
  • Fields mapped to a "Table" alias [Alias1], for example the "Treatment History" table alias
  • Fields mapped to another "Table" alias [Alias2], for example the ""Patient Notes" table alias
  • Have a modeled form [FormA] that contains fields from [TableA] in two sections:
  • [Section1] contains just fields mapped to table alias [Alias1]
  • [Section2] contains just fields mapped to table alias [Alias2]
  • For [ClientA] in [EpisodeA], populate the fields available in [FormA] and file two rows of data [Row1] and [Row2]
  • Create another table in "Table Definition" [TableB] which includes the same fields mapped in [Alias2] from the "Patient Notes" table alias
  • In "Form Definition", edit [FormA]
  • Add [TableA] as a secondary table
  • Edit [Section2], and replace the "Table" aliased fields from [TableA] with the same ones form [TableB] and submit the form
Steps
  1. Open [FormA]
  2. Select [ClientA]
  3. Select [Episode1]
  4. In the pre-display, validate [Row1] and [Row2] a displayed for selection
  5. Select [Row1]
  6. Click the [Delete] button to delete the row
  7. Click [Yes] to confirm the deletion
  8. Exit the form
  9. Open [FormA]
  10. Select [ClientA]
  11. Select [Episode1]
  12. In the pre-display, validate [Row1] is no longer present and [Row2] a displayed, as expected
  13. Select [Row2]
  14. Click the [Edit] button to edit the row
  15. Edit any field on the form [FieldA]
  16. Click [Submit]
  17. Validate the form files successfully
  18. Open [FormA]
  19. Select [ClientA]
  20. Select [Episode1]
  21. In the pre-display, select [Row2]
  22. Click the [Edit] button to edit the row
  23. Validate the change made to [FieldA] is present, as expected
Topics
• NX
AV-74908 Summary | Details
Sub System Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
Scenario 1: Sub System Code's - User access to clients validation
Specific Setup:
  • Have a system with multiple system code functionality enabled
  • Have system has a root system code [RootA] and three sub system codes on the system
  • [SubA] - assigned to only "ProgramA"
  • [SubB] - assigned to only "ProgramB"
  • [SubC] - assigned to only "ProgramC"
  • User "STAFFA" has three clients in his caseload
  • "ClientA" - admitted to "ProgramA"
  • "ClientB" - admitted to "ProgramB"
  • "ClientC" - admitted to "ProgramC"
Steps
  1. Log into the root system code [RootA] as [StaffA]
  2. Validate "ClientA", "ClientB" and "ClientC" are displayed in the user's "My Clients" widget
  3. Select each client and open any client based form, for example "Update Client Data"
  4. Add or edit any data and submit the form
  5. Validate the form files successfully
  6. Log out of [RootA]
  7. Log into sub system code, [SubA]
  8. Validate "ClientA" is displayed in the users in the user's "My Clients" widget
  9. Validate "ClientB" and "ClientC" are not displayed in the user's "My Clients" widget
  10. In the "Search Clients" field, search for "ClientB"
  11. Validate "ClientB" is not found
  12. In the "Search Clients" field, search for "ClientC"
  13. Validate "ClientC" is not found
  14. Select "ClientA" and open any client based form,
  15. Add or edit any data and submit the form
  16. Validate the form files successfully
  17. Log out of [SubA]
  18. Log into sub system code, [SubB]
  19. Validate "ClientB" is displayed in the user's "My Clients" widget
  20. Validate "ClientA" and "ClientC" are not displayed in the user's "My Clients" widget
  21. In the "Search Clients" field, search for "ClientA"
  22. Validate "ClientA" is not found
  23. In the "Search Clients" field, search for "ClientC"
  24. Validate "ClientC" is not found
  25. Select ClientA open any client based form,
  26. Add or edit any data and submit the form
  27. Validate the form files successfully
  28. Log out of [SubB]
  29. Log into sub system code, [SubC]
  30. Validate "ClientC" is displayed in the user's "My Clients" widget
  31. Validate "ClientA" and "ClientB" are not displayed in the user's "My Clients" widget
  32. In the "Search Clients" field, search for "ClientA"
  33. Validate "ClientA "is not found
  34. In the "Search Clients" field, search for "ClientB"
  35. Validate "ClientB" is not found
  36. Select "ClientC" open any client based form,
  37. Add or edit any data and submit the form
  38. Validate the form files successfully
Topics
• NX

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Reference
  2. Tags
    1. content:release
    2. llm-no-index
    3. role:sysadmin
    4. search:ready