Table of Contents

Search

  1. Preface
  2. Overview, Downloading, and Installing
  3. Administration API
  4. Identity Service API
  5. Screenflow Programming and SDK
  6. ActiveVOS WSHT API
  7. Embedding Request Forms in Standalone Web Pages
  8. XML-JSON for Process Central

7. APIs, SDKs, and Services

7. APIs, SDKs, and Services

Custom Data Types

Custom Data Types

Custom data types allow for custom rendering of fields in your entity. They also allow Process Designer to do type matching; this provides the guide developer more appropriate choices when mapping data to fields. For example, if the input to a service call step requires an
email
type, the Guide Designer editor will only show you options for the
email
type.
The sample project has an example of creating a custom type with a custom renderer. If you want to use an existing renderer with a new data type, override a base type and do not add a renderer. This means that your new data type inherits the renderer from its base type.
The following is an example of specifying an
accountNumber
type that has a base type of
string
. Even though this new type will render as a
string
during design time, guide developers will have more relevant data mappings for it.
Code Example: Sample Custom Data Type
<tns:type name="accountNumber" base="string" label="Account Number"> <tns:description>Account Number</tns:description> </tns:type>