[CLOSED] - Allow a display name for custom fields

[#1]

This post has been closed as a duplicate. All votes have been moved to the original: Have separate Field API Names vs Label

We have multiple regions on our instance and so we start the name of new fields with the region name e.g. a stakeholder field would be called "EMEA Stakeholders". (or "APAC Stakeholders" if set-up by the Asia Pacific region)

This can be become a bit repetitive visually on custom forms having each field start with the same letters.

We would love a way to set an optional 'display name' for these fields that would show in custom forms.

[#2]

note I have the same ask here -- its gotten sooo many upvotes

https://support.workfront.com/hc/en-us/community/posts/115000904754-Custom-Fields-Creating-an-alias-...

[#3]

We have the same requirement also please.

[#4]

Completely agree. This is very much needed. My company has THOUSANDS of fields, many that are nearly identical, but can't be re-used because of existing limitations.

Each instance of a form should be able to mask the display label and values for existing fields appropriate to the work group.

In addition to a Unique Display label, each instance of a radio button or multi-select fields should have its own masked list of values to display. For example, the admin might need an existing "Region" multi-select field that has 5 values already, of which he can use 3, but he needs to add 2 not on the list. So he adds the 2 new values and configures his form to display 3 of the existing 5 values plus the 2 new ones on his instance of the form.

This allows him to re-deploy a field that currently he can't use, instead of creating a new one.

In addition, each instance of the field on a new custom form should allow a distinct default value, as well as a distinct required-not required setting.