Increase the number of possible ENUM and ENTITY_LINK custom fields

Idea ID 2762557

Increase the number of possible ENUM and ENTITY_LINK custom fields

Requested functionality :

Increase the number of possible ENUM and ENTITY_LINK custom fields that can be defined on an entity.

It should be possible to define 40 - 50 such fields.

Use case :

In our change management process, we have defined 12 qualification questions that allow the risk of a requested change to be assessed in a deterministic manner.

Answers to these questions are to be selected from a list of options.

We would like to save these answers in the change ticket.

However, given the current limit of 12 custom ENUM fields, and the need to add a few other ENUM fields, this is not currently possible.

We also reviewed the option to create a custom lookup table and use ENTITY_LINK type fields instead, but with the current limit of 15 custom ENTITY_LINK fields, this is not a sustainlable option, either.

Tags (2)
1 Comment
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.