Terminology
Reporting API Name | Designer Name |
---|---|
IsMasterVariant | When the variants feature is enabled, this indicates the primary variant. |
IsRootNode | If this is the item of the highest hierarchy within the facet, e.g. Process House. |
SupportsVariants | If this element supports different variants in the case that variant management is in use for the database. |
SupportsVersions | If this element supports different versions. |
Variants | A list of variants of the elements and their details. |
Versions | A list of the versions of this element and their details for each version. |
Attributes | Attributes can be different per element type and configurations to elements by the designer Admin in the “extended configuration”. |
CreationId | Original ID for any element within a process that is just part of a process (Tasks, Events, Conditions, Rules), and can be used to identify unique tasks. This is kept consistent while tasks get duplicated into new process versions and get new IDs. |
Content | A list of objects that is modeled within the Element, which can include children and non-hierarchical elements. |
Related | A list of objects that are related to the Element, such as their accountable organization and system used. |
ContainerPermaLink | Link to the latest, relevant version of the element. |
FacetName | The facet this element belongs to. An element can only belong to a single facet. |
Id | Container ID of the element which is the same across all versions of the element. |
Ordering | Ordering of the element in the Hierarchy , if custom defined. |
PermaLink | Link to a version of the element. |
ElementHierarchy:Key | Element Id |
The Reporting API is organized in objects that share a set of similar attributes. The following diagram describes their relation to each other. Common attributes have been extracted to the table StandardAttributes for brevity.
mermaidmermaid