Add More Data Types for Envelope Custom Fields

Problem

Currently, Envelope Custom Fields only support Text and List field types. This limits how metadata can be captured and validated for envelopes.

Suggested Enhancement

Expand Envelope Custom Fields to support additional data types, such as:

• Date
• Number
• Boolean (Yes/No)
• Email
• Phone Number
• Currency
• Decimal
• Date & Time

Benefits

• Improves data quality through built-in validation.
• Reduces the need for custom integrations and manual formatting.
• Makes searching, filtering, and reporting on envelope metadata more reliable.
• Enables downstream systems to consume correctly typed data without additional parsing.
• Aligns Envelope Custom Fields with common business use cases such as contract renewal dates, invoice amounts, approval flags, and reference numbers.

Example Use Case

A company uses an Envelope Custom Field to store a contract expiration date. Since only text fields are available, users must manually enter the date in a specific format, increasing the risk of inconsistent or invalid values. A native Date field would provide a date picker, enforce valid formatting, and improve data consistency across integrations and reporting.

Requested Enhancement

Please extend Envelope Custom Fields to support additional data types beyond Text and List, starting with Date, while allowing future support for other commonly used field types such as Number, Boolean, Email, and Currency.