Fields Element
The following elements allow for the configuration of fields. Fields dictate the entry information required for screens and activity processing.
| Element | Attribute | Parent Element | Description | Element/Attribute Values |
|---|---|---|---|---|
| <Fields> |
|
|
The root element for the <Fields> structure. |
|
| <Field> |
|
<Fields> |
Required, Repeatable: This element is a structure that defines a single field. The element structure is repeated to define multiple fields. |
|
| <Name> |
|
<Field> |
Required: This element provides the exact name of an entity database column or a dynamic field associated to an OIPA entity or activity. It can also present data returned from an associated SQL query or an associated Math section. |
|
| <Display> |
|
<Field> |
Required: This element provides the field's label. All labels can be translated to languages or renamed for a custom label. |
|
| <DataType> |
|
<Field> |
Required: This element classifies the field to one of the system's supported types of data. A specific data type gives a field a general definition of the potential appropriate values and the operations that can be performed on those values. |
|
|
|
MASK | <DataType> |
Optional: This attribute provides the name of a mask. The system chooses a specific definition by the mask name and the user's security group. This attribute is applicable only for "Text" data types. Field data that is masked is not persisted with formatting characters. |
|
|
|
CALENDAR | <DataType> |
Optional: This attribute provides the name of an industry standard calendar type. This influences the format of the entered or presented data value. The attribute is applicable only for "Date" data types. |
|
|
|
FORMAT | <DataType> |
Optional: This attribute provides the name of a date format defined in the AsTranslation table. The attribute is applicable only for "Date" data types. |
|
| <Group> |
|
<Field> |
Optional: This element provides a simplified name of the table that is the source of the data presented in the field. This is used where the source data may come from one of multiple tables (i.e., criteria for search screen). |
|
|
|
ROLECODE | <Group> |
Optional: This attribute identifies the Role whose field will be presented by the containing <Field>. |
|
| <Currency> |
|
<Field> |
Optional: This element provides a comma delimited list of currency codes. This list is presented in OIPA as a combo box. Selection associates the decimal value to the selected currency code. The element is applicable to fields with a data type of Money, otherwise it is ignored. |
|
| <DefaultCurrency> |
|
<Field> |
Optional: This element defines the initial currency selection from the combo box presented by the <Currency> element or provides the single currency code to associate to the field's value when the <Currency> element is not configured. This element is ignored in the Inquiry Screen's output field section. |
|
| <DefaultValue> |
|
<Field> |
Optional: This element provides the field's initial value. |
|
| <Calculated> |
|
<Field> |
Optional: This element provides a means to "calculate" the initial value of the field. The element's value provides different ways to calculate the field's default value. The element's value differs between the types provided by the TYPE attribute. |
|
|
|
TYPE | <Calculated> |
Required: The attribute describes the value that is configured in the parent element. |
|
|
|
METHOD | <Calculated> |
Optional: The element adds additional conditions to process the parent <Calculated> element. |
|
| <Disabled> |
|
<Field> |
Optional: The element controls the ability to access the field for data entry. |
|
| <Hidden> |
|
<Field> |
Optional: The element controls visibility of the field on the screen. |
|
| <Expanded> |
|
<Field> |
Optional: The element controls the width of the field. Normally the field's width is limited to the width of a single field column on the page. When a field is expanded, the field's width is expanded across all field columns on the page. If the field's natural presentation is in the left column, the field is expanded to all field columns. If the field's natural presentation is not in the left column, the field moves down a row and expands across all field columns. The only data types that can be expanded are Combo, Radio and Text. |
|
| <Required> |
|
<Field> |
Optional: The element indicates where a value is required to be entered. A required field cannot be left blank when the screen is submitted for persistence. There is exceptional information to note:
|
|
| <Final> |
|
<Field> |
Optional: This element will indicate when the field cannot be overridden during inheritance and is only applicable to screen rules that can be inherited. Those rules are PlanScreen and SegmentName. |
|
| <Query> |
|
<Field> |
Optional: This element provides the options that populate a combo box either through a SQL query or static list of <Option> elements. The element applies to Combo and Radio data type fields only. If configuration does not provide this element, a screen <Event> and associated <Action> must ASSIGN option values with value\text pairs. |
|
|
|
TYPE | <Query> |
Required: This attribute defines the method to obtain the options that populate the combo box. |
|
| <Options> |
|
<Query> |
Optional: This element provides a structure defining the options available to a Combo and Radio data type. This element is required when the <Query> element's type is FIXED. |
|
| <Option> |
|
<Options> |
Required, Repeatable: This element defines a single option. An option is always a key and value pair. Repeating the element allows definition of multiple key/value pairs. |
|
| <OptionValue> |
|
<Option> |
Required: This element provides the value for the key part of the key/value pair. Often this is a code value from the AsCode table. When this option is selected, this is also the field's actual value. |
|
| <OptionText> |
|
<Option> |
Required: This element provides a descriptive label for the associated key. A user actually sees this on the UI. |
|
| <Encrypt> |
|
<Field> |
Optional: This element identifies that the field's text value will be encrypted as it is persisted to the database. If the field applies a MASK, the MASK is applied first followed by encrypting the data. MASK formatting characters are not persisted in the database and not part of the encrypted data. This element may co-exist on the same field with the <Decrypt> element and is recommended. <Decrypt> instructs the system about data retrieval while <Encrypt> impacts data persistence. This element applies only to Activities defined by Transaction configuration. |
|
|
|
ERASE | <Encrypt> |
Optional: This attribute identifies the actions the system takes on this field's data when the Activity processes successfully ("Active" status) or when the activity is deleted while it is pending ("Pending Shadow" status). This attribute applies to Activities regardless of how they are created ( UI, Data Intake, Spawn, AsFile), regardless of the process that made it active and regardless of the process that shadowed the activity (UI, Data Intake, ShadowPendingActivities attached business rule). |
|
| <Decrypt> |
|
<Field> |
Optional: This attribute indicates that the field's encrypted text value will be decrypted as the value is retrieved from the database with or without a SQL query. The data is presented in its raw decrypted value. A MASK on the field applies formatting characters after decryption. This element may co-exist on the same field with the <Encrypt> element and is recommended. <Encrypt> instructs the system on persisting data while <Decrypt> instructs data retrieval. This element applies only to Activities defined by Transaction configuration. |
|
|
|
ERASE | <Decrypt> |
Optional: This attribute identifies the actions the system takes on this field's data when the Activity processes successfully ("Active" status) or when the activity is deleted while it is pending ("Pending Shadow" status). This attribute applies to Activities regardless of how they are created ( UI, Data Intake, Spawn, AsFile), regardless of the process that made it active and regardless of the process that shadowed the activity (UI, Data Intake, ShadowPendingActivities attached business rule). |
|
| <Parts> |
|
<Field> |
Optional: This element provides a structure to define concatenation of field values, math variable values, literals and sequence numbers. This is applicable for fields where <DataType> is "Identifier". See Parts page under Common Elements topic. |
|
| <ClearOnRecycle> |
|
<Field> |
Optional: The element instructs the system to clear the field's value during the activity's presentation when it is manually recycled by a user. This element can only be applied to a transaction's fields. |
|
| <ToolTip> |
|
<Field> |
Optional: This element provides an informational message when a user hovers over a field name or it's label. |
|
XML Schema
<Fields>
<Field>
<Name>[field name | variable | column name]</Name>
<Display>[literal]</Display>
<DataType>[Blank | Check | Client | Decimal | Label | Line | LinkExternal | Message | Percent | TextArea | Title]</DataType>
<Group ROLECODE="[code]">[table name]</Group>
<DefaultValue>[literal]</DefaultValue>
<Disabled>[No | Yes | ReadOnly]</Disabled>
<Hidden>[No | Yes]</Hidden>
<Required>[No | Yes]</Required>
<Final>[No | Yes]</Final>
<ToolTip>[message]</ToolTip>
</Field>
<Field>
...
<DataType CALENDAR="[Gregorian | JP | JP_IMP]" FORMAT="[literal]">Date</DataType>
<DefaultValue>SYSTEMDATE</DefaultValue>
<Calculated TYPE="[SQL | REPLACE | FUNCTION]" METHOD="[FORCE | IFEMPTY]">[sql statement | SystemDate | function call]</Calculated>
...
</Field>
<Field>
...
<DataType>Money</DataType>
<Currency>[list]</Currency>
<DefaultCurrency>[code]</DefaultCurrency>
...
</Field>
<Field>
...
<DataType MASK="[name]">Text</DataType>
<Expanded>[No | Yes]</Expanded>
...
</Field>
<Field>
...
<DataType>[Combo | Radio]</DataType>
<Expanded>[No | Yes]</Expanded>
<Query TYPE="SQL">[sql statement]</Query>
...
</Field>
<Field>
...
<DataType>[Combo | Radio]</DataType>
<Query>
<Options>
<Option>
<OptionValue>[code | literal]</OptionValue>
<OptionText>[literal]</OptionText>
</Option>
<Option>...</Option>
</Options>
</Query>
...
</Field>
<Field>
...
<DataType>Identifier</DataType>
<Parts>...</Parts>
...
</Field>
<Field>
...
<Calculated TYPE="SQL" METHOD="[FORCE | IFEMPTY]">[sql statement]</Calculated>
...
</Field>
<Field>
...
<Calculated TYPE="MESSAGE" METHOD="[FORCE | IFEMPTY]">[message]</Calculated>
...
</Field>
<Field>
...
<Calculated TYPE="REPLACE" METHOD="[FORCE | IFEMPTY]">[field name | literal]</Calculated>
...
</Field>
<Field>
...
<Calculated TYPE="FUNCTION" METHOD="[FORCE | IFEMPTY]">[function call]</Calculated>
...
</Field>
<Field>...</Field>
</Fields>
XML Schema - Transaction Feild
<Transaction>
...
<Fields>
<Field>
...
<DataType MASK="[name]">Text</DataType>
<Encrypt ERASE="[No | Yes]">[No | Yes]</Encrypt>
<Decrypt ERASE="[No | Yes]">[No | Yes]</Decrypt>
...
</Field>
<Field>
...
<ClearOnRecycle>[No | Yes]</ClearOnRecycle>
...
</Field>
<Field>...</Field>
</Fields>
...
</Transaction>
XML Example
General Example
<Fields>
<Field>
<Name>TaxID</Name>
<Display>Tax ID</Display>
<DataType MASK="SSN">Text</DataType>
<Disabled>No</Disabled>
<Hidden>No</Hidden>
</Field>
<Field>
<Name>QualNonQual</Name>
<Display>Qual or Non-Qual</Display>
<DataType>Text</DataType>
<ToolTip>Indicates a Qualified or non-Qualified Policy with 'Qual' or 'NonQual'</ToolTip>
</Field>
</Fields>
Line DataType Example
<Field>
<Name>Line1</Name
<Display>Line</Display>
<DataType>Line</DataType>
</Field>
Radio and Combo DataType Population Examples
<Fields>
<Field>
<Name>AccountType</Name>
<Display>Account Type</Display>
<DataType>Radio</DataType>
<Query TYPE="FIXED">
<Options>
<Option>
<OptionValue>C</OptionValue>
<OptionText>Checking</OptionText>
</Option>
<Option>
<OptionValue>S</OptionValue>
<OptionText>Savings</OptionText>
</Option>
</Options>
</Query>
</Field>
<Field>
<Name>BankStateLocation</Name>
<Display>Bank State</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT CodeValue, ShortDescription FROM AsCode UNION SELECT '$$$Blank$$$', ' ' ORDER BY ShortDescription</Query>
</Field>
</Fields>
Calculated Example
<Fields>
<Field>
<Name>Prefix</Name>
<Display>Prefix</Display>
<DataType>Text</DataType>
<Calculated TYPE="SQL">SELECT CASE WHEN '[PolicyStatus]' = '08' THEN 'B' ELSE 'R' END</Calculated>
</Field>
</Fields>
Currency Example
<Fields>
<Field>
<Name>AnnualPremium</Name>
<Display>Annual Premium</Display>
<DataType>Money</DataType>
<Disabled>Yes</Disabled>
<DefaultValue>0</DefaultValue>
<Currency>KRW,THB,INR,USD</Currency>
<DefaultCurrency>USD</DefaultCurrency>
</Field>
</Fields>
Parts Examples
<Fields>
<Field>
<Name>ClientID</Name>
<Display>Client Name ID</Display>
<DataType>Identifier</DataType>
<Parts>
<Part TYPE="SEQUENCE" FORMAT="0000000000">ClientID</Part>
</Parts>
</Field>
<Field>
<Name>ActivityWarrantNumber</Name>
<Display>Activity Warrant Number</Display>
<DataType>Identifier</DataType>
<Parts>
<Part TYPE="FIELD" LEFT="1">Prefix</Part>
<Part TYPE="SEQUENCE" FORMAT="0000000">AsActivity_RBWarrantNumber</Part>
</Parts>
</Field>
</Fields>
Activity Encrypt/Decrypt Example
<Transaction>
<Fields>
<Field>
<Name>PersonalId</Name>
<Display>Personal Id</Display>
<DataType>Text</DataType>
<Encrypt ERASE="Yes">Yes</Encrypt>
<Decrypt ERASE="Yes">Yes</Decrypt>
</Field>
<Field>
<Name>WithdrawalAmount</Name>
<Display>Removal Amount</Display>
<DataType>Money</DataType>
</Field>
</Fields>
</Transaction>