Relationship Templates
Use Relationship templates to explain how one object is linked to the other object. Download templates for Relationships from Axon to perform a bulk upload.
If an object in a relationship template contains a reference identifier column, the object name column becomes optional. When you perform a bulk upload, you must provide a value either in the name or reference identifier column even though both the columns are optional. For example, in the Business Area X Glossary template, the Glossary object has Glossary Ref. and Glossary Name columns that are optional. You need to fill in the Glossary Ref. or Glossary Name column before you upload the Business Area X Glossary template.
You can bulk upload the following types of relationships:
- •Attribute X Attribute
- •Attribute X Field
- •Business Area X Glossary
- •Business Area X Process
- •Business Area X System
- •Capability X Business Area
- •Capability X Client
- •Capability X Glossary
- •Capability X Legal Entity
- •Capability X Process
- •Capability X Product
- •Capability X System
- •Committee X Capability
- •Committee X Committee
- •Data Set X Client
- •Data Set X Legal Entity
- •Data Set X Product
- •Glossary X Client
- •Glossary X Glossary
- •Glossary X Product
- •Interface X Glossary
- •Legal Entity X Geography
- •People X People
- •Policy X Attribute
- •Policy X Business Area
- •Policy X Client
- •Policy X Data Set
- •Policy X Glossary
- •Policy X Legal Entity
- •Policy X Policy
- •Policy X Process
- •Policy X Product
- •Policy X Project
- •Policy X System
- •Process X Attribute
- •Process X Client
- •Process X Data Set
- •Process X Glossary
- •Process X Legal Entity
- •Process X Process
- •Process X Product
- •Process X System
- •Process X System Interface
- •Product X Business Area
- •Product X Client
- •Product X Legal Entity
- •Project X Attribute
- •Project X Business Area
- •Project X Capability
- •Project X Client
- •Project X Data Set
- •Project X Glossary
- •Project X Process
- •Project X Product
- •Project X Project
- •Project X System
- •Regulation X Policy
- •Regulation X Product
- •Regulation X Project
- •Regulation X Regulator
- •Regulation X Regulatory Theme
- •Regulator X Geography
- •Segment X Object
- •System X Client
- •System X Glossary
- •System X Legal Entity
- •System X Product
- •System X Resource
Attribute X Attribute
Download the Attribute X Attribute relationship template to bulk upload the relationships between attributes.
The following table describes the fields of the Attribute X Attribute relationship template:
Field | Type | Description |
|---|
Sourcing Logic | Optional | Indicates the logic that is applied to the flow of data. For example, selections or transformations performed. |
Sourcing Type | Required | The type of sourcing for the attribute. Specify whether the sourcing type is enforced lookup, unenforced lookup, or sourced from. |
Target Attribute Ref. | Optional | A unique reference identifier for the target attribute. |
Target Attribute Name | Optional | Name of the target attribute. |
Target Data Set Name | Optional | Name of the target data set that contains the attribute. |
Target System Name | Optional | Short name of the target system that contains the data set and the attribute. |
Source Attribute Ref. | Optional | A unique reference identifier for the source attribute. |
Source Attribute Name | Optional | Name of the source attribute. |
Source Data Set Name | Optional | Name of the source data set that contains the attribute. |
Source System Name | Optional | Short name of the source system that contains the data set and the attribute. |
Scope of Data | Optional | The actual scope of data. Specify if you want all the data or a subset of data. |
Interface Name | Optional | Name of the system interface. If you specify the Interface Name field, you need to fill in the Interface Source System and Interface Target System fields. |
Interface Source System | Optional | System from which the information flows out. |
Interface Target System | Optional | System to which the information flows in. |
Attribute X Physical Field
Download the Attribute X Physical Field relationship template to bulk upload the relationships between Axon attributes and Enterprise Data Catalog fields.
When you bulk upload the Attribute X Physical Field relationship template, Axon validates the operation based on the following details:
- •The Enterprise Data Catalog instance is configured, available, and running.
- •The field name, field identifier, and field type are present in Enterprise Data Catalog.
- •You have the required permissions to access the physical fields in Enterprise Data Catalog.
The following table describes the fields of the Attribute X Physical Field relationship template:
Field | Type | Description |
|---|
Attribute Ref. | Optional | A unique reference identifier for the attribute. |
Attribute Name | Optional | Name of the attribute. Enter a name that other Axon users can recognize easily. |
Attribute Data Set | Optional | Name of the data set that contains the attribute. If you provide a duplicate attribute name, you must provide the data set name. |
Attribute System | Optional | Name of the system that contains the data set and attribute. If you provide a duplicate attribute name, you must provide the system name. |
Name | Required | Name of the Enterprise Data Catalog field. Note: If you link an Axon attribute with an Enterprise Data Catalog field that contains the $ symbol in the field name, the field will not appear in Unison Search. |
Field ID | Required | Identifier for the Enterprise Data Catalog field. |
Field Type | Required | Type of the Enterprise Data Catalog field. To know the list of values that you can enter in this field, download the list of Enterprise Data Catalog physical fields as a CSV file, and see the Class Type column. To download the list of fields, click Create > Manage Catalog Links, go to the Physical Fields tab, click the  icon next to the Search option, and select Export to CSV. |
Business Area X Glossary
Download the Business Area X Glossary relationship template to bulk upload the relationships between a business area and glossary.
The following table describes the fields of the Business Area X Glossary relationship template:
Field | Type | Description |
|---|
Glossary Ref. | Optional | A unique reference identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Parent Business Area Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the business area and glossary. Select Is related to. |
Business Area X Process
Download the Business Area X Process relationship template to bulk upload the relationships between a business area and process.
The following table describes the fields of the Business Area X Process relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description of the relationship between the business area and process. |
Process Ref. | Optional | A unique identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Business Area Parent Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the business area and process. Select Process is related to Business Area. |
Business Area X System
Download the Business Area X System relationship template to bulk upload the relationships between a business area and system.
The following table describes the fields of the Business Area X System relationship template:
Field | Type | Description |
|---|
System Name | Required | Short name of a system or an acronym that other Axon users can recognize easily for a system. |
Parent System Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Business Area Parent Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the business area and system. Select Is related to. |
Capability X Business Area
Download the Capability X Business Area relationship template to bulk upload the relationships between a capability and business area.
The following table describes the fields of the Capability X Business Area relationship template:
Field | Type | Description |
|---|
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability if the capability belongs to a hierarchy. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Business Parent Area Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the capability and business area. Select Capability is related to Business Area. |
Capability X Client
Download the Capability X Client relationship template to bulk upload the relationships between a capability and client.
The following table describes the fields of the Capability X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Client Parent Name | Optional | Name of the parent client that you want to create. |
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability if the capability belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the capability and client. Select Is related to. |
Capability X Glossary
Download the Capability X Glossary relationship template to bulk upload the relationships between a capability and glossary.
The following table describes the fields of the Capability X Glossary relationship template:
Field | Type | Description |
|---|
Glossary Ref. | Optional | A unique identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Parent Capability Name | Optional | Name of the parent capability if the capability belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the capability and glossary. Select Is related to. |
Capability X Legal Entity
Download the Capability X Legal Entity relationship template to bulk upload the relationships between a capability and legal entity.
The following table describes the fields of the Capability X Legal Entity relationship template:
Field | Type | Description |
|---|
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability if the capability belongs to a hierarchy. |
Legal Short Name | Required | Name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Short Name | Optional | Name of the parent legal entity if the legal entity belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the capability and legal entity. Select Capability is related to Legal Entity. |
Capability X Process
Download the Capability X Process relationship template to bulk upload the relationships between a capability and process.
The following table describes the fields of the Capability X Process relationship template:
Field | Type | Description |
|---|
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Parent of the capability. The capability parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the capability and process. Select Is related to. |
Capability X Product
Download the Capability X Product relationship template to bulk upload the relationships between a capability and process.
The following table describes the fields of the Capability X Product relationship template:
Field | Type | Description |
|---|
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability. The parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the capability and product. Select Is related to. |
Capability X System
Download the Capability X System relationship template to bulk upload the relationships between a capability and system.
The following table describes the fields of the Capability X System relationship template:
Field | Type | Description |
|---|
System Name | Required | Short name of a system or an acronym that other Axon users can recognize easily for a system. |
System Parent Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Capability Ref. | Optional | A unique identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability. The capability parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the capability and system. Select Capability is supported by System. |
Committee X Capability
Download the Committee X Capability relationship template to bulk upload the relationships between a committee and capability.
The following table describes the fields of the Committee X Capability relationship template:
Field | Type | Description |
|---|
Committee Ref. | Optional | A unique reference identifier for the committee. |
Committee Name | Optional | Name of the committee. Enter a name that users can recognize easily. |
Committee Parent Name | Optional | Name of the parent committee that you want to create. |
Capability Ref. | Optional | A unique reference identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability if the capability belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the committee and capability. Select Is related to. |
Committee X Committee
Download the Committee X Committee relationship template to bulk upload the relationships between committees.
The following table describes the fields of the Committee X Committee Area relationship template:
Field | Type | Description |
|---|
Source Committee Ref. | Optional | A unique identifier for the source committee. |
Source Committee Name | Optional | Name of the source committee. Enter a name that other Axon users can recognize easily. |
Source Committee Parent Name | Optional | Name of the parent source committee if the committee belongs to a hierarchy. |
Target Committee Ref. | Optional | A unique identifier for the target committee. |
Target Committee Name | Optional | Name of the target committee. Enter a name that other Axon users can recognize easily. |
Target Parent Committee Name | Optional | Name of the parent target committee if the committee belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the source and target committees. Select Rolls up into. |
Data Set X Client
Download the Data Set X Client relationship template to bulk upload the relationships between a data set and client.
The following table describes the fields of the Data Set X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Client Parent Name | Optional | Name of the parent client that you want to create. |
Data Set Ref. | Optional | A unique reference identifier for the data set. |
Data Set Name | Optional | Name of the data set as known in the business organization. |
Data Set System Name | Optional | Short name of the system that contains the data set. |
Data Set System Parent Name | Optional | Parent name of the system that contains the data set. |
Relationship Type | Required | The type of relationship between the data set and client. Select Is related to. |
Data Set X Legal Entity
Download the Data Set X Legal Entity relationship template to bulk upload the relationships between a data set and legal entity.
The following table describes the fields of the Data Set X Legal Entity relationship template:
Field | Type | Description |
|---|
Legal Entity Short Name | Required | Name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Entity Short Name | Optional | Name of the parent legal entity if the legal entity belongs to a hierarchy. |
Data Set Ref. | Optional | A unique reference identifier for the data set. |
Data Set Name | Optional | Name of the data set as known in the business organization. |
Data Set System Name | Optional | Short name of the system that contains the data set. |
Data Set System Parent Name | Optional | Parent name of the system that contains the data set. |
Relationship Type | Required | The type of relationship between the data set and legal entity. Select Is related to. |
Data Set X Product
Download the Data Set X Product relationship template to bulk upload the relationships between a data set and product.
The following table describes the fields of the Data Set X Product relationship template:
Field | Type | Description |
|---|
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Data Set Ref. | Optional | A unique reference identifier for the data set. |
Data Set Name | Optional | Name of the data set as known in the business organization. |
Data Set System Name | Optional | Short name of the system that contains the data set. |
Data Set System Parent Name | Optional | Parent name of the system that contains the data set. |
Relationship Type | Required | The type of relationship between the data set and product. Select Is related to. |
Glossary X Client
Download the Glossary X Client relationship template to bulk upload the relationships between a glossary and client.
The following table describes the fields of the Glossary X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Parent Client Name | Optional | Name of the parent client that you want to create. |
Glossary Ref. | Optional | A unique reference identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the glossary and client. Select Is Related to. |
Glossary X Glossary
Download the Glossary X Glossary relationship template to bulk upload the relationships between glossaries.
The following table describes the fields of the Glossary X Glossary relationship template:
Field | Type | Description |
|---|
Source Glossary Ref. | Optional | A unique identifier for the source glossary. |
Source Glossary Name | Optional | Name of the source glossary. |
Source Parent Glossary Name | Optional | Name of the parent source glossary. The source glossary parent name must exist in Axon. |
Target Glossary Ref. | Optional | A unique identifier for the target glossary. |
Target Glossary Name | Optional | Name of the target glossary. |
Target Parent Glossary Name | Optional | Name of the parent target glossary. The target glossary parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the source and target glossaries. Select Is Related to. You can also create relationship types if required. |
Glossary X Product
Download the Glossary X Product relationship template to bulk upload the relationships between a glossary and product.
The following table describes the fields of the Glossary X Product relationship template:
Field | Type | Description |
|---|
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Glossary Ref. | Optional | A unique identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the glossary and product. Select Is Related to. |
Interface X Glossary
Download the Interface X Glossary relationship template to bulk upload the relationships between an interface and a glossary.
The following table describes the fields of the Interface X Glossary relationship template:
Field | Type | Description |
|---|
Relationship Type | Required | The type of relationship between the interface and the glossary. Select Expected glossary item coverage. |
Interface Ref. | Optional | A unique identifier for the system interface. |
Interface Name | Optional | Name of the system interface. |
Interface Source System | Optional | System from which the information flows out. |
Interface Target System | Optional | System to which the information flows in. |
Glossary Ref. | Optional | A unique identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Parent of the glossary term. The glossary parent name must exist in Axon. |
Legal Entity X Geography
Download the Legal Entity X Geography relationship template to bulk upload the relationships between a legal entity and geography.
The following table describes the fields of the Legal Entity X Geography relationship template:
Field | Type | Description |
|---|
Geography | Required | Name of the geography. Enter a name that other Axon users can recognize easily. |
Parent Geography | Optional | Name of the parent geography. |
Legal Short Name | Required | Short name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Short Name | Optional | Name of the parent legal entity if the legal entity belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the geography and legal entity. Select Is related to. |
People X People
Download the People X People relationship template to bulk upload the relationships between an employee and manager.
The following table describes the fields of the People X People relationship template:
Field | Type | Description |
|---|
Manager Email | Optional | Email address of the manager of the employee. |
Manager First Name | Optional | First name of the manager of the employee. |
Manager Last Name | Optional | Last name of the manager of the employee. |
Manager LAN ID | Optional | Network ID of the manager of the employee. |
Employee Email | Optional | A unique email address of the employee. Axon sends emails to this address. |
Employee First Name | Optional | First name of the employee. Specify the name as it is recorded in the LDAP directory server of your organization. |
Employee Last Name | Optional | Last name of the employee. Specify the name as it is recorded in the LDAP directory server of your organization. |
Employee LAN ID | Optional | Network ID of the employee. LAN ID might be required if you want to enable Single Sign-On authentication. If the LAN ID column is empty, you must not map the LAN ID column of the template to any field in the Axon Field column when you perform a bulk upload. |
Relationship Type | Required | The type of relationship between the employee and manager. Specify one of the following relationship types: - - Direct report
- - Dotted line
|
Policy X Attribute
Download the Policy X Attribute relationship template to bulk upload the relationships between a policy and attribute.
The following table describes the fields of the Policy X Attribute relationship template:
Field | Type | Description |
|---|
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Attribute Ref. | Optional | A unique reference identifier for the attribute. |
Attribute Name | Optional | Name of the attribute. Enter a name that other Axon users can recognize easily. |
Attribute Data Set | Optional | Name of the data set that contains the attribute. |
Attribute System | Optional | Name of the system that contains the data set and attribute. |
Relationship Type | Required | The type of relationship between the policy and attribute. Select Is related to. |
Policy X Business Area
Download the Policy X Business Area relationship template to bulk upload the relationships between a policy and business area.
The following table describes the fields of the Policy X Business Area relationship template:
Field | Type | Description |
|---|
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Parent Business Area Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and business area. Specify whether the policy is owned by the business area or the policy is a training requirement for the business area. |
Policy X Client
Download the Policy X Client relationship template to bulk upload the relationships between a policy and client.
The following table describes the fields of the Policy X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Client Parent Name | Optional | Name of the parent client that you want to create. |
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Parent of the policy if the policy belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and client. Select Is Related to. |
Policy X Data Set
Download the Policy X Data Set relationship template to bulk upload the relationships between a policy and data set.
The following table describes the fields of the Policy X Data Set relationship template:
Field | Type | Description |
|---|
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Data Set Ref. | Optional | A unique reference identifier for the data set. |
Data Set Name | Optional | Name of the data set. Enter a name that other Axon users can recognize easily. |
Data Set System | Optional | Name of the system that contains the data set. |
Relationship Type | Required | The type of relationship between the policy and data set. Select Is related to. |
Policy X Glossary
Download the Policy X Glossary relationship template to bulk upload the relationships between a policy and glossary.
The following table describes the fields of the Policy X Glossary relationship template:
Field | Type | Description |
|---|
Relationship Description | Optional | Description about the relationship between the policy and glossary. |
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Parent Policy Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Glossary Ref. | Optional | A unique reference identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the policy and glossary. Select Policy is regulating Glossary. |
Policy X Legal Entity
Download the Policy X Legal Entity relationship template to bulk upload the relationships between a policy and legal entity.
The following table describes the fields of the Policy X Legal Entity relationship template:
Field | Type | Description |
|---|
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Legal Short Name | Required | Short name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Short Name | Optional | Short name of the parent legal entity if the legal entity belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and legal entity. Select Policy is related to Legal Entity. |
Policy X Policy
Download the Policy X Policy relationship template to bulk upload the relationships between policies.
The following table describes the fields of the Policy X Policy relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description about the relationship between source and target policies. |
Source Policy Ref. | Optional | A unique reference identifier for the source policy. |
Source Policy Name | Optional | Name of the source policy. |
Source Policy Parent Name | Optional | Name of the parent of source policy. The parent name must exist in Axon. |
Target Policy Ref. | Optional | A unique reference identifier for the target policy. |
Target Policy Name | Optional | Name of the target policy. |
Target Parent Policy Name | Optional | Name of the parent of target policy. The parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the source and target policies. Select Is Related to. |
Policy X Process
Download the Policy X Process relationship template to bulk upload the relationships between a policy and process.
The following table describes the fields of the Policy X Process relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description about the relationship between the policy and process. |
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and process. Select Policy is regulating Process. |
Policy X Product
Download the Policy X Product relationship template to bulk upload the relationships between a policy and product.
The following table describes the fields of the Policy X Product relationship template:
Field | Type | Description |
|---|
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and product. Select Is Related to. |
Policy X Project
Download the Policy X Project relationship template to bulk upload the relationships between a policy and project.
The following table describes the fields of the Policy X Project relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description about the relationship between the policy and project. |
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Parent of the policy if the policy belongs to a hierarchy. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that users can recognize easily. |
Parent Project Name | Optional | Parent of the project if the project belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and project. Select Is related to. |
Policy X System
Download the Policy X System relationship template to bulk upload the relationships between a policy and system.
The following table describes the fields of the Policy X System relationship template:
Field | Type | Description |
|---|
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Policy Parent Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
System Name | Required | Short name of a system or an acronym that other Axon users can recognize easily for a system. |
Parent System Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the policy and system. Select Policy is regulating System. |
Process X Attribute
Download the Process X Attribute relationship template to bulk upload the relationships between a process and attribute.
The following table describes the fields of the Process X Attribute relationship template:
Field | Type | Description |
|---|
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Process Parent Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Attribute Ref. | Optional | A unique reference identifier for the attribute. |
Attribute Name | Optional | Name of the attribute. Enter a name that other Axon users can recognize easily. |
Attribute Data Set | Optional | Name of the data set that contains the attribute. |
Attribute System | Optional | Name of the system that contains the data set and attribute. |
Relationship Type | Required | The type of relationship between the process and attribute. Select Is related to. |
Process X Client
Download the Process X Client relationship template to bulk upload the relationships between a process and client.
The following table describes the fields of the Process X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Client Parent Name | Optional | Name of the parent client that you want to create. |
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Process Parent Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the process and client. Select Is related to. |
Process X Data Set
Download the Process X Data Set relationship template to bulk upload the relationships between a process and data set.
The following table describes the fields of the Process X Data Set relationship template:
Field | Type | Description |
|---|
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Process Parent Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Data Set Ref. | Optional | A unique reference identifier for the data set. |
Data Set Name | Optional | Name of the data set. Enter a name that other Axon users can recognize easily. |
Data Set System | Optional | Name of the system that contains the data set. |
Relationship Type | Required | The type of relationship between the process and data set. Select Is related to. |
Process X Glossary
Download the Process X Glossary relationship template to bulk upload the relationships between a process and glossary.
The following table describes the fields of the Process X Glossary relationship template:
Field | Type | Description |
|---|
Relationship Description | Optional | Description of relationship between the process and glossary. |
Glossary Ref. | Optional | A unique reference identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the process and glossary. Select one of the following types: - - Is used for Process
- - Is KDE for Process
|
Process X Legal Entity
Download the Process X Legal Entity relationship template to bulk upload the relationships between a process and legal entity.
The following table describes the fields of the Process X Legal Entity relationship template:
Field | Type | Description |
|---|
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Legal Short Name | Required | Short name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Short Name | Optional | Name of the parent legal entity if the legal entity belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the process and legal entity. Select one of the following types: - - Legal Entity is Data Controller
- - Legal Entity is Data Processor
|
Process X Process
Download the Process X Process relationship template to bulk upload the relationships between processes.
The following table describes the fields of the Process X Process relationship template:
Field | Type | Description |
|---|
Condition | Optional | The condition that you can specify only for a Control type process. The condition that you enter appears as annotation text on the output in Process maps when the predecessor is a Control type process. |
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Process Parent Name | Optional | Parent of the process. |
Predecessor Process Ref. | Optional | A unique reference identifier for the predecessor process. |
Predecessor Process Name | Optional | Name of the predecessor process. |
Predecessor Process Parent Name | Optional | Parent of the predecessor process. |
Process X Product
Download the Process X Product relationship template to bulk upload the relationships between a process and product.
The following table describes the fields of the Process X Product relationship template:
Field | Type | Description |
|---|
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the process and product. Select Is related to. |
Process X System
Download the Process X System relationship template to bulk upload the relationships between a process and system.
The following table describes the fields of the Process X System relationship template:
Field | Type | Description |
|---|
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Process Parent Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
System Name | Required | Short name of a system or an acronym that other Axon users can recognize easily for a system. |
Parent System Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the process and system. Select Process is applicable to System. |
Process X System Interface
Download the Process X System Interface relationship template to bulk upload the relationships between a process and system interface.
The following table describes the fields of the Process X System Interface relationship template:
Field | Type | Description |
|---|
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Process Parent Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Interface Name | Optional | Name of the system interface. |
Interface Source System | Optional | System from which the information flows out. |
Interface Target System | Optional | System to which the information flows in. |
Relationship Type | Required | The type of relationship between the process and system interface. Select Process supports Interface. |
Product X Business Area
Download the Product X Business Area relationship template to bulk upload the relationships between a product and business area.
The following table describes the fields of the Product X Business Area relationship template:
Field | Type | Description |
|---|
Product Ref. | Optional | A unique reference identifier for the product. |
Product Name | Optional | Name of the product. Enter a name that other Axon users can recognize easily. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Business Area Parent Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the product and business area. Select Is related to. |
Product X Client
Download the Product X Client relationship template to bulk upload the relationships between a product and client.
The following table describes the fields of the Product X Client relationship template:
Field | Type | Description |
|---|
Product Ref. | Optional | A unique reference identifier for the product. |
Product Name | Optional | Name of the product. Enter a name that other Axon users can recognize easily. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Parent Client Name | Optional | Name of the parent client that you want to create. |
Relationship Type | Required | The type of relationship between the product and client. Select Is related to. |
Product X Legal Entity
Download the Product X Legal Entity relationship template to bulk upload the relationships between a product and legal entity.
The following table describes the fields of the Product X Legal Entity relationship template:
Field | Type | Description |
|---|
Product Ref. | Optional | A unique reference identifier for the product. |
Product Name | Optional | Name of the product. Enter a name that other Axon users can recognize easily. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Legal Short Name | Required | Short name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Short Name | Optional | Short name of the parent legal entity if the legal entity belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the product and legal entity. Select Is related to. |
Project X Attribute
Download the Project X Attribute relationship template to bulk upload the relationships between a project and attribute.
The following table describes the fields of the Project X Attribute relationship template:
Field | Type | Description |
|---|
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Attribute Ref. | Optional | A unique reference identifier for the attribute. |
Attribute Name | Optional | Name of the attribute. Enter a name that other Axon users can recognize easily. |
Attribute Data Set | Optional | Name of the data set that contains the attribute. |
Attribute System | Optional | Name of the system that contains the data set and attribute. |
Relationship Type | Required | The type of relationship between the project and attribute. Select Is related to. |
Project X Business Area
Download the Project X Business Area relationship template to bulk upload the relationships between a project and business area.
The following table describes the fields of the Project X Business Area relationship template:
Field | Type | Description |
|---|
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Business Area Name | Required | Name of the business area. Enter a name that other Axon users can recognize easily. |
Business Area Parent Name | Optional | Name of the parent business area if the business area belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the project and business area. Select Project is related to Business Area. |
Project X Capability
Download the Project X Capability relationship template to bulk upload the relationships between a project and capability.
The following table describes the fields of the Project X Capability relationship template:
Field | Type | Description |
|---|
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Capability Ref. | Optional | A unique reference identifier for the capability. |
Capability Name | Optional | Name of the capability. Enter a name that other Axon users can recognize easily. |
Capability Parent Name | Optional | Name of the parent capability if the capability belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the project and capability. Select Is related to. |
Project X Client
Download the Project X Client relationship template to bulk upload the relationships between a project and client.
The following table describes the fields of the Project X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Client Parent Name | Optional | Name of the parent client that you want to create. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the project and client. Select Is related to. |
Project X Data Set
Download the Project X Data Set relationship template to bulk upload the relationships between a project and data set.
The following table describes the fields of the Project X Data Set relationship template:
Field | Type | Description |
|---|
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Data Set Ref. | Optional | A unique reference identifier for the data set. |
Data Set Name | Optional | Name of the data set as known in the business organization. |
Data Set System | Optional | Name of the system that contains the data set. |
Relationship Type | Required | The type of relationship between the process and data set. Select Is related to. |
Project X Glossary
Download the Project X Glossary relationship template to bulk upload the relationships between a glossary and project.
The following table describes the fields of the Project X Glossary relationship template:
Field | Type | Description |
|---|
Relationship Description | Optional | The description about the relationship between the glossary and project. |
Glossary Ref. | Optional | A unique identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Name of the parent glossary term. The glossary parent name must exist in Axon. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Parent Project Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the glossary and project. Select Glossary is used by Project. |
Project X Process
Download the Project X Process relationship template to bulk upload the relationships between a project and process.
The following table describes the fields of the Project X Process relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | The description about the relationship between the project and process. |
Process Ref. | Optional | A unique reference identifier for the process. |
Process Name | Optional | Name of the process. Enter a name that other Axon users can recognize easily. |
Parent Process Name | Optional | Name of the parent process if the process belongs to a hierarchy. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the project and process. Select Project is affecting Process. |
Project X Product
Download the Project X Product relationship template to bulk upload the relationships between a project and product.
The following table describes the fields of the Project X Product relationship template:
Field | Type | Description |
|---|
Description | Optional | The description about the relationship between the project and product. |
Product Name | Required | Name of the product. Enter a name that other Axon users can recognize easily. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the project and product. Select Is related to to indicate that the project is related to product. |
Project X Project
Download the Project X Project relationship template to bulk upload the relationships between projects.
The following table describes the fields of the Project X Project relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description about the relationship between source and target projects. |
Source Project Ref. | Optional | A unique reference identifier for the source project. |
Source Project Name | Optional | Name of the source project. |
Source Project Parent Name | Optional | Name of the parent of source project. The parent name must exist in Axon. |
Target Project Ref. | Optional | A unique reference identifier for the target project. |
Target Project Name | Optional | Name of the target project. |
Target Project Parent Name | Optional | Name of the parent of target project. The parent name must exist in Axon. |
Relationship Type | Required | The type of relationship between the source and target projects. Select one of the following values: - - Is related to
- - Is predecessor to
- - Is dependent on
|
Project X System
Download the Project X System relationship template to bulk upload the relationships between a project and system.
The following table describes the fields of the Project X System relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description about the relationship between the project and system. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that other Axon users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
System Name | Required | Short name of a system or an acronym that other Axon users can recognize easily for a system. |
Relationship Type | Required | The type of relationship between the project and system. Select one of the following values: - - Project is affecting System
- - Project is sourcing from System
|
Regulation X Policy
Download the Regulation X Policy relationship template to bulk upload the relationships between a regulation and policy.
The following table describes the fields of the Regulation X Policy relationship template:
Field | Type | Description |
|---|
Regulation Ref. | Optional | A unique reference identifier for the regulation. |
Regulation Name | Optional | Name of the regulation. Enter a name that other Axon users can recognize easily. |
Parent Regulation Name | Optional | Name of the parent regulation if the regulation belongs to a hierarchy. |
Policy Ref. | Optional | A unique reference identifier for the policy. |
Policy Name | Optional | Name of the policy. Enter a name that other Axon users can recognize easily. |
Parent Policy Name | Optional | Name of the parent policy if the policy belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the regulation and policy. Select Regulation affects Policy. |
Regulation X Product
Download the Regulation X Product relationship template to bulk upload the relationships between a regulation and product.
The following table describes the fields of the Regulation X Product relationship template:
Field | Type | Description |
|---|
Regulation Ref. | Optional | A unique reference identifier for the regulation. |
Regulation Name | Optional | Name of the regulation. Enter a name that other Axon users can recognize easily. |
Parent Regulation Name | Optional | Name of the parent regulation if the regulation belongs to a hierarchy. |
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the regulation and product. Select Is related to. |
Regulation X Project
Download the Regulation X Project relationship template to bulk upload the relationships between a regulation and project.
The following table describes the fields of the Regulation X Project relationship template:
Field | Type | Description |
|---|
Regulation Ref. | Optional | A unique reference identifier for the regulation. |
Regulation Name | Optional | Name of the regulation. Enter a name that other Axon users can recognize easily. |
Parent Regulation Name | Optional | Name of the parent regulation if the regulation belongs to a hierarchy. |
Project Ref. | Optional | A unique reference identifier for the project. |
Project Name | Optional | Name of the project. Enter a name that users can recognize easily. |
Project Parent Name | Optional | Name of the parent project if the project belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the regulation and project. Select Project is implementing Regulation. |
Regulation X Regulator
Download the Regulation X Regulator relationship template to bulk upload the relationships between a regulation and regulator.
The following table describes the fields of the Regulation X Regulator relationship template:
Field | Type | Description |
|---|
Regulator Reg Reference | Required | Reference identifier for the relationship between a regulator and regulation. |
Regulation Ref. | Optional | A unique reference identifier for the regulation. |
Regulation Name | Optional | Name of the regulation. Enter a name that other Axon users can recognize easily. |
Parent Regulation Name | Optional | Name of the parent regulation if the regulation belongs to a hierarchy. |
Regulator Name | Required | Full name of the regulator. |
Regulation X Regulatory Theme
Download the Regulation X Regulatory Theme relationship template to bulk upload the relationships between a regulation and regulatory theme.
The following table describes the fields of the Regulation X Regulatory Theme relationship template:
Field | Type | Description |
|---|
Regulation Ref. | Optional | A unique reference identifier for the regulation. |
Regulation Name | Optional | Name of the regulation. Enter a name that other Axon users can recognize easily. |
Parent Regulation Name | Optional | Name of the parent regulation if the regulation belongs to a hierarchy. |
Regulatory Theme Ref. | Optional | A unique reference identifier for the regulatory theme. |
Regulatory Theme Name | Optional | Full name of the regulatory theme. |
Parent Regulatory Theme Name | Optional | Parent object of the regulatory theme. |
Relationship Type | Required | The type of relationship between the regulation and regulatory theme. Select Is related to. |
Regulator X Geography
Download the Regulator X Geography relationship template to bulk upload the relationships between a regulator and geography.
The following table describes the fields of the Regulator X Geography relationship template:
Field | Type | Description |
|---|
Rel. Description | Optional | Description about the relationship between the regulator and geography. |
Regulator Name | Required | Name of the regulator. |
Geography Name | Required | Name of the geography. |
Parent Geography Name | Optional | Name of the parent geography if the geography belongs to a hierarchy. |
Segment X Object
Download the Segment X Object relationship template to move objects in bulk to target segments.
The following table describes the fields of the Segment X Object relationship template:
Field | Type | Description |
|---|
Object ID | Required | The unique identifier for the object that you want to move to a target segment. |
Object Type | Required | The type for the object that you want to move to a target segment. |
Target Segment | Required | The target segment to which you want to move all the objects to. |
System X Client
Download the System X Client relationship template to bulk upload the relationships between a system and client.
The following table describes the fields of the System X Client relationship template:
Field | Type | Description |
|---|
Client Name | Required | Short name of the client. Enter a name that other Axon users can recognize easily. |
Client Parent Name | Optional | Name of the parent client if the client belongs to a hierarchy. |
System Name | Required | Short name of a system or an acronym that other Axon users can recognize easily for a system. |
System Parent Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the system and client. Select Is related to. |
System X Glossary
Download the System X Glossary relationship template to bulk upload the relationships between a system and glossary.
The following table describes the fields of the System X Glossary relationship template:
Field | Type | Description |
|---|
Glossary Ref. | Optional | A unique reference identifier for the glossary. |
Glossary Name | Optional | Name of the glossary. |
Parent Glossary Name | Optional | Parent of the glossary term. The glossary parent name must exist in Axon. |
System Name | Required | Short name of a system that other Axon users can recognize easily. |
Strategic Data Set Name | Optional | The name of the data set that acts as a strategic data set. |
Strategic Data Set System | Optional | The name of the system that contains the data set that acts as a strategic data set. |
Relationship Type | Required | . The type of relationship between the system and glossary. Select one of the following types: - - Strategic Master Source for
- - Expected glossary item coverage
|
System X Legal Entity
Download the System X Legal Entity relationship template to bulk upload the relationships between a system and legal entity.
The following table describes the fields of the System X Legal Entity relationship template:
Field | Type | Description |
|---|
System Name | Required | Name of the system. Enter a name that other Axon users can recognize easily. |
Parent System Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Legal Entity Short Name | Required | Name of the legal entity. Enter a name that other Axon users can recognize easily. |
Parent Legal Entity Short Name | Optional | Name of the parent legal entity if the legal entity belongs to a hierarchy. |
Relationship Type | Required | The type of relationship between the system and legal entity. You can select one of the following values: - - Is Supported By
- - Is Used By
- - License is Owned by
|
System X Product
Download the System X Product relationship template to bulk upload the relationships between a system and product.
The following table describes the fields of the System X Product relationship template:
Field | Type | Description |
|---|
Product Name | Required | Name of the product. |
Product Parent Name | Optional | Name of the parent product if the product belongs to a hierarchy. |
System Name | Required | Short name of a system that other Axon users can recognize easily. |
Relationship Type | Required | The type of relationship between the system and product. Select Is related to. |
Product x Legal Entity Rel Type | Optional | The type of relationship between the product and the legal entity. Select Risk Owning Entity or Booking Entity. |
Legal Entity Short Name | Optional | Short name of the legal entity. |
Legal Entity Parent Name | Optional | Name of the parent legal entity if the legal entity belongs to a hierarchy. |
System X Resource
Download the System X Resource relationship template to bulk upload the relationships between an Axon system and Enterprise Data Catalog resource.
When you bulk upload the System X Resource relationship template, Axon validates the operation based on the following details:
- •The Enterprise Data Catalog instance is configured, available, and running.
- •The resource name and resource identifier are present in Enterprise Data Catalog.
- •You have the required permissions to access the resources in Enterprise Data Catalog.
The following table describes the fields of the System X Resource relationship template:
Field | Type | Description |
|---|
System Name | Required | Short name of a system that other Axon users can recognize easily. |
Parent System Name | Optional | Name of the parent system if the system belongs to a hierarchy. |
Name | Required | Name of the Enterprise Data Catalog resource. |
Resource ID | Required | Identifier for the Enterprise Data Catalog resource. |