...
Attribute Enumerations are now based on Dictionaries. Dictionaries will automatically be created for existing Attribute Enumerations. No specific manual tasks are required as part of this migration, however deployments with multiple enumerations over the same values may wish to update their configurations to use shared Dictionaries (to avoid duplicate data sets).
New Organizations Object
Registry v4.0.0 introduces a new Organization object. This isn't of itself an issue regarding attention, except that there was a legacy (never functional) Organization object that was removed in v2.0.0. Deployments that came online on versions prior to v2.0.0 might still have the old cm_organizations (obsolete) table present if it were not manually dropped. If the deployment is also using Postgres, then a schema management bug may prevent the table from being fully converted to the new cm_organizations structure. This will result in some columns having the wrong widths. Operationally, this is unlikely to cause problems, and will eventually get corrected when the underlying schema management bug is addressed. However, affected deployments may wish to manually drop the old table before upgrading, or review the column widths after upgrading to make sure they are correct.