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
type, the Guide Designer editor will only show you options for the
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
type that has a base type of
. Even though this new type will render as a
during design time, guide developers will have more relevant data mappings for it.