State Form Button Mapping
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- State Form Button Mapping
Scenario 1: Validate the use of "State Form Button" mapping functionality in a Modeled Form
Specific Setup:
- Have a client [ClientA], that's currently admitted in two episodes. [Episode1] and [Episode2]
- Have a state form definition file [StateFormDefA] created that extracts the "Episode" number from the "SYSTEM.admission_data" table
- Have modeled form [FormA] that includes a "ScriptLink" type button [PopulateA] defined, as well as an "Episode" number field on the form
- In form "State Form Button Mapping", have the following prompts populated with the form submitted
- [PopButtonA] selected in the "Button Field"
- [StateFormDefA] selected in the "State Form Definition" field
- "Episode Number" selected in the "Parameter Field 1" field
- "Netsmart" has configured the [PopulateA] button on [FormA] using "Programmer Override" logic so that when the button is clicked, it will run state form definition file [StateformDefA] to populate "Episode" number field on [FormA], with the current selected episode
Steps
- Open [FormA]
- Select the desired client [ClientA]
- Select [Episode1]
- Click the [PopulateA] button, set up on the form
- Validate the [Episode] field contains the expected selected episode, [Episode1]
- Click [Submit]
- Validate the form files successfully
- Return to [FormA]
- Select [Episode1]
- Select [ClientA]
- Validate the [Episode] field contains the expected selected episode, [Episode1]
- Close the form
- pen [FormA]
- Select the desired client [ClientA]
- Select [Episode2]
- Click the [PopulateA] button, set up on the form
- Validate the [Episode] field contains the expected selected episode, [Episode2]
- Click [Submit]
- Validate the form files successfully
- Return to [FormA]
- Select [Episode2]
- Select [ClientA]
- Validate the [Episode] field contains the expected selected episode, [Episode2]
- Close the form
|
Topics
• NX
• State Form Tools
|
State Form Tools - Populate functionality
Scenario 1: Validate the use of "State Form Button" mapping functionality in a Modeled Form w/Event Logic
Specific Setup:
- Have a modeled form [FormA], that includes the following field types: "Name" field [NameA] ;"Date" field [DOB] ; "Dictionary" field [FieldA], Dictionary field [FieldB] and "ScriptLink" button [PopulateA]
- [FormA] has event logic set on a field [FieldA] that will set [FieldB] to be required when specific value [Value1], is selected in [FieldA]
- Have a "State Form Definition" file [StateFormDefA] created that extracts the "Patient Name" and "Date of birth" from the "SYSTEM.patient_current_demographics" table
- Have the "State Form Button Mapping" form submitted with following values populated:
- [PopulateA] selected in the "Button Field"
- [StateFormDefA] is selected in the "State Form Definition" field
- [FieldA] is selected in the "Parameter Field1" field
- [FieldB] is selected in the "Parameter Field2" field
- "Netsmart" has configured the [PopulateA] button on [FormA] using "Programmer Override" logic to run state form definition file [StateformDefA] to then populate field values on [FormA] and also trigger any expected event logic
Steps
- Open [FormA]
- Select [ClientA]
- Click the [PopulateA] button, set up on the form
- Validate the [Name] field contains the expected name for [ClientA]
- Validate the [Date] field contains the date of birth for [ClientA]
- Validate [FieldA] is populated with [ValueA], the trigger value for the event logic
- Validate [FieldB] is set to be 'Required', as expected
- Deselect any values selected in the field
- Submit the form
- Validate a message indicating [FieldB] is not populated is displayed
- Select a value in [FieldB]
- Submit the form
- Validate the form files successfully
- Return to [FormA]
- Select [ClientA]
- Validate fields all are populated as expected
|
Topics
• NX
• State Form Tools
|
