Panel | |
---|---|
|
...
Extending Attributes
The standard Registry Data Model is unlikely to cover all attributes required for a given CO. There are two three ways of extending the data model to add additional attributes.
Ad Hoc Attributes
Available as of Registry v3.3.0, Ad Hoc Attributes are simple key/value pairs attached to CO Person Roles or Organizational Identities. Ad Hoc Attributes are available via the REST API, are supported by Organizational Identity Source Plugins, and are made available to Provisioner Plugins.
Ad Hoc Attributes are not currently validated in any way (CO-1478) or available to attach to the CO Person (CO-469).
...
Extended Attributes
Note |
---|
Extended Attributes are deprecated as of Registry v3.3.0. Extended Attributes will be converted to Ad Hoc Attributes in a future release (CO-1478). |
The Registry supports simple extended attributes that can be attached to CO Person Role records on a per-CO basis. These extended attributes can be managed entirely via the Registry UI (select "Extended Attributes" from the CO menu) or the REST API, however the following limitations currently apply:
...
Deleting an extended attribute causes the associated column to be dropped from the table. If all extended attributes are deleted from a CO, then the dynamic table is dropped as well.
...
DIY (Do It Yourself)
More sophisticated requirements can be met by implementing native models, views, and controllers in the CakePHP framework. The best way to do that is probably to write a Plugin.
...