You are viewing the documentation for an outdated or unreleased 9.5 version.
This page is also available in versions: 7.6, 7.7, 7.8, 8.0, 8.1, 9.0, 9.1, 9.2, 9.3, 9.4, 9.5, 9.7 (current), devel

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

9.5:documentation:eav [2019/02/14 15:33] (current)
Line 1: Line 1:
 +<- .:​organization | Organization structure ​ ^ .:start | Documentation ^ .:systems | Systems ->
 +
 +====== Extended attributes (EAV) ======
 +
 +Entities (Identities,​ Roles...) in CzechIdM contain a set of basic attributes which can deal with most of general situations. However, due to the fact, that the implementation needs vary, it often happens that there is not enough basic attributes. Therefore, the so-called extended attributes (EAV) can be added to important entities in GUI. CzechIdM contains an agenda where these attributes can be managed.
 +
 +{{ :​devel:​documentation:​role_eav.png | EAVs of Role entity}}
 +
 +Those entities currently support extended attributes:
 +  * Role
 +  * Identity
 +  * Tree Node
 +
 +===== EAV Forms =====
 +To be able to add an attribute to an entity, a **form** must be set up first. The form can be imagined as a set of extended attributes of an entity. There can be more forms for one entity (Identity, Role...), and thus the extended attributes can be logically divided according to them. Every entity that supports EAVs always has default form defined after CzechIdM installation. Tt has no EAVs at the beginning, administrators can create them. 
 +
 +{{ :​devel:​documentation:​role_forms.png | Forms for entity}}
 +
 +====== Read more ======
 +
 +===== Admin tutorials =====
 +  * [[tutorial:​adm:​eav| Manage EAVs and forms]]
 +
 +===== Admin guide =====
 +  * [[.eav:​adm:​eav|Overview of EAVs and dynamic forms]]
 +
 +===== Devel guide =====
 +  * [[.application_configuration:​dev:​dynamic-forms| Dynamic forms]]
 +
 +===== Devel tutorials =====
 +  * [[tutorial:​dev:​how_to_create_eav_face_type]]
 +