A Data repository allows you to group one to many data models that are related to a unified business or technical domain. For instance, the 'Human resource' Data repository contains all data models related to a company's HR systems.
Property | Definition |
---|---|
Identifier | Identifier used as a tag link reference. |
Name | Name of the data repository. |
Description | Description of the data repository. |
Type | A Data repository is associated with a type that has been defined in the ''Repository type" table, located in the 'Reference data' domain. When associating a repository with a type does not provide any immediate benefit, you can set this property to 'Unknown'. You can extend the list of types to meet your specific business needs by creating new records in the 'Repository type' table. |
Last refresh date | Date of the latest refresh executed at the data model level in the Data repository. |
A Data model is the main entry-point for the EBX® Information Governance Add-on. It contains the metadata the repository collects, and enriches and governs through the governance processes. It corresponds to a data model in EBX®.
Property | Definition |
---|---|
Data identifier | Identifier used as a tag link reference. |
Data model | The published data model to use as the basis for Administered Item management. |
Data space | The data space containing the data set from which you can create and synchronize Administered Items. Caution: The data space and data set should be stable throughout the governance repository life-cycle. If either are removed, or deleted you will still have access to the data model, but other features like links to data value will not be available. |
Data set | The data set from which you can create and synchronize Administered Items. Caution: The data space and data set should be stable throughout the governance repository life-cycle. If either are removed, or deleted you will still have access to the data model, but other features like links to data values will not be available. |
Data repository | A Data model can belong to one Data repository. The ability to group Data models by Data repository is not mandatory to use the add-on. |
Description | Description of the data model. |
Data nature | The 'Data nature' property allows you to declare the underlying characteristics that the Data model is designed around. All Administered Items created for this Data model will inherit their 'Data nature' from this value. When a Data model contains data that varies in nature, either the 'Data nature' property is set to 'All nature' or 'Unknown', or with one that is most commonly used in the data model. It is also possible to extend the list of natures by creating new records in the 'Date nature' table. |
De-duplication is active | You decide whether or not to activate the de-duplication process when the data model is configured in the repository. This decision is definitive for the related data model. The 'De-duplication is active' configuration property becomes read-only once the data model is declared in the repository. The de-duplication process is applied on fields defined in a data model. This means that only one Property is generated when two fields have the same logical name. The de-duplication process uses an exact matching execution that is case sensitive. For example, the fields 'age' and 'Age' are considered different fields. But if an 'age' field is located in two tables ('Employee' and 'Company') and each field name is an exact match, then only one 'age' property is created in the repository. This property is then linked to the two fields located in the two tables. When the de-duplication is activated, D.E.C. (Data Element Concept) types of Administered Items can be used to collect the definition related to the association of a field (Property) and a table (Object class). For instance, if an 'age' field exists in two tables ('Product' and 'Client') then the de-duplication process will generate these Administered Items:
The generic definition of the age is applied to the property and the additional definitions that are specific to the client and the product are attached to the related D.E.C.s. |
Last refresh date | Date of the last refresh of Administered Items applied to the data model. |
Property | Definition |
---|---|
Data repository | The Data repository containing the Data model. |
Data model | Data model that owns the Administered Item. |
Data nature | The 'Data nature' of the Administered Item is inherited from the 'Data nature' property defined at the Data model. You can change this value at the Administered Item level. |
ISO type | ISO-IEC 11179 type such as Object Class, Property, Value Domain, Data Element Concept, Data Element. |
Logical data type | Logical data type such as Table, Field, Data value |
Logical name | The logical name of the Item comes from the logical data model. This name cannot be modified manually. It must be identical to the one coming from the data model. It is not localized by languages since this is a unique logical name designated in the data model. It is automatically generated during the synchronization process between the data model and Administered Items. For the composite Administered Items the logical name is based on the logical names of the two related Administered Items. The composite Administered Items are the D.E.C. (Object class - Property) and the Data Element (D.E.C. - Value Domain). |
Logical label | The Item's logical label comes from the logical data model. This is the label used by language to identify the Item in the data model. |
Universal name | The 'Universal name' property is required and inherits from the logical name. You can change the inherited value to clarify naming and provide a more meaningful value. The universal name is not localized by languages since there is a direct relation with the logical name. To provide names in different languages, the "Context naming definition" is used. The universal name is not automatically supplied by the synchronization process between the data model and Administered Items. It is provided by a governance repository's administrator. Composite Administered Items' universal name is based on the composition of the related Administered Items' universal names. The composite Administered Items are the D.E.C. (Object class - Property) and the Data Element (D.E.C. - Value Domain). The 'Reset' button automatically retrieves the name based on the two related universal names. You can use the 'Freeze' property to protect a composite Administered Item's universal name value from an automatic refresh by the add-on during repository synchronization. |
Freeze universal name | If 'True': The universal name is no longer automatically synchronized with the names of the two related Administered Items. If 'False': The universal name is automatically synchronized with the names of the two related Administered Items. The 'undefined' value is considered as 'False'. |
Property | Definition |
---|---|
Item identifier group | |
Data identifier | The Administered Item's unique identifier. In the current add-on version the identifier value is automatically incremented by one. In a future version other data could participate in the 'Data identifier' property's computation. From a technical point of view, an Administered Item's primary key is a composite data structure that includes an object identifier (auto-incremented by one) and the current EBX® repository's unique identifier. This means that you can export and import one repository's Administered Items to another without risk of conflict between the primary key values. |
Item information group | |
Creation date | Automatically provided when the Administrated Item is created. |
Creation mode | When the Administered Item is automatically created by the synchronization process with a data model, the 'Creation mode' property displays as 'Automatic'. Otherwise, the 'Creation mode' property is 'Manual'. |
Last modification date | Automatically provided every time a modification occurs on the Administered Item. |
Effective date | When an Administered Item is created, its Registration status value is automatically set to 'Candidate'. When an Administered Item's Registration status moves to 'Standard', then its effective date is automatically populated with the current date. |
State | If the state value is 'Aligned', it means that the Administered Item can be associated to a data model element. If there is a misalignment, the state value is "No Data Model reference". Other states can exist depending on the governance process to be applied. |
Registration status | The registration status is defined in the ISO-IEC 11179 standard. It lets you track an Administered Item's publication level. The following list highlights the possible status as defined in the ISO-IEC standard.
|
Approval | Percentage of the approval process achieved. |
Deployment | Percentage of the deployment process achieved. |
Quality | Percentage of the quality process achieved. |
Additional attribute | Unrestricted additional information that can be added in the format of 'Meaning - Value'. |
Extended attribute | Controlled additional information that can be added in the format of 'Meaning - Value'. The 'Meaning' field allows you to select a table, and the 'Value' field to choose a record from the selected table. The list of the tables and fields for the selection is declared in the reference data domain, 'Extended attribute tables'. |
Application | The item can be linked to one to many applications. |
Confidentiality | The item can be attached to a level of confidentiality. |
Maintenance rules | The item can be linked to one to many maintenance rules. |
Is deleted item | When the Administered Item has been logically deleted the 'Is deleted' property is set to 'Yes', otherwise its value is 'No' |
Hidden item | You can hide any Administered Item from data views. The 'Is hidden' configuration property can be updated by the administrator profile. This feature is useful when you want to hide technical metadata or business metadata that isn't meaningful for governance. Under the EBX® Administration tab, the 'TIBCO EBX® Information Governance Add-on' data space allows you to activate/deactivate the process to hide the Administrated Items by user profiles. |
View by only | You can restrict the visibility of any Administered Item to one to many user profiles. Under the EBX® Administration tab, the 'TIBCO EBX® Information Governance Add-on' data space activate/deactivate the process to filter the Administrated Items by user profiles. |
Depending on the selected Item, this tab displays one of the groups described in the following sections.
Is Data Element Concept
A 'Data Element Concept' (D.E.C.) is the association between an 'Object Class' and a 'Property'. This is not similar to a field in a table because a property can be associated with many tables. For instance, the 'Employee', 'Client' and 'Company' tables can each have an 'age' field. In this case, the 'age' property is linked to the 'age' fields in each of the three tables.
Property | Definition |
---|---|
Object Class | The Object class used to define the D.E.C. |
Property | The Property used to define the D.E.C. |
Used in Data Element | The list of Data Element(s) that relies on this D.E.C. |
Is Data Element
A 'Data Element' is the actual value of a data. A 'Data Element' is used as an example to enrich the definition of an ISO item. A 'Data Element' exists as the link between a 'Data Element Concept' (D.E.C.) and a 'Value Domain'.
Property | Definition |
---|---|
Data Element Concept | The D.E.C used to define the Data Element. |
Value Domain | The Value domain used to define the Data Element. |
Data exemplary | This is an example of data value (first record in the table used as example). |
Is Object Class
An 'Object Class' is a representation of a composite data structure such as a business object or a group of related information.
Property | Definition |
---|---|
Used in Data Element Concept | List of Data Element Concepts that use this Object Class. |
Is Property
A 'Property' is an atomic item (field or association). The combination of a property with an 'Object Class' represents a 'Data Element Concept'. A property can be associated with many fields with the same name in different tables. For instance, the 'Name' property is linked to the 'name' fields that are located in the 'Employee', 'Supplier' and 'Partner' tables.
Property | Definition |
---|---|
Used in Data Element Concept | List of Data Element Concepts that use this Property. |
Used in Data Element | List of Data Elements that use this Property. |
Is Value Domain
A 'Value Domain' is either an atomic data type (integer, string, etc.) or an enumeration that provides a list of possible values for a 'Property'.
Property | Definition |
---|---|
Used in Data Element | List of Data Elements that use this Value Domain. |
Is table
A table as defined in SQL. With the semantic data management mode in EBX®, a table's data structure can be a complex data type that includes multi-occurrence fields.
Unlike for the block of information "Is field", the "State" field is not used since the current version of the add-on considers that an Object Class is linked to one "Table" at maximum. Then the state at the level of the Object Class is sufficient.
Property | Definition |
---|---|
EBX® table | The corresponding table in the logical data model. |
EBX® group | The group where the table is localized. |
Identifying properties | List of the properties that constitute the primary key. |
Relation Use when a table holds fields that are foreign keys | Table: linked to the table content |
Object class: linked to the administered item | |
Property: linked to the administered item that correspond to the foreign key | |
The cardinality information is retrieved from the logical data model in two different ways:
| |
Information | Retrieved from the logical data model in the 'Information' attached to the table. |
Is field
Atomic data with a simple data type: integer, string, etc. or a complex data type.
Property | Definition |
---|---|
EBX® table | The corresponding table in the logical data model. |
EBX® group | The group where the table is located |
EBX® field | The logical name of the field with its path in the table. |
Physical data type | The field's data type. |
Associated D.E.C | The list of D.E.Cs that use the property associated to this field. |
Is primary key | Boolean value that is retrieved from the logical data model. |
Is foreign key | Boolean value that is retrieved from the logical data model. |
Linked to the Administered Item | In case the field is a foreign key it gives the link to the related Administered Item. |
Information | Retrieved from the logical data model in the 'Information' attached to the field. In the case that the field is a foreign key you must establish a naming convention to be sure that the information property is used to describe the cardinality links on both sides of the association. For instance, between a 'Client' and 'Product', the foreign key field in the 'Client' table should have a definition with the following format: 'Product(1,*), Client(0,*), if the association means that a 'Client' can have 1 to many Product(s), and it is permitted to have Product not yet sold. You can define any naming convention depending on the preferred direction for reading the cardinality links between the two tables. An alternative to using the information statement applied to a foreign key, is the 'Association' concept (refer to EBX® documentation) that allows you to directly describe relationships. |
Is not null | Boolean value that is retrieved from the logical data model. |
Is Part of uniqueness constraints | Boolean value that is retrieved from the logical data model. |
Is auto increment | Boolean value that is retrieved from the logical data model. |
Minimum occurrence | The value is retrieved from the logical data model. |
Maximum occurrence | The value is retrieved from the logical data model. |
State | If the state value is 'Aligned', it means that the Administered Item can be associated to a data model element. If there is a misalignment, the state value is 'Unaligned data model'. Other states can exist depending on the governance process to be applied. Comment: the 'State' field is needed because a single Property can be linked to one to many fields. Each field holds a state to indicate its synchronization status in relation to the data model. |
Min size of the field | Integer value that is retrieved from the logical data model. |
Max size of the field | Integer value that is retrieved from the logical data model. |
Fixed size | Integer value that is retrieved from the logical data model. |
Max number of figures for an Integer and Decimal | Integer value that is retrieved from the logical data model. |
Number of figures after decimal for a Decimal | Integer value that is retrieved from the logical data model. |
Default value | The value is retrieved from the logical data model. |
Input pattern | The value is retrieved from the logical data model. |
Computed value | Boolean value that is retrieved from the logical data model. |
Inherited field | Boolean value that is retrieved from the logical data model. |
History activated | Boolean value that is retrieved from the logical data model. |
Category | The value is retrieved from the logical data model. |
Is association
Association between two tables linked either directly or through a join table (refer to EBX® documentation for a more in-depth explanation).
Property | Definition |
---|---|
EBX® table | The corresponding table in the logical data model. |
EBX® group | The group where the association is localized. |
Association | The logical name of the association as defined in the data model. |
Linked Object class | The object class that is reached by the association. |
Minimum occurrence | The minimum occurrence of the object class that is reached by the association. |
Maximum occurrence | The maximum occurrence of the object class that is reached by the association. |
Information | The value is retrieved from the logical data model. |
Is data type
Atomic data type (Integer, String, etc.) with facets for data validation (length, enumeration, etc.).
Property | Definition |
---|---|
EBX® table | The corresponding table in the logical data model. |
EBX® group | The group where the table is localized. |
EBX® field | The logical name of the field with its path in the table. |
Data type | Integer, String, etc. |
Data format | The value is retrieved from the logical data model. |
Minimum length | The value is retrieved from the logical data model. |
Maximum length | The value is retrieved from the logical data model. |
Minimum value | The value is retrieved from the logical data model. |
Exclusive | The value is retrieved from the logical data model. |
Maximum value | The value is retrieved from the logical data model. |
Exclusive | The value is retrieved from the logical data model. |
Is enumeration | Boolean value. The value is retrieved from the logical data model. |
Permission value | List of enumeration values when this data type is enumeration. This value is retrieved from the logical data model. |
State | If the state value is 'Data Aligned', it means that the Administered Item can be associated to a data model element. If there is a misalignment, the state value is 'Unaligned Data Model'. Other states can exist depending on the governance process to be applied. |
Is Domain
Group of tables that allows you to organize a data model into domains and sub-domains of tables.
Property | Definition |
---|---|
EBX® table | Not used for the domain definition. |
EBX® group | The group corresponding to the domain. |
Minimum occurrence | The value is retrieved from the logical data model. |
Maximum occurrence | The value is retrieved from the logical data model. |
Domain contain | The link to show all Object classes and Properties (in this group and in the table of this group) which are contained in this group. |
Property | Definition |
---|---|
Definition | |
Context | Link to a context that is defined through the 'Context' table. Every definition is provided for a context which could be a language, an organization, a classification or anything else. The context named "[ON] DMA" is automatically created during the process of synchronization between the data model and the Administered Items. It is used to collect all logical descriptions that exist in the data model, namely the label and description by languages. This information is then stored in the 'Definition' field. |
Definition | The definition is based on a label and a description localized by language. It is important to distinguish the languages used for information localization, and the languages used for creating contexts. For instance, a 'Spanish' context is created to provide definitions that are relevant for this language that covers many countries worldwide. But for this context, the definition are provided not only in Spanish but also in English and Portuguese. |
Related definition | A link to other Administered Items that are considered meaningful and complement, or enrich the current definition. |
Synonym | The synonyms can be provided by languages. In case of synonyms that are not reliant on any languages, then the 'Universal synonym' property is used. Any naming convention can be used to provide the list of synonyms. A best practice is to use the short description as an explanation of the synonyms origin and the long description provides the list of synonyms with a comma as separator. |
Universal synonym | One to many synonyms that are not dependent on a language. |
Description | An additional description of the item. |
Property | Definition |
---|---|
Party The Parties involved in this Administered Item. | |
Party | A Party involved in the Administered Item. |
Role | The role the Party plays regarding the Administered Item. |
Party type | The type of the Party automatically displays depending on the selected Party. |
Property | Definition |
---|---|
Property List of all properties of the current Administered Item of type Object class. |
Property | Definition |
---|---|
Also defined in List of all Administered Items for which the definition is related to the current Administrated Item. |
Property | Definition |
---|---|
Other relation List of the relations with the current Administered Items that are defined through the relation scheme |
Property | Definition |
---|---|
Classification List of the classification related to the current Administered Items that are defined through the classification scheme |
Property | Definition |
---|---|
Rules List of the rules related to the current Administered Items that are defined through the rules scheme |
Property | Definition |
---|---|
Data graph Graph view applied on the data model under governance |
Property | Definition |
---|---|
Meta Data graph Graph view of the metadata |
Property | Definition |
---|---|
Quality Display the quality indicators related to the Administered Item. The display is based on the dashboards configured in the TIBCO EBX™ Insight Add-on |
Property | Definition |
---|---|
Comment Display the comments related to the Administered Item. |
Property | Definition |
---|---|
History Displays the currently selected Administered Item's history of changes. | |
Date | The date and time of the modification. |
User profile | The user who modified the item. |
Operation | The type of operation that triggered history storage. |
Data model | The data model that owns the Administered Item. |
Universal name | The Administered Item's universal name. |
ISO type | The Administered Item's ISO type. |
Logical data type | The Administered Item's logical data type. |
Property | Definition |
---|---|
Name | A context is used to provide the naming and definition of any Administered Item. The context name can use any naming convention except the use of "[ON]" as prefix. This prefix is reserved for contexts that are created automatically during the synchronization process between a data model and Administered Items. |
Identifier | Identifier used as tag link reference. |
Description | The description of the context is localized by language. |
Language | A context can be related to a language. |
Country | A context can be related to a country. |
Criterion | A context can be related to a classification criterion coming from the classification scheme that is defined in the 'Classification' table group. |
Parent context | A hierarchy of context can be defined. |
Property | Definition |
---|---|
Administered Item from | The Administered Item from which this relationship stems. |
Administered Item to | The Administered Item where this relationship terminates. |
Relation | The type of relationship these items share. Several default types are provided. You can select Create from the drop-down list to add a custom defined relationship. Additionally, you can navigate to the table that stores these values and add one there. The table location is Reference data → Relation type |
Property | Definition |
---|---|
Identifier | Identifier used as tag link reference. |
Name | A criterion is a classification item that is attached to a 'Classification domain' through the 'Classification' table. |
Description | The description is localized by languages. |
Property | Definition |
---|---|
Parent criterion | The parent criterion in this relationship. The Criterion table stores these values. |
Child criterion | The child criterion in this relationship. The Criterion table stores these values. |
Property | Definition |
---|---|
Administered Item | The Administered Item you want to apply this classification to. |
Criterion | The criterion you want to use to define this classification. |
Description | A description of this classification. |
Property | Definition |
---|---|
Administered Item | The Administered Item that is linked to a Party among those declared in the 'Party' table domain. |
Party | A party among ones declared in the 'Party' table domain. |
Role | A role that the party plays in relation to the Administered Item. This role is one among the list that is defined in the 'Party' table domain. |
Party type | The type of the Party automatically displays depending on the selected Party. |
Description | Any additional description can be used. |
A Data repository can be associated to one to many parties playing certain roles.
Property | Definition |
---|---|
Data repository | A Data repository on which a party is configured. |
Party | A Party involved in the Data repository. |
Role | The role the Party plays in relation the Data repository. |
Party type | The type of the Party automatically displays depending on the selected Party. |
A Data model can be associated to one to many parties playing certain roles.
Property | Definition |
---|---|
Data model | A Data model on which a party is configured. |
Party | A Party involved in the Data model. |
Role | The role the Party plays in relation the Data model. |
Party type | The type of the Party automatically displays depending on the selected Party. |
Property | Definition |
---|---|
Home tab | |
Identifier | Identifier used as tag link reference. |
Name | A party can be any type of party such as: organization, application, systems, etc. |
Second name | Second name of the party |
Image | Specifies the image to associate with this party. This list allows you to select from images uploaded to the 'Reference' → 'Image' table. |
Display label on image | If set to 'Yes': The party's label, specified by the 'Name' property, displays along with the image. If set to 'No': The label does not display. |
Phone | Phone |
Country | Country |
Language | Language |
Party type | Any type of party can be created in the Governance repository, such as Organization, Business division, Region, Country, Application, System, Report, etc. You can attach any type of party to an Administered Item with additional information about the party's role. For instance, an 'Application SAP' party with its type as 'Application' can be 'Owner' of an 'Employee' Administered Item. |
Registration authority identifier | |
International code designator | When the Party identification must apply the ISO international coding convention. |
Organization identifier | When the Party identification must apply the ISO international coding convention. |
Organization part identifier | When the Party identification must apply the ISO international coding convention. |
Organization part identifier source | When the Party identification must apply the ISO international coding convention. |
Description | The description is localized by languages. |
Administered Item tab: This tab displays a RACI style view of the party involvement by Administered Item. | |
Administered Item | The Administered Item linked to a party declared in the 'Party' table. |
Role | A role that the party plays in relation to the Administered Item. You can specify these roles in the 'Party' domain. |
Party type | The type displays automatically depending on its assigned type. |
Description | You can use any additional information to enrich understanding of the party. |
Data model tab: This tab displays any roles the selected party plays with data models. | |
Data model | The data model on which the party plays a role. |
Role | The role the party plays in relation to the data model. |
Party type | The party type automatically displays depending on the selected party. |
Data repository tab: This tab displays any roles the selected party plays with data repositories. | |
Data repository | The data repository on which the party plays a role. |
Role | The role the party plays in relation to the data repository. |
Party type | The party type automatically displays depending on the selected party. |
This table allows you to create a parent/child relationship between parties.
Property | Definition |
---|---|
Parent party | The selected party becomes the parent in this relationship. |
Child party | The selected party becomes the child in this relationship. |
Property | Definition |
---|---|
Name | Any type of party can be created in the Governance repository, such as Organization, Business division, Region, Country, Application, System, Report, etc. You can attach any type of party to an Administered Item with additional information about the party's role. For instance, an 'Application SAP' party with its type as 'Application' can be 'Owner' of an 'Employee' Administered Item. |
Is prebuilt | A value of 'Yes' indicates that the add-on included this default 'Party type'. A value of 'No' indicates that you created this 'Party type'. You cannot change images associated to default 'Party type(s)'. However, if you've created your own 'Party type', you can associate it with a custom image. |
Image | Specifies the image to associate with this party type. This list allows you to select from images uploaded to the 'Reference' → 'Image' table. |
Display label on image | If set to 'Yes': The party type's label, specified by the 'Name' property, displays along with the image. If set to 'No': The label doesnot display. |
Description | The description is localized by languages |
Property | Definition |
---|---|
Name | Any type of role can be created in the Governance repository, such as Consumer, Owner, Populated by, Transformed by, Used by, etc. F For instance, an 'Application SAP' party with its type as 'Application' can be 'Owner' of an 'Employee' Administered Item. |
Is prebuilt | A value of 'Yes' indicates that the add-on included this default 'Party role'. A value of 'No' indicates that you created this 'Party role'. You cannot change images associated to default 'Party role(s)'. However, if you've created your own 'Party role', you can associate it with a custom image. |
Image | Specifies the image to associate with this party role. This list allows you to select from images uploaded to the 'Reference' → 'Image' table. |
Display label on image | If set to 'Yes': The party role's label, specified by the 'Name' property, displays along with the image. If set to 'No': The label doesnot display. |
Description | The description is localized by languages. |
The 'Rules' domain allows you to create rules and link them to Administered items. In the current version of the EBX® Information Governance Add-on repository, you have to manually create the rules you want to attach to Administered items.
Property | Definition |
---|---|
Rule name | You can use any naming convention. |
External code | An open field that allows you to define a code for the rule. |
Rule description | Free description. |
Rule message | The error message the rule can raise. |
Type of rule | A rule can be categorized into a type of rule. |
Scope | Description of the rule's scope. |
Metric | Description of the rule's metric. |
Comments | Additional information used to describe the rule. |
Property | Definition |
---|---|
Item | The Item on which the rule is applied. |
Rule | The rule applied on the Item. |
Property | Definition |
---|---|
Name | Name of the Logical data type. |
Icon | The icon used to represent this logical data type. |
Display label on icon | Determines whether the label displays on the icon. |
Description | Description. This information is provided by the add-on and cannot be modified. |
Property | Definition |
---|---|
Name | Name of the ISO type. |
Icon | The icon used to represent this ISO type. |
Display label on icon | Determines whether the label displays on the icon. |
Description | Descriptive text for this ISO type. |
Property | Definition |
---|---|
Tag link | The code used to refer to a piece of information in the EBX® Information Governance Add-on repository. For instance 'ai' allows you to refer to an Administered Item. Any description text can integrate "tag links" to refer to any information contained in the governance repository. For instance, the text 'Please refer to the item ai3392' is automatically translated into 'Please refer to the item 3392' (the hyperlink is computed thanks to the key word 'ai'). A list of ready-to-use key words is available to reach any information in the governance repository (refer to the 'Tag link' table in the 'Reference data' group). |
Reference table | The table related to the tag link. |
Description | Description of the tag link. |
Property | Definition |
---|---|
Name | The 'Operation' property is used to state how an Administered Item is created: either automatically by the add-on or manually by a user. |
Icon | The icon used to represent this operation. |
Display label on icon | Determines whether the label displays on the icon. |
Description | The description is localized by languages. |
Property | Definition |
---|---|
Name | The 'State' property is used to indicate whether an Administered Item is aligned ("Aligned") or not ("No Data Model reference") with its underlying data model. |
Icon | The icon used to represent this state. |
Display label on icon | Determines whether the label displays on the icon. |
Description | The description is localized by languages. |
Property | Definition |
---|---|
Name | Registration status is used to follow the life-cycle of an Administered item from its creation to its deletion. Any type of registration status can be created. The add-on provides a Registration status set that includes those defined in the ISO-IEC 11179 standard. |
Icon | The icon used to represent the registration status. |
Display label on icon | Determines whether the label displays on the icon. |
Description | Descriptive text for this ISO type. |
Property | Definition |
---|---|
Name | A relation is used to indicate what type of relationship it exists between two Administered Items. Any type of relation can be created. |
Description | The description is localized by languages. |
Property | Definition |
---|---|
Name | Any type of data repository is possible. |
Icon | The icon used to represent this repository type. |
Display label on icon | Determines whether the label displays on the icon. |
Description | The description is localized by languages. |
Property | Definition |
---|---|
Name | Any type of data nature is possible. |
Icon | The icon used to represent this data nature. |
Display label on icon | Determines whether the label displays on the icon. |
Description | The description is localized by languages. |
Property | Definition |
---|---|
Code | Any country can be created. |
Name | Name of the country. |
Property | Definition |
---|---|
Code | Any language can be created. |
Name | Name of the language. |
Property | Definition |
---|---|
Code | Any application can be created. |
Name | Name of the application. |
Description | Optional information. |
Property | Definition |
---|---|
Code | Any application role can be created. |
Name | Name of the role. |
Description | Optional information. |
Property | Definition |
---|---|
Code | Any application status can be created. |
Name | Name of the status. |
Description | Optional information. |
Property | Definition |
---|---|
Code | Any confidentiality can be created. |
Name | Name of the confidentiality. |
Description | Optional information. |
Property | Definition |
---|---|
Code | Any maintenance rule can be created. |
Name | Name of the maintenance rule |
Description | Optional information. |
Property | Definition |
---|---|
Code | Any rule type can be created. |
Name | Name of the rule type. |
Description | Optional information. |
This table allows you to define the list of tables and fields used as 'Extended data' to enrich the metadata attributes. Extended data display as coupled data: Meaning (the table to select) and Value (a value in the selected table).
Property | Definition |
---|---|
Name | Name used in the drop-down list 'Meaning' |
Data space | Data space where the table is located |
Date set | Data set where the table is located |
Table | Table used to feed the 'Meaning' drop list in the Extended attribute. |
Field selection | Field used to feed the 'Value' drop list in the Extended attribute. |
Restricted to data model | This table is only accessible to the Items created from the data model listed here. If this field is empty, all Items can access this table. |
Automatic display | Setting this property to 'Yes' automatically displays this table when users open the related Item. Note that when enabled you may receive a confirmation dialog from your browser after opening and closing a related Item—even if no changes were made. |
The 'Image' table allows you to upload images to the location specified in 'Administration' → 'TIBCO EBX® Information Governance Add-on' → 'Images'. You can then assign an image to Party, Party type, or Party role records that display in the Business Glossary.
To upload an image:
From the 'Actions' menu, select 'Information Governance' → 'Upload image'.
Enter a name for the image and specify the path to the image. Alternatively, you can use the 'Browse' option to point to the image.
After clicking Upload Image, a preview of the image displays and you can still alter the name before saving and closing.
This table allows you to set which icons represent Item quality information when displayed in the Business Glossary. You can set icon display for 'Approval', 'Deployment', and 'Quality'.
Property | Definition |
---|---|
Code | The identifier for this icon configuration. |
Quality item | The quality information this configuration pertains to. |
Display digit on icon | Determines whether the overall value displays along with the icon. |
Display label on icon | Determines whether the label displays with the icon. |
Label | Specifies the label. |
Threshold value | Set the threshold value. |
Icon below threshold | Determines the icon used if the value is below the specified threshold. |
Icon equal 100 | Determines the icon used if the value is 100. |
Icon equal 0 | Determines the icon used if the value is 0. |
Icon equal threshold | Determines the icon used if the value is equal to the specified threshold. |
Icon above threshold | Determines the icon used if the value if above the specified threshold. |
Java class compute value | The Java class used to compute the quality value. |
This table allows you to assign icons to represent different types of Administered Items when viewing the 'Item' table as a hierarchy. Simply create a new record and link the 'Type' with a provided icon.
Property | Definition |
---|---|
Type | Indicates the type of node displayed in the hierarchy. |
Icon | Specifies which image displays for the selected type. |
You can save a history of actions that modify Administered Items. You must enable this feature by setting the 'Enable history' property in the Information Governance → User preferences to 'Yes'. Although, item modification saves a history record, a record is not saved when an item is created, you comment on an item, or physically delete an item. To view all item history, use the 'History' table. If you only want to view a specific item's history, open the item and select its 'History' tab.
Each record in the 'History' table corresponds to an action taken that modified an Administered Item. The number of records stored in this table depend on how you set the user preferences. See the 'Configuring user preferences' section for more information. When viewing the 'History' table, you can select 'Information Governance' → 'Purge Administered Item history' to clear the records.
Each record in this table contains the following information about item changes:
Property | Definition |
---|---|
Date | The date and time of the modification. |
User profile | The user who modified the item. |
Operation | The type of operation that triggered history storage. |
Data model | The data model that owns the Administered Item. |
Universal name | The Administered Item's universal name. |
ISO type | The Administered Item's ISO type. |
Logical data type | The Administered Item's logical data type. |
This table stores operations that can apply to events that trigger an entry in the history log.