Skip to main content

RADplus 2022 Update 59

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Product Update Form Description

An issue is resolved in the 'Form Designer' form where the field 'Other System Codes to File Form Designer Changes to' will sometimes display invalid system codes. The following enhancements are added: the 'Form Designer' form now allows any user to select and modify the 'Table Definition', 'Form Definition', 'Envelope Definition', 'Report Definition', and 'Site Specific Section Modeling' forms; the product design of the 'Form Definition' form is updated with new and expanded fields.

Included Updates

None

Required Updates

None

Details
NEW1 CHANGED0 FIXED1
New (1)
Form Designer and Form Definition (Form's) - Product design and field changes
The 'Form Designer' form now allows a user to select and modify the 'Table Definition', 'Form Definition', 'Envelope Definition', 'Report Definition', and 'Site Specific Section Modeling' forms.
In addition, the Netsmart product design layout of a form used when reverting changes to the "Netsmart Produced Changes" via "Form Designer", has been updated in the "Form Definition" form. The change includes expanding the size of "Multi-Select" dictionary field boxes in the "Event Definition" section of the form for increased visibility of dictionary values selections within each field
Value Added: Provides enhanced functionality and visibility in the "Form Definition" and "Form Designer" forms for user's
Topics
• Assign MR# • Audit Log • Auto Save • Azure Authentication • Form Designer • NX
 
Fixed (1)
Form Designer
An issue is resolved to ensure prompt 'Other System Codes to File Form Designer Changes to' in the 'Form Designer' form, only displays valid system codes.
Topics
• Form Designer • NX
 
Acceptance Tests
AV-79201 Summary | Details
Form Designer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
Scenario 1: Form Designer - Form field validations
Specific Setup:
  • Have a system with multiple root system codes defined.
  • [UserA] has access to the "Form Designer" form
  • [UserA] access to the following forms:
  • 'Table Definition', 'Form Definition', 'Envelope Definition', 'Report Definition', 'Site Specific Section Modeling' and any other desired forms
  • [UserA] is logged any desired root system code
Steps
  1. Open form "Form Designer"
  2. From the "Forms" list, select any desired form
  3. Select any section from the "Sections" tab
  4. Validate field "Other System Codes to File Form Designer Changes to" contains all other valid root systems codes, displayed as expected
  5. Click back to the "Forms" list and validate the following forms are present for selection in the drop down list:
  6. 'Table Definition'
  7. 'Form Definition'
  8. 'Envelope Definition'
  9. 'Report Definition'
  10. 'Site Specific Section Modeling'
  11. Select each form in step c
  12. Click [Show Section]
  13. Select each section listed for the form for edit:
  14. Validate the form layout is displayed as expected
  15. Click [Save]
  16. Validate the section saved successfully
  17. Click [Submit]
  18. Validate the "Form Definition" form is saved successfully
Topics
• Form Designer • NX
AV-80229 Summary | Details
Form Designer and Form Definition (Form's) - Product design and field changes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Definition (CWS)
  • Form Designer (CWS)
Scenario 1: Form Definition (Form) - Validate "Netsmart Produced " product design field and format changes
Specific Setup:
  • Have access to the "Form Definition" form in the "PM" namespace and any child namespace
  • Have access to the "Form Designer" form in the "PM" namespace and any child namespace
  • Have access to any modeled form in each namespace [FormA]
  • In each namespace, open "Form Definition" and select [FormA], make a note the following:
  • In "Event Definition" section, note the size of all the "Multi-Select" dictionary fields, for example, the "Enable", "Disable", "Required", "Not Required", "Hide" and "Unhide" fields
Steps
  1. Open form "Form Designer"
  2. From the "Forms" drop down list, select "Form Definition"
  3. Select the "Event Def." section from the "Sections" field
  4. Navigate to the "Select Copy to Revert to" field.
  5. Select "Netsmart Produced Changes". (Please Note: This selection will revert the section to the latest Netsmart product design layout for the section. Note: In the event the user wants to revert to the previous layout after submission, the user can return and select the previous layout from the "Select Copy to Revert to" field drop down list and restore it back)
  6. Click [Submit]
  7. Validate the form files successfully
  8. Navigate back to the "Form Definition"
  9. Select [FormA]
  10. Navigate to the "Object Definition" and select a field to edit
  11. Click the "Event Def" section on the left side
  12. Scroll down and observe the size of all the "Multi-Select" dictionary fields, for example, the "Enable", "Disable", "Required", "Not Required", "Lock", "Unlock" and "Fields for Summation" fields
  13. Validate the size of the box containing the dictionary values of the fields noted in the set up has increased and more dictionary values are now visible, if applicable. (Note: the increase is approximately twice the original size)
  14. Close the form
  15. Repeat steps 1 and 2 in any child namespaces
  16. Validate results are as expected
Topics
• Assign MR# • Audit Log • Auto Save • Azure Authentication • Form Designer • NX