Adding Fields for Internal Use Only

UI extension fields can now be marked as internal. The easy way to do this when adding a new field to a UI extension is to check the new Snippets option ‘Internal’.


It can also be set later by manually adding the attribute data-internal to the HTML.

By default, a UI extension field is not internal.
When a UI extension field is marked as internal, the following people can see this field:

• Auditors, Specialists and Administrators of the account in which the UI extension was created, and
• Auditors, Specialists and Administrators of a support domain account that belongs to the same directory account as the account in which the UI extension was created.

However, if the option ‘Internal notes and internal UI extension fields are visible in other support domains‘ is not activated, or the UI extension is registered in a strong-privacy account, then the other support domain accounts that belong to the same directory account will not be able to see the internal fields of the UI extension.
Note that it is possible to make a whole section of fields within a UI extension, or even a whole UI extension, internal.

It is important to keep in mind that, when adding an internal field to a person record that is registered in a directory account, all people who have the Auditor, Specialist or Administrator role of any support domain of this directory account will be able to see this field.
4me users who are not allowed to see an internal UI extension field in a record, will also not be able to see this field’s value in the audit trail of this record.
This change also affected 4me’s APIs and its Import/Export functionality. The custom_fields attribute has been added to the REST API. In addition, the Custom Fields column has been added to the Export CSV files. The old custom_data attribute and the Custom Data column are still available, but are now deprecated.