For each type of transaction, we can define a schema of what information gets passed in during creation. Each transaction type has a transaction type ID. Transaction Types consist of custom field schemas and custom statuses.
Transactions have support for the following field types:
Customers can archive both Transaction fields and Types, which enables updates in the event a user saves the wrong field key, or a customer's model changes over time. After a field is archived on a Transaction Type or a Transaction Type itself gets archived, all associated Workflows must get updated.
Updated about 1 month ago