State Form Populate Functionality

System Requirements and Initial Setup

RADplus 2019 Update 8 

RADplus 2019 Update 78

RADplus 2019 Update 96

RADplus 2020 Update 31

A Netsmart Representative will import the necessary Envelopes, State Form Definitions into applicable environments

Populate Product Overview

Populate functionality allows Providers to populate fields in modeled forms by combining the uses of ScriptLink buttons, Programmer Form Overrides, and State Form tools. The majority of initial setup and configuration will be handled and documented on a per-solution basis by a Netsmart team member. Once all necessary configuration is in place, Providers will have the opportunity to configure where and how their Populate buttons pull data from desired areas of the myAvatar system using State Form Definitions

State Forms

• Launch the form 'State Form Definition'
• Choose to the appropriate 'State Form'
• Navigate to the 'Record Definition' of the form and select Edit record
  • Select 'Define Record Tables' button to add appropriate tables to the Definition
  • Select 'Define Record Data Elements' button to add appropriate fields from alias table

State Form Field Translations

Dictionaries will often need to be translated from the myAvatar dictionary code to the state required dictionary code so that field populate correctly in modeled form

• Create translation document with current myAvatar codes/values, Compass codes/values, and translations needed for each myAvatar field
• Launch the ‘State Form Field Translation’ form
• Choose the appropriate ‘State Form’
• Choose the appropriate ‘Record’
• Choose the appropriate ‘Table’
• Choose the appropriate ‘Table Property’
• Choose the ‘Single Translation’ via the ‘Action’ field
• Input the current myAvatar Dictionary Code via the ‘Dictionary Code’ field
• Input the state Dictionary Code via the ‘State Form Dictionary Code’ field

Troubleshooting

If the fields are not populating correctly you may troubleshoot the information by logging into the ‘State Form File Generation’ form. When you select the Populate Button on any form the process will go through the mapping set up on the ‘State Form Definition’ then go out to the ‘State Form File Generation’ form. Once it goes through the ‘State Form File Generation’ form the information that is mapped on the ‘State Form Definition’ populates on the form. If you select the ‘Populate Button’ on the form and nothing happens the first place you should check is the ‘State Form File Generation’ form.

State Form File Generation Process

1.     Launch ‘State Form File Generation’ form

2.     Select ‘Dump File’ in the ‘Field Generation Options’ section

3.     Click ‘Process’

4.     Does the dump file contain the populate information?

Using Populate Parameters

Data elements that exist in Modeled from which the button being mapped resides can be passed to the State Form Definition using the Parameter Fields in State Form Button Mapping:

Note: Parameters are configured and controlled by a Netsmart team member. Consult with Netsmart team lead on information regarding parameters specific to your populate configurations

Use the following Syntax in the State Form Definition Table Grid for Each Parameter when applicable:

• Parameter Field 1: {?Param1}
• Parameter Field 2: {?Param2}
• Parameter Field 3: {?Param3}

Populating to or from Multi-Select Fields

Additional setup is required for populating to or from multi-select dictionaries. In both cases, a sql view will need to be added to the system using ‘SQL View Definition’. After the view is created, user will need to have table access to view in User Definition/User Role Definition. Once permissions have been updated, the view can be used in the Table Elements grid in the State Form Populate Definition

Multi Select to Single Select

The multi-select field will need to be broken into individual columns to populate the single-select fields on the form. The example view below would be used to populate 4 single-select fields. You may need to pull additional fields other than PATID to join the table in the definition.

Once the view is in place, you can add translations to the columns in the view just as you would a normal table. Please see Translation section of this guide

Single Select to Multi Select

The single select field(s) will need to be concatenated into one string delimited by &. The example view below would be used to populate one multi-select field from 3 single-select fields. The view can be updated accordingly depending on how many single-select fields exist. 

Once the view is in place, you can add translations to the columns in the view just as you would a normal table. Please see Translation section of this guide

Additional Populate Use Cases

Range to Single Select

An integer field will need to be broken out by ranges to populate a single select field with the appropriate range/code. The example view below would be used to populate one integer field to one single select field.

Once the view is in place, you can add translations to the columns in the view just as you would a normal table. Please see Translation section of this guide

The example state reporting tool If Then Logic below would be used to populate one integer field to one single select field without creating a view.