The organization data defined on Emakin is stored on a structure as described by the model schema below. It consists of multiple entities and each one of them has a corresponding database table to store its data. These tables are automatically created when a new domain is registered to Emakin. Organization model schema can be modified as adding new entities and relations but by default it is in the form depicted in the image below.
...
Details
When we look at the image above we see tables with titles and listed items, lines between these boxes connecting some of them and various figures on these connecting lines. The boxes represent the entities, building blocks of the organization schema. Looking at their names we can see that every one of them represents a meaningful real-world concept like Users, OrganizationUnits, Positions etc. Lists inside them contain their defined data fields. The line drawn between two entities shows that they have a relation. You can use this relation to go from one entity to another to get its associated data. The name written on a line specifies the relation name and the arrow heads indicates the relation's direction(s). There There are also different figures on the both end ends of relation lines, which states state the type of relation. See the image below for relation types:
For example if you have a User Id, you can get its Employ
...
We can use a relation to go from one entity to another to get its associated data by using $Membership methods. For example assume that we want to get the department name of a workitem's initiator user. We can acquire it as in the example below:
| Code Block | ||
|---|---|---|
| ||
$Membership.GetProperty( $Initiator, 'Employee.Department.Name') |