Skip to main content

RADplus 2023 Update 32

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Product Update Form Description

The following issues are resolved: 1) The error '[SUBSCRIPT]Import2+116^User.RadPlusCSMOption.1', which may occur when importing form designer changes. 2) The 'T' and 'Y' components of date fields may not respond on forms modified with 'Form Designer'. 3) Importing form designer changes in myAvatar NX may clear ScriptLink settings for the form. 4) The error '[UNDEFINED]PrintHTML+21^UICHARTHTML', which may occur in customized console widgets.

Included Updates

None

Required Updates

None

Details
NEW0 CHANGED0 FIXED4
Fixed (4)
Form Designer - field labels
An issue is resolved to ensure that an envelope containing a modeled form with a field label that was modified in "Form Designer", to include a tilde '~' character within its name, can exported and then imported successfully
Topics
• Envelope Import • NX
 
Form Designer - Date field components
An issue is resolved where importing an envelope containing a form with form designer changes, may cause the 'T' and 'Y' components of any date fields on the form not to respond
Topics
• Envelope Import • NX
 
Form Designer- ScriptLink settings
An issue is resolved to ensure that when importing form designer changes in Avatar NX, that any "ScriptLink" settings existing on form remain intact.
Topics
• NX • Scriptlink
 
Console Widgets - SQL query override
An issue is resolved to ensure "Console" widgets using "SQL Query Override" statements to display data that use a query with no episode included in the row link, can be displayed successfully in the "Console Widget Viewer" widget
Topics
• Console Widget
 
Acceptance Tests
AV-75201 Summary | Details
Form Designer - field labels
Scenario 1: Envelope Import (with Form Designer changes) - Field validations after import
Specific Setup:
  • Have an existing modeled envelope [TestEnvelope] that contains a form [TestForm] that includes a "Date" type field and any other desired field types
  • Using "Form Designer", edit [TestForm] and navigate to any field [TestField] on the form.
  • Edit the field label name of the field to include a '~' tilde character within the field label name. For example a field label name of "Te~stField"
Steps
  1. Open form [TestForm]
  2. Navigate to [TestField]
  3. Validate the form designer change to add a '~' tilde character within the field label name, is displayed as expected
  4. Navigate to the "Date" field
  5. Enter a desired date
  6. Click the 'T' and 'Y' buttons of date field
  7. Validate the date field reflects the expected value
  8. Click the 'Calendar' icon and select a date
  9. Validate the date field reflects the expected value
  10. Populate any other fields on the form
  11. Submit the form
  12. Validate the form files successfully
  13. Open form "Envelope Export"
  14. Select [TestEnvelope] for export
  15. Select "Yes" in prompt "Include Form Design Changes"
  16. Click to [Export] the file and save the file to a folder location
  17. Validate the export is successful
  18. Close the form
  19. Open form "Envelope Import"
  20. Click [Select Envelope For Import]
  21. Navigate the location of export file for [TestEnvelope] saved in step 2
  22. Select the file
  23. Select "Yes" in prompt "Include Form Design Changes"
  24. In the "Overwrite Existing Envelope or Create New Envelope" field, select "Create New"
  25. At the dialog prompt, "This envelope already exists within this system. Are you sure that you would like to create a new envelope?"
  26. Click [Yes]
  27. Click [Begin Import Scan]
  28. In the "Import Scan Results" field, validate there are the following warnings:
  29. Warning: Envelope The import file contains an envelope name which is already in use. The import process will assign a new envelope name based upon the existing name and a counter.
  30. Warning: Table: The import file contains a table name which is already in use. The import process will assign a new table name based upon the existing name and a counter.
  31. Click [Begin Import]
  32. Validate the following "Import" warning is received
  33. Import: The envelope to be imported is currently defined and can be imported as an 'Overwrite' with no errors. Selecting 'Create New' may cause conflicts in future envelope imports. Are you sure that you want to 'Create New'?
  34. Click [Yes]
  35. Validate import is completed successfully
  36. Close the form
  37. Open "Form Definition" and select the new import version of [TestForm]. Note: the new copy form will have the same name as the original, but the (ID#) of the form next to the form name will be a higher number
  38. Rename the form to a desired name [TestFormNew] and submit the form
  39. Open the new form [TestFormNew]
  40. Navigate to [TestField]
  41. Validate the form designer change, to add a '~' tilde character within the field label name, is displayed as expected
  42. Navigate to the "Date" field
  43. Enter a desired date
  44. Click the 'T' and 'Y' buttons of date field
  45. Validate the date reflects the expected value
  46. Click the 'Calendar' icon and select a date
  47. Validate the date field reflects the expected value
  48. Populate any other desired fields on the form
  49. Submit the form
  50. Validate the form files successfully
  51. Repeat step 5 for the original version of the form [TestForm]
  52. Validate results are as expected
Topics
• Envelope Import • NX
AV-84935 Summary | Details
Form Designer - Date field components
Internal Test Only
Topics
n/a
AV-85286 Summary | Details
Form Designer- ScriptLink settings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
Scenario 1: Form Designer (Export/Import) - Validate "ScriptLink" configuration" settings after form designer changes
Specific Setup:
  • Have a form [TestForm] with one or more fields on the form
  • Have a "ScriptLink" script configured [ScriptTest] that exists in the system
  • In "Form Designer", the "WSDL" for [ScriptTest] has already been imported for form [TestForm]
  • The logged in user must have access to 'Form Designer'.
Steps
  1. Access 'Form Designer'.
  2. Select "TestForm" from the 'Forms' field.
  3. Select a section [TestSection] from the 'Sections' field.
  4. Click [Show Section].
  5. Navigate to the "ScriptLink" settings section
  6. Click the "Post-File" field in the "Available Scripts" column
  7. Select [TestScript]
  8. Populate the "Script Parameter" field with a parameter [TestParam]
  9. Return to the form layout section
  10. Click to select any field [TestField]
  11. On the left side panel in the "General" settings section
  12. Click the "ScriptLink" setting link
  13. From the "Available Scripts" field, select [TestScript]
  14. Populate the "Script Parameter" field with a parameter [TestParam]
  15. Click [Apply]
  16. Click [Save]
  17. Submit the form
  18. Validate the form submits successfully
  19. Return to "Form Designer"
  20. Navigate to the form layout and make any desired form designer change to the layout. For this example, [TestField] is moved to a new location on the layout
  21. Click [Save]
  22. Submit the form
  23. Return to "Form Designer"
  24. Select "TestForm"
  25. Select [TestSection]
  26. From the "Export All Tabs or Select Tab" field?
  27. Select "Selected Section"
  28. Click "Export Form Designer Copy"
  29. Navigate to a folder location and save the file
  30. Close the form
  31. Re-open "Form Designer"
  32. Select "TestForm"
  33. Select [TestSection]
  34. Click "Import Form Designer Copy"
  35. Navigate the folder location of the export file saved in step 3, and select the file
  36. Submit the form
  37. Return to "Form Designer"
  38. Select "TestForm"
  39. Select [TestSection]
  40. Click [Show Section].
  41. Navigate to the "ScriptLink" settings section
  42. Click the "Post-File" field in the "Available Scripts" column
  43. Validate script [TestScript] is selected as expected
  44. Validate the "Script Parameter" field is populated with parameter [TestParam] as expected
  45. Return to the form layout section
  46. Validate the form designer change made to [TestField] in step 2 is displayed as expected
  47. Select [TestFeild]
  48. Click to select the "General" settings section on the left side panel
  49. Click the "ScriptLink" setting link
  50. From the "Available Scripts" field, validate script [TestScript] is selected as expected
  51. Validate the "Script Parameter" field is populated with parameter [TestParam] as expected
  52. Re-submit the form
  53. Return to "Form Designer"
  54. Repeat step 5c and 5d
  55. Validate all "ScriptLink" configuration setting are still present, as expected
Topics
• NX • Scriptlink
AV-85769 Summary | Details
Console Widgets - SQL query override
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
Scenario 1: Validate data displayed in the "Console Widget Viewer" widget
Specific Setup:
  • Have registry setting "Enable Console Widgets/Views" is set to "Y"
  • Have access to the 'Admission' form
  • Have an episodic modeled form [TestForm] created
  • In form "Console Widget Configuration":
  • Create a console widget for the "Admission" form [AdminWidget] with "SQL Query override" field populated with a query that does not include an episode in the link. For example: "SELECT <LINK:PATIENT510:PATID:EPN_uniqueid>PATID,EPN_uniqueid FROM SYSTEM.episode_history WHERE FACILITY=?FACILITY AND PATID=?PATID"
  • Create a console widget for the "Modeled" form [ModeledWidget] with "SQL Query override" field populated with a query that does not include an episode in the link. For example: "SELECT <LINK:USER19:PATID:CUSTHAAS_UID>PATID,CUSTHAAS_UID FROM SYSTEM.testtable1 WHERE FACILITY=?FACILITY AND PATID=?PATID" Note: (replace the row ID and option ID values as applicable)
  • Add the two widgets and the 'Console Widget Viewer' widget to the logged in users home view
  • Have a client [TestClient] admitted in two episodes
  • In each episode, have a row filed for that client in the modeled form
Steps
  1. At the homeview, select [TestClient]
  2. Select 'All Episodes' from the episode dropdown field.
  3. Navigate to the [AdminWidget]
  4. Validate a row for both admission episodes are present in the widget
  5. Click the "View" button for "Episode 1" row
  6. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  7. Click the "View" button for "Episode 2" row
  8. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  9. Select "Episode 1" from the episode dropdown field.
  10. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
  11. Select "Episode 2" from the episode dropdown field.
  12. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
  13. Select 'All Episodes' from the episode dropdown field.
  14. Navigate to the [ModeledWidget]
  15. Validate a row for both modeled form episodes are present in the widget
  16. Click the "View" button for "Episode 1" row
  17. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  18. Click the "View" button for "Episode 2" row
  19. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  20. Select "Episode 1" from the episode dropdown field.
  21. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
  22. Select "Episode 2" from the episode dropdown field.
  23. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
Topics
• Console Widget