Creating custom schema values for output parameters
When you define output parameters that use the DirectSQL, Array of Impact Object, or Impact Object format in the user output parameters editor, you also must specify a name and a format for each field that is contained in the DirectSQL, Array of Impact Object, or Impact Object objects.
About this task
O1.city="NY"
O1.ZIP=07002 You define the following custom schemas values
for this policy:
| Field | Entry |
|---|---|
| Name | City |
| Format | String |
| Field | Entry |
|---|---|
| Name | ZIP |
| Format | Integer |
If you use the DirectSQL policy function with the UI data provider or OSLC, you must define a custom schema value for each DirectSQL value that you use.
If you want to use the chart widget to visualize data
from an Impact object or an array of Impact objects with the UI data provider and
the console, you define custom schema values for the fields that are
contained in the objects. The custom schemas help to create descriptors
for columns in the chart during initialization. However, the custom
schemas are not technically required. If you do not define values
for either of these formats, the system later rediscovers each Impact
object when it creates additional fields such as the key field. UIObjectId,
or the field for the tree widget, UITreeNodeId. You
do not need to define these values for OSLC.