Just tried to setup a field with a pull down list and received the dreaded error:
The following fields are invalid: value 1,589 length is too long, max 255, label 1,589 length is too long, max 255
First, the message is not clear. It should read that the combined length of all pull down values cannot exceed 255. BTW, this error occurs because the field is a max value of 255 in a repository due to a constrained design for handling user defined fields and their values. Folks, it's 2017, and these constraints are remnants of limited architecture design.
I propose the following redesign of custom forms for Workfront.
Custom Forms should be part of a separate Metadata Object Model (MOM) that can be associated with any other type of Object in WF. The MOM should support the following:
- Ability to create fields of any size, where values are stored as separate records (instantiations) rather than in a single record with implied separators.
- Ability to define, build, and import ontologies
- Ability to reference industry standard metadata (Dublin Core minimally)
- Ability to create and update taxonomies
- Ability to import and/or link to Metadata Models (3rd party standards per OMG) using a MOF compliant design
- Ability to associate the MOM with any WF object (Project, Issue, Risk, Document, etc). Users should not be forced to create separate User Defined Fields (UDFs) for each object type in WF. That is a sub-optimal design and creates barriers for reuse and increases the likelihood of errors.
- Ability to support ETL for data upload from existing user repositories
