In the main view of the Type Editor, the various properties of a type can be edited.
This includes the attributes of the type, the type kind, a comment attached to the type (optional)
and a storage name (optional).
A type must have a valid name. This name is simply the file name of the corresponding type file.
This name must contain only letters, digits, and underscores, and must begin with a letter or an underscore.
Additionally, it must be unique in the project.
The name of a type is used as storage name unless a storage name has been specifically configured (see below).
A type contains the following properties which can be configured in the Type Editor:
The attributes that are added to the type are shown
in the table. To add a new attribute, click the 'Add and Configure New Attribute' button below
the table. To remove an attribute, select the row with the attribute, and click
the 'Remove Attribute' button. To configure an attribute,
click the 'Configure Attribute' button.
When you add or configure an attribute, the Attribute Configuration
dialog will automatically pop up.
Note that to conserve space, not all columns in the table are shown by default. To change which columns are
shown, right-click on any of the column names.
- Type Kind:
The type kind selection of a type is available for legacy purposes. Normally, the 'Standard Type" type kind
should simply be used, meaning it is not necessary to configure this property.
The drop-down allows the following selections:
- Standard Type indicates that the type is a standard type.
- Database Output Type (Legacy) indicates that the type is a Database Output type. This is a special type
required when storing data in a database created with versions of Kapow Katalyst prior to 7.2. This
type kind exists only for backwards compatibility purposes.
Database Output types require at least the following attributes with the indicated
These attributes are required because when a value extracted from a variable of a database output type
is persisted to storage, Kapow Katalyst will try to
find a value with the same 'refindKey' in the database. If such a value exists, it
will be updated, and if not, the extracted value will be inserted. The 'firstExtractedDate'
is the date and time when the value was extracted for the first time, and the
'latestExtractedDate' is the date and time when the extracted value was
inserted or updated for the last time.
The 'extractedInLatestRun' will be 'true' if the value was extracted in the
latest robot run.
If some of these required attributes are missing from a database output type, the type will not be valid.
The Type Editor will warn you if this is the case, and provide you with the possibility of adding the
Here you can add an optional comment to the type. The comment is only displayed in the Type Editor.
- Storage Name:
Here you can set a name to use when storing values from variables of this type, e.g. the table name in a database,
or the tag name in XML.
If you leave this field blank, the name of the type will be used instead for storage.
The intended use of the type may put some constraints on the storage name; for example,
if values of the type are going to be stored in a database, you must avoid using a storage name which is the same as
some keyword in the database you intend to use.