Background
This article relates to iPaaS.com custom fields only. Custom fields from subscriptions are handled in the Subscriptions Management section.
Custom fields in iPaaS.com allow you to create text fields that are not supported natively in iPaaS.com, associate that field with a data model and populate it with data from an integration subscription (or custom API integration). Custom fields exist at both the data model level as well as all child levels.
If custom fields are used in default mapping collections they are added when you add the subscription.
Custom fields are not available on the create screen, only on the edit screen.
Basic Example Use Cases for Custom Fields
A merchant that sells goods that require refrigeration at specific temperatures: Create a custom product field to hold that temperature.
A company needs to track a certain skill level for an employee: Create a custom employee field to track.
A merchant has an engraving option: Create a custom transaction field to hold this data.
Add/Edit Screen
Name*: The name in IPaaS.com for this custom field. This will appear when adding/updating records.
Description: A description of the field. Could be used to denote the system this field comes from.
System: Will default to iPaaS.com and can not be changed.
Module*: The data model and child records where this field will be created.