Date: Fri, 29 Mar 2024 00:00:14 +0000 (UTC) Message-ID: <1187423525.7231.1711670414405@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7230_864944790.1711670414404" ------=_Part_7230_864944790.1711670414404 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As of v2.0.0, Registry supports Attribute Enumerations, wh= ich allow the possible values of free-form fields to be constrained to a se= lection of pre-determined values.
The following attributes can be enumerated (via CO >>= Configuration >> Attribute Enumerations):
When Organizational Identities are pooled, Attribute Enumerations for OrgIdentity= attributes can only be set by a platform administrator, and will apply to = all COs. These enumerations are set via the Platform >> = Attribute Enumerations menu.
Once at least one enumeration is defined for a given attribute, all poss= ible data entry points for that attribute will be constrained to the enumer= ated values. This includes
For enumerations attached to CO attributes, if normalizations are enabled the enumerated value w= ill be normalized.
Enumerations only apply to records as they are updated. Deleting, editin= g, or suspending an enumeration will not by default affect any existing rec= ords. However, if someone edits a record with a value that no longer correl= ates to an enumeration, the value will need to be updated before the record= can be saved.
As of Registry v4.0.0, Attribute Enumerations are implemented using Dictionaries. If the selected Di= ctionary defines both Values and Codes, the Codes will be stored as the val= ue in the database, so be sure to define Codes for all Dictionary Entries w= ithin the Dictionary, or do not use any Codes within the Dictionary. Dictio= nary Entry ordering may also be used to place certain values at the top of = the enumeration list. (Entries will otherwise be sorted alphabetically.)
Only one D= ictionary may be attached to a given attribute.
As of Registry v4.0.0, Attribute Enumeration support an Allow Other<= /em> option. When enabled, the attribute will allow a free-form field in ad= dition to the enumerations defined in the associated Dictionary. Allow = Other is not currently supported for CoPersonRole and OrgIdentity attr= ibutes within an Enrollment Flow, although it is supported for these attrib= utes in other contexts (CO-2012).