RADplus 2024 Update 68

Last updated
Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Update 126
RADplus 2024 Monthly Release 2024.01.02

Product Update Description

The error "[SYNTAX]ModeledHTMLLoad+80^GUIEventHTML" which may occur on the 'Form and Table Documentation' form when using 'Generate Form Map' is resolved.

Required Updates

None

Included Updates

None

Details

NEW0 CHANGED0 FIXED1

Fixed (1)

AV-96691 Details \| User Acceptance Tests Form and Table Documentation - 'Generate Form To Map' Ensure the ability to use the 'Generate Form To Map' functionality in the 'Form and Table Documentation' form for modeled forms containing event logic KB0076573 v0.01	Topics • Forms • Modeling

Acceptance Tests

AV-96691 Summary | Details

Form and Table Documentation - 'Generate Form To Map'

Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:

Form and Table Documentation (PM)

Scenario 1: "Form and Table Documentation" form (Modeled Forms) - Validate "Generate Form Map' report results

Specific Setup:

Have a "Modeled" form that contains a table column of Single response dictionary type and event logic defined on the form [FormA].
Event logic must be defined as: 'Type of Event' set to "Input Validation" and 'Compare With for Event' set to "Specific Value".
Have a "Modeled" form that does 'not' contain event logic defined on the form [FormB].
Make a note or all the fields on the form.
Have access to form "Form and Table Documentation".

Steps

Open 'Form and Table Documentation'.
Set 'Type of Documentation' to 'Form'.
Select "Individual" in the "Individual or All Forms" field.
Select [FormA] from the 'Form to be Documented' field. (Modeled form with event logic defined)
Navigate to the "Generate Form Map" button.
Validate form is generated without any error.
Validate the user is presented with a file explorer dialog [Note: In Avatar NX the file will automatically be created and saved in the windows "Downloads" directory on the server].
Validate the (.htm) type file name field is populated in the file name field.
Validate the file name includes the associated internal "FormID' for [FormA], followed by its form "Name". For example: "NetsmartFormMap_USER9_Modeled Form with Event logic".
Select a folder location to save the file and click [Save].
Navigate to the location of the (.htm) file.
Click to open the file.
Validate the title of the report reflects the name of [FormA] and its associated internal "FormID".
Validate each "Section" name is displayed on the form as expected with each field contained in that section listed beneath it.
Validate the field names contain both the name and its associated field number in brackets, for example "Date of Entry (777.77)".
Locate a field on the form that contains event logic defined.
Validate the event logic noted in the setup is displayed as expected. For example:
Date of Entry(777.77)
Type of Event: Input Validation
Compare with For Event: Specific Value
Specific Value : Dictionary Value configured
Relationship To Comparison Value to Trigger Event: Equal To
Type of Validation Message: Message with [OK] and [Cancel] Buttons
Validation Message: Test Validation Message
Close the page
Select [FormB] from the 'Form to be Documented' field. (Modeled form with 'no' event logic defined)
Repeat steps 1a through 1e.
Validate results are as expected.
Close the form.

Topics

• Forms • Modeling