Skip to main content

RADplus 2023 Update 90

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Monthly Release 2023.02.02

Product Update Description

Two issues are resolved: An issue where 'Menu Location' and 'Form Description' on 'Site Specific Section Modeling' may not enable on form entry. UNDEFINED GetDesc+10^GUILaunchForm *ind on returning ScriptLink calls which initiate a form launch, but do not have a user defined launching message.

Required Updates

None

Included Updates

2, 4, 6, 12, 14, 22, 25, 26, 29, 33, 35, 47, 49, 55, 56, 58, 59, 64, 71, 75, 80, 89

Details
NEW0 CHANGED0 FIXED2
Fixed (2)
Site Specific Section Modeling - form
An issue is resolved to ensure that the 'Menu Location' and 'Form Description' on 'Site Specific Section Modeling' are enabled initially when creating a new form and then disabled after the form is submitted KB0074468 v0.01
Topics
• NX • Site Specific Section Modeling
 
ScriptLink - form launch
An issue is resolved to ensure that "ScriptLink" scripts set to launch an additional form that do not contain a user defined form launch dialog, launch and display the default Avatar form launch dialog message, as expected
Topics
• NX • Scriptlink
 
Acceptance Tests
AV-90051 Summary | Details
Site Specific Section Modeling - form
Scenario 1: Site Specific Section Modeling Form - prompt and value validations
Specific Setup:
  • Have access to form "Site Specific Section Modeling"
Steps
  1. Open form "Site Specific Section Modeling"
  2. Select any form [TestFormA] from the "Site Specific Section" drop down list that has not already been configured, for example the "(Inpatient Progress Notes) Supplemental Information" form
  3. Click [OK] to edit the form.
  4. Validate the "Site Specific Section Description" field is enabled and pre-populated with the default description of "Supplemental Information", as expected
  5. Change the name of the field to a new desired value [ValueA]
  6. Validate the "Form Description" field is enabled and blank, as expected
  7. Populate the field to a desired value [ValueB]
  8. Validate the "Menu Location" field is enabled
  9. Click the drop down list and select a menu location
  10. Select the "Prompt Definition" section
  11. Click "Add New Item" and add any desired field [NewField1]
  12. Submit the form
  13. Validate the form files successfully
  14. Return to "Site Specific Section Modeling" and select [TestFormA]
  15. Select the "Prompt Definition" section
  16. In the "Prompt Definition" grid, validate [NewField1] is present, as expected
  17. Select the prompt and click [Delete Selected Item].
  18. Validate message "Are Your Sure?" is displayed.
  19. Click [OK].
  20. Validate the prompt is removed from the "Prompt Definition" grid.
  21. Click "Add New Item" and add any desired field [NewField2]
  22. Navigate to the "Initially Required" prompt and set it to "Yes"
  23. Navigate to prompt "Exclude from Data Collection Instrument" and set it to "Yes"
  24. Validate a message is displayed "Cannot exclude a required prompt", is displayed
  25. Click "OK"
  26. \Navigate to the "Initially Required" prompt and set it to "No"
  27. Navigate to prompt "Exclude from Data Collection Instrument" and set it to "Yes"
  28. Validate the selection is accepted
  29. Submit the form
  30. Validate the form files successfully
  31. Return to "Site Specific Section Modeling" and select [TestFormA]
  32. Validate the "Site Specific Section Description" field is still enabled and populated as expected
  33. Validate the "Form Description" field is populated as expected and is now disabled as the form, since the form has already been submitted.
  34. Validate the "Menu Location" field is populated as expected and also now disabled after form submission, as expected
  35. Navigate the "Prompt Definition" section
  36. Validate [NewField2] is present in the grid and the prompts populated in step 2 are populated as expected
  37. Validate [NewField1] that was deleted, is not present in the grid as expected
Topics
• NX • Site Specific Section Modeling
AV-91164 Summary | Details
ScriptLink - form launch
Scenario 1: "ScriptLink' - Launch additional form validations
Specific Setup:
  • Have two "ScriptLink" scripts configured to prompt the user with a message to launch an additional form [TestFormC]
  • [ScriptA] is 'not' configured with user defined message and will contain the default message to the user when the prompt is launched. For example "ScriptLink is attempting to launch the Avatar form "Update Client Data. Press OK to do this now"
  • [ScriptB] is configured with user defined message when the prompt is launched. For example "Launch Form "Update Client Data" ?
  • Have two forms for testing.
  • [TestFormA] is configured with [ScriptA]. For this example, it is configured to trigger when the [TestFormA] is launched
  • [TestFormB] is configured with [ScriptB]. For this example, it is configured to trigger when a value in [TesField] on the form
Steps
  1. Open [TestFormA]
  2. Select a desired client
  3. Click to add a new row
  4. Validate the user is prompted with the Avatar default message "ScriptLink is attempting to launch the Avatar form '[TestFormC]'. Press 'OK' to do this now"
  5. Click "No"
  6. Validate the user is returned to [TestFormA]
  7. Close the form
  8. Re-open [TestFormA]
  9. Select a desired client
  10. Click to add a new row
  11. Validate the user is prompted with the Avatar default message "ScriptLink is attempting to launch the Avatar form '[TestFormC]'. Press 'OK' to do this now"
  12. Click "OK"
  13. Validate [TestFormC] is launched, as expected
  14. Submit or close the form
  15. Open [TestFormB]
  16. Select a desired client
  17. Navigate to [TestField]
  18. Select a value in the field other than the value set to trigger the script
  19. Validate [TestFormC] is not launched, as expected
  20. Select the value in the field set to trigger the script
  21. Validate the form launch message is displayed
  22. Validate the message includes the user defined message configured in the script, as expected. For example "Launch form [TestFormC] ?
  23. Click "No"
  24. Validate the user is returned to [TestFormB]
  25. Select the value in the field set to trigger the script again
  26. Validate the form launch message is displayed
  27. Validate the message includes the user defined message configured in the script. For example "Launch form [TestFormC] ?"
  28. Click "Yes"
  29. Validate [TestFormC] is launched as expected
  30. Submit or close the form
Topics
• NX • Scriptlink