The field name can contain underscores and alphanumeric characters and must be unique in your organization. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. Ensure the custom field name is not identical to any standard field name for that object.

If you want any custom fields beyond Agreement to map field data from the Agreement record to your content library, you need to configure the optional APTS_ContentConfig Admin object, as detailed in Set Admin Properties.