Skip to main content

RADplus 2022 Update 26

Product Requirements / Recommendations

RADplus required

Product Update Form Description

The following modifications are made: 1) The State Form Tools are modified to allow formats to be applied to fields within the Default Error Message. 2) An issue is resolved where an error is received when running a populate button without the State Forms module installed.

Included Updates

None

Required Updates

None

Details

NEW1 CHANGED0 FIXED1
New (1)
State Form Definition Form
The "Define Record Data Elements Grid" of the "State Form Definition" form is modified to allow formatting options to be applied to fields referenced in "Default Error Message" field when used in conjunction with the "Forced Error Message" field
Value Added: Provides enhanced formatting functionality when displaying messages to users
Topics
• NX • State Form Tools
 
Fixed (1)
State Form Tools - State Form Button Mapping
An issue is resolved to ensure that the use of the "State Form Tools" state form button mapping functionality in modeled forms, works in systems with the "Avatar State Forms" module installed and also in systems without the module installed
Topics
• NX • State Form Tools
 
Acceptance Tests

AV-71635 Summary | Details
State Form Tools - State Form Button Mapping
Scenario 1: Modeled Form - Validate the use of "State Form Button" mapping functionality
Specific Setup:
  • Have modeled form [FormA] that includes a "ScriptLink" type button [PopulateA] defined, as well as a "Name" type field [Patient Name] and "Date" type field [Date of Birth], on the form
  • Have a state form definition file [StateFormDefA] created that extracts the "Patient Name" and "Date of birth" from the "SYSTEM.patient_current_demographics" table
  • 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
  • "Patient Name" selected in the "Parameter Field 1" field
  • "Date of Birth" selected in the "Parameter Field 2" field
  • Have "Netsmart" configure the [PopulateA] button on [FormA] using "Programmer Override" logic in order execute the [StateFormDefA] file so that it populates [FieldA] and [FieldB] on modeled form, when a user clicks the [PopulateA] button
Steps
  1. Open [FormA]
  2. Select the desired client [ClientA]
  3. Click the [PopulateA] button, set up on the form
  4. Validate the [Patient Name] field contains the expected name for [ClientA]
  5. Validate the [Date of Birth] field contains the date of birth for [ClientA]
  6. Click [Submit]
  7. Validate the form files successfully
  8. Return to [FormA]
  9. Select [ClientA]
  10. Validate the [Patient Name] field contains the expected name for [ClientA]
  11. Validate the [Date of Birth] field contains the date of birth for [ClientA]

Topics
• NX • State Form Tools
AV-79111 Summary | Details
State Form Definition Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: 'State Form Definition' form - "Define Record Data Elements" grid validations
Specific Setup:
  • Have a state form definition file created in form "State Form Definition", [DefinitionA]. For this example, a definition that selects the "PATID" and "Patient Name" for all clients on the system from the SYSTEM.patient_current_demographics table is used
  • Have two test clients:
  • [ClientA] with a PATID of "1"
  • [ClientB] with a "PATID" of "2" and also has a "Date of Birth" filed in their client record
Steps
  1. Open form "State Form Definition"
  2. Select [DefinitionA]
  3. Navigate to the "Record Definition" tab
  4. Select the existing record in the "Select Record" field
  5. Click the "Define Record Data Elements" to open the data elements grid
  6. In the grid, select the row containing "PATID",
  7. Navigate to the "Force Error Condition" column
  8. Enter "p.PATID = 1" in the input field
  9. Validate the value is accepted
  10. Navigate to 'Default Error Message' column
  11. Enter a default text message that includes the clients name in the message but formatted to use the "NAME1" format variable, to just display only the clients last name. For example enter, "Client {p.patient_name:NAME1} is not valid"
  12. Validate the value is accepted
  13. Save the grid
  14. File the record and file the form
  15. Open form "State Form File Generation"
  16. Select [DefinitionA]
  17. Select "Compile" in the "File Generation Options" field
  18. Click [Process]
  19. Validate a message is displayed indicating the compile is complete but it contains errors
  20. Click [OK]
  21. Click the [Process] button to run the error report
  22. Validate the warning message is present and contains the last name PATID "1" as expected. For example, "Client SMITH is not valid"
  23. Close the report and close the form
  24. Open form "State Form Definition"
  25. Select [DefinitionA]
  26. Navigate to the "Record Definition" tab
  27. Select the existing record in the "Select Record" field
  28. Click "Define Record Data Elements" to open the data elements grid
  29. In the grid, select the row containing "PATID",
  30. Navigate to the "Force Error Condition" column
  31. Enter "p.PATID = "2" in the input field
  32. Validate the value is accepted
  33. Navigate to 'Default Error Message' column
  34. Enter a default text message to include the display of the clients date of birth using the "D3" date format variable, which will display the date in the "YYYY-MM-DD" format. For example enter, "Client {p.patient_name:NAME1} is not valid. DOB {p.date_of_birth:D3}"
  35. Validate the value is accepted
  36. Save the grid
  37. File the record and file the form
  38. Open form "State Form File Generation"
  39. Select [DefinitionA]
  40. Select "Compile" in the "File Generation Options" field
  41. Click [Process]
  42. Validate a message is displayed indicating the compile is complete but it contains errors
  43. Click [OK]
  44. Click the [Process] button to run the error report
  45. Validate a warning message is displayed containing the last name and the date of birth for PATID "2" as expected, for example: "Client SMITH is not valid. DOB 1996-07-25"
Topics
• NX • State Form Tools

 

  • Was this article helpful?