Data Governance User Guide > Bulk Upload Data > Bulk Upload Templates

Bulk Upload Templates

You can download predefined Microsoft Excel templates to bulk upload in Axon. You can also use custom Microsoft Excel templates to upload data to Axon. Informatica recommends that you use the templates that Axon provides.

You can use a comma-separated-value (CSV) file format to bulk upload data to Axon. You can use a CSV file that you created to upload data to Axon. If you want to use the Axon template, you need to download and save the Microsoft Excel template in the CSV format.

Each facet has some default configuration values, such as lifecycle, classification types, and relationship types, that are predefined in the template. You can configure these values from the Admin panel. If your current Axon instance was upgraded from a previous version, you might see more values in the drop-down configuration list from the previous version. If you perform a fresh install, you can see the latest, shorter list of drop-down configuration values.

Use the bulk upload template when you need to perform the following tasks:

•Add new objects, relationships, and roles to Axon.
•Update existing objects, relationships, and roles in Axon.

Template Types

You can bulk upload the Object, Relationship, and Role template types to Axon. The Object templates include the following categories:

•Business & Change
•Organizational
•Regulatory
•Data & Technology

After you download a template, you can view that the worksheet name is provided for the template for ease of use and reference. The worksheet name format for the template that you want to bulk upload is Create <Template Name>. For example, if you want to upload the System X Client template, the worksheet name is Create System X Client. The worksheet name format for the template that you want to bulk update is Update <Template Name>. For example, if you want to update the Glossary object, the worksheet name is Update Glossary.

If you have created segments in Axon, you can view the Segment column in most of the downloaded Object templates. You cannot view the Segment column for the following object templates:

•Attributes
•Org Unit
•People
•Data Quality Rule
•System Interface

In the Object and Roles templates, you can see the following optional columns for the user details: User Email, User First Name, User Last Name, and User LAN ID. When you bulk upload objects and roles, you must enter at least one of the user details so that it becomes easier to identify an object and role. You can enter an email address, LAN ID, or a combination of first and last name.

Most of the templates contain the reference identifier column that is optional. If you leave the column empty and map the empty column during the bulk upload process, the operation fails because the Reference column cannot have null values. If you want to map the Reference column, ensure that you enter a value in the template.

Business & Change Object Templates

Use Business and Change object templates to explain different business functions and changes to objects in an organization. Download templates for Business and Change objects from Axon to perform a bulk upload.

You can bulk upload the following types of objects:

•Committee
•Policy
•Process
•Project

Committee

Download the Committee template to bulk upload committees to Axon. You can choose to upload a new committee or update an existing committee.

Upload New Items

The following table describes the fields of the Committee template that you can use to upload new items:

Field	Type	Description
Reference	Optional	Reference identifier for the committee. If you leave this field empty, Axon automatically assigns a new reference identifier.
Committee Name	Required	Name of the committee. Enter a name that other Axon users can recognize easily.
Description	Required	Description of the committee.
Parent Committee Name	Optional	Parent name of the committee that you want to create.
Parent Ref.	Optional	A unique reference identifier for the parent committee.
Axon Viewing	Optional	Whether the committee is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Classification	Required	Classification of the committee. You can classify the committee as Core Governance Entity.
Axon Status	Optional	Status of the committee in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the committee in the production lifecycle. Select one of the following stages: - In Effect - Obsolete
Committee Type	Required	Type of the committee. Select one of the following types: - Committee - Working Group
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. Select Committee Chair.
Segment	Optional	The segment to which you want to assign the committee to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Committee template that you can use to update existing items:

Field	Type	Description
Committee ID	Optional	ID for the committee.
Reference	Optional	Reference identifier for the committee. If you leave this field empty, Axon automatically assigns a new reference identifier.
Committee Name	Required	Name of the committee. Enter a name that other Axon users can recognize easily.
Description	Required	Description of the committee.
Parent Committee Name	Optional	Parent name of the committee that you want to create.
Parent Ref.	Optional	A unique reference identifier for the parent committee.
Axon Viewing	Optional	Whether the committee is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Classification	Required	Classification of the committee. You can classify the committee as Core Governance Entity.
Axon Status	Optional	Status of the committee in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the committee in the production lifecycle. Select one of the following stages: - In Effect - Obsolete
Committee Type	Required	Type of the committee. Select one of the following types: - Committee - Working Group

Policy

Download the Policy template to bulk upload policies to Axon. You can choose to upload a new policy or update an existing policy.

Upload New Items

The following table describes the fields of the Policy template that you can use to upload new items:

Field	Type	Description
Policy Name	Required	Name of the policy. Enter a name that other Axon users can recognize easily.
Reference	Optional	Reference identifier for the policy. If you leave this field empty, Axon assigns a new reference automatically.
Internal	Required	Indicates whether the policy is internal or external.
URL	Optional	Link to another page where the policy is mentioned in detail. Include the network protocol in the link. For example, enter https://www.website.com.
Definition	Required	Definition of the policy.
Effective Date	Optional	The date from which the policy is effective. The effective date must be in the DD/MM/YYYY format.
End Date	Optional	The date after which the policy ceases to be effective. The end date must be in the DD/MM/YYYY format.
Parent Policy Name	Optional	Name of the parent policy if the policy belongs to a hierarchy.
Parent Ref.	Optional	A unique reference identifier for the parent policy.
Axon Viewing	Optional	Whether the policy is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the policy in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Policy Lifecycle	Required	Stage of the policy in the approval lifecycle. You can select the following default stages: - Draft - Enforced - Obsolete You can also create policy lifecycle stages.
Policy Type	Required	Category that best describes the policy. You can select the following default policy types: - Conduct Standards - Data Standards You can also create policy types.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - Policy Owner - Policy Steward
Segment	Optional	The segment to which you want to assign the policy to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Policy template that you can use to update existing items:

Field	Type	Description
Policy ID	Optional	ID for the policy.
Policy Name	Required	Name of the policy. Enter a name that other Axon users can recognize easily.
Reference	Optional	Reference identifier for the policy. If you leave this field empty, Axon assigns a new reference automatically.
Internal	Required	Indicates whether the policy is internal or external.
URL	Optional	Link to another page where the policy is mentioned in detail. Include the network protocol in the link. For example, enter https://www.website.com.
Definition	Required	Definition of the policy.
Effective Date	Optional	The date from which the policy is effective. The effective date must be in the DD/MM/YYYY format.
End Date	Optional	The date after which the policy ceases to be effective. The end date must be in the DD/MM/YYYY format.
Parent Policy Name	Optional	Name of the parent policy if the policy belongs to a hierarchy.
Parent Ref.	Optional	A unique reference identifier for the parent policy.
Axon Viewing	Optional	Whether the policy is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the policy in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Policy Lifecycle	Required	Stage of the policy in the approval lifecycle. You can select the following default stages: - Draft - Enforced - Obsolete You can also create policy lifecycle stages.
Policy Type	Required	Category that best describes the policy. You can select the following default policy types: - Conduct Standards - Data Standards You can also create policy types.

Process

Download the Process template to bulk upload processes to Axon. You can choose to upload a new process or update an existing process.

Upload New Items

The following table describes the fields of the Process template that you can use to upload new items:

Field	Type	Description
Process Name	Required	Name of the process.
Reference	Optional	Reference identifier for the process. If you leave this field empty, Axon assigns a new reference automatically.
Description	Required	Description of the process.
Input Description	Optional	Description of relevant inputs to the process.
Output Description	Optional	Description of relevant outputs from the process.
Step Type	Required	Specify whether you are creating the starting step of a process, the ending step of a process, or a common step across the process.
Create Permission	Optional	Permission to create a process. (*)
Read Permission	Optional	Permission to read a process. (*)
Update Permission	Optional	Permission to update a process. (*)
Delete Permission	Optional	Permission to delete a process. (*)
Archive Permission	Optional	Permission to archive a process. (*)
Process Duration	Optional	The time duration for the process that you create.
Parent Process Name	Optional	Parent of the process.
Parent Ref.	Optional	A unique reference identifier for the parent process.
Axon Viewing	Optional	Whether the process is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the process in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Process Type	Required	The type of process that you create. You can select the following process types: - Process - Step - Control You can also add other process types.
Duration Type	Optional	The unit of time duration for the process that you create. Choose hours or days as the unit of time.
Lifecycle	Required	Stage of the process in the approval lifecycle. You can select the following default stages: - In Production - Draft - Obsolete You can also create process lifecycle stages.
Classification	Optional	Classification of the process. You can select the Execution Process, or create other processes.
Automation	Optional	Level of automation. - Manual. The process requires human intervention at every stage of the workflow. - Partially Automated. The process requires human intervention at some, but not all, stages of the workflow. - Fully Automated. The process requires no human intervention at any stage of the workflow. You can also add other automation options.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - Process Owner - Process Steward
Segment	Optional	The segment to which you want to assign the process to. This column appears if a SuperAdmin user has created segments in the Admin Panel.
(*) You need to select the values if you want to map the template column to an Axon field. If you map an empty column to the Axon field, Axon does not assign the default values and the bulk upload fails. If you remove the field mapping for the empty column, Axon assigns the default values for the column.

Update Existing Items

The following table describes the fields of the Process template that you can use to update existing items:

Field	Type	Description
Process ID	Optional	ID of the process.
Process Name	Required	Name of the process.
Reference	Optional	Reference identifier for the process. If you leave this field empty, Axon assigns a new reference automatically.
Description	Required	Description of the process.
Input Description	Optional	Description of relevant inputs to the process.
Output Description	Optional	Description of relevant outputs from the process.
Step Type	Required	Specify whether you are creating the starting step of a process, the ending step of a process, or a common step across the process.
Create Permission	Optional	Permission to create a process. (*)
Read Permission	Optional	Permission to read a process. (*)
Update Permission	Optional	Permission to update a process. (*)
Delete Permission	Optional	Permission to delete a process. (*)
Archive Permission	Optional	Permission to archive a process. (*)
Process Duration	Optional	The time duration for the process that you create.
Parent Process Name	Optional	Parent of the process.
Parent Ref.	Optional	A unique reference identifier for the parent process.
Axon Viewing	Optional	Whether the process is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the process in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Process Type	Required	The type of process that you create. You can select the following process types: - Process - Step - Control You can also add other process types.
Duration Type	Optional	The unit of time duration for the process that you create. Choose hours or days as the unit of time.
Lifecycle	Required	Stage of the process in the approval lifecycle. You can select the following default stages: - In Production - Draft - Obsolete You can also create process lifecycle stages.
Classification	Optional	Classification of the process. You can select the Execution Process, or create other processes.
Automation	Optional	Level of automation. - Manual. The process requires human intervention at every stage of the workflow. - Partially Automated. The process requires human intervention at some, but not all, stages of the workflow. - Fully Automated. The process requires no human intervention at any stage of the workflow. You can also add other automation options.
(*) You need to select the values if you want to map the template column to an Axon field. If you map an empty column to the Axon field, Axon does not assign the default values and the bulk upload fails. If you remove the field mapping for the empty column, Axon assigns the default values for the column.

Project

Download the Project template to bulk upload projects to Axon. You can choose to upload a new project or update an existing project.

Upload New Items

The following table describes the fields of the Project template that you can use to upload new items:

Field	Type	Description
Reference	Optional	Reference identifier for the project. If you leave this field empty, Axon assigns a new reference automatically.
Project Name	Required	Name of the project. Enter a name that other Axon users can recognize easily.
Project Description	Required	Description of the project.
Start Date	Required	Start date of the project. The start date must be in the DD/MM/YYYY format.
End Date	Required	End date of the project. The end date must be in the DD/MM/YYYY format.
Parent Project Name	Optional	Parent of the project that you create.
Parent Ref.	Optional	A unique reference identifier for the parent project.
Axon Viewing	Optional	Whether the project is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
RAG	Required	Status of the project in the project management lifecycle. Select Red, Amber, or Green.
Classification	Optional	Classification of the project. You can select from the following classification options: - Mandatory - Discretionary You can also create other classification options.
Axon Status	Optional	Status of the project in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Project Lifecycle	Required	Stage of the project in the project management lifecycle. You can select the following default stages: - Initiation - Execution - Closed You can also create project lifecycle stages.
Project Type	Required	Indicates the type of the project. You can select the following default projects: - Program - Project You can also create other project types.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - Project Manager - Project Steward
Segment	Optional	The segment to which you want to assign the project to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Project template that you can use to update existing items:

Field	Type	Description
Project ID	Optional	ID for the project.
Reference	Optional	Reference identifier for the project. If you leave this field empty, Axon assigns a new reference automatically.
Project Name	Required	Name of the project. Enter a name that other Axon users can recognize easily.
Project Description	Required	Description of the project.
Start Date	Required	Start date of the project. The start date must be in the DD/MM/YYYY format.
End Date	Required	End date of the project. The end date must be in the DD/MM/YYYY format.
Parent Project Name	Optional	Parent of the project that you create.
Parent Ref.	Optional	A unique reference identifier for the parent project.
Axon Viewing	Optional	Whether the project is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
RAG	Required	Status of the project in the project management lifecycle. Select Red, Amber, or Green.
Classification	Optional	Classification of the project. You can select from the following classification options: - Mandatory - Discretionary You can also create other classification options.
Axon Status	Optional	Status of the project in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Project Lifecycle	Required	Stage of the project in the project management lifecycle. You can select the following default stages: - Initiation - Execution - Closed You can also create project lifecycle stages.
Project Type	Required	Indicates the type of the project. You can select the following default projects: - Program - Project You can also create other project types.

Organizational Object Templates

Use Organizational object templates to explain the different functions of an organization. Download templates for Organizational objects from Axon to perform a bulk upload.

You can bulk upload the following types of objects:

•Business Area
•Client
•Capability
•Legal Entity
•Product
•People
•Org Unit

Business Area

Download the Business Area template to bulk upload business area data to Axon. You can choose to upload a new business area object or update an existing business area object.

Upload New Items

The following table describes the fields of the Business Area template that you can use to upload new items:

Field	Type	Description
Business Area Name	Required	Name of the business area.
Description	Required	Description of the business area.
Parent Business Area	Optional	Parent name of the business area if the business area belongs to a hierarchy.
Axon Viewing	Optional	Whether the business area is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the business area in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the business area in the governance lifecycle. You can select the following default stages: - Operating - Obsolete You can also create the lifecycle stages.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the Business Area Head role.
Segment	Optional	The segment to which you want to assign the business area to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Business Area template that you can use to update existing items:

Field	Type	Description
Business Area ID	Optional	ID of the business area.
Business Area Name	Required	Name of the business area.
Description	Required	Description of the business area.
Parent Business Area	Optional	Parent name of the business area if the business area belongs to a hierarchy.
Axon Viewing	Optional	Whether the business area is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the business area in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the business area in the governance lifecycle. You can select the following default stages: - Operating - Obsolete You can also create the lifecycle stages.

Capability

Download the Capability template to bulk upload capabilities to Axon. You can choose to upload a new capability or update an existing capability.

Upload New Items

The following table describes the fields of the Capability template that you can use to upload new items:

Field	Type	Description
Reference	Optional	A unique identifier for the capability.
Capability Name	Required	Name of the capability.
Capability Definition	Required	Description of the capability.
Parent Capability	Optional	Name of the parent capability if the capability belongs to a hierarchy.
Parent Ref.	Optional	A unique reference identifier for the parent capability.
Axon Viewing	Optional	Whether the capability is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Classification	Required	Classification of the capability that best describes its purpose. You can classify the capability as Organizational Capability. You can also create classification types.
Axon Status	Optional	Status of the capability in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the capability in the approval lifecycle. You can select one of the following default stages: - In Effect - Obsolete You can also create lifecycle stages.
Capability Type	Required	Type of capability that best describes the object. Specify whether the object is a capability or responsibility.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the Capability Owner role.
Segment	Optional	The segment to which you want to assign the capability to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Capability template that you can use to update existing items:

Field	Type	Description
Capability ID	Optional	ID of the capability.
Reference	Optional	A unique identifier for the capability.
Capability Name	Required	Name of the capability.
Capability Definition	Required	Description of the capability.
Parent Capability	Optional	Name of the parent capability if the capability belongs to a hierarchy.
Parent Ref.	Optional	A unique reference identifier for the parent capability.
Axon Viewing	Optional	Whether the capability is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Classification	Required	Classification of the capability that best describes its purpose. You can classify the capability as Organizational Capability. You can also create classification types.
Axon Status	Optional	Status of the capability in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the capability in the approval lifecycle. You can select one of the following default stages: - In Effect - Obsolete You can also create lifecycle stages.
Capability Type	Required	Type of capability that best describes the object. Specify whether the object is a capability or responsibility.

Client

Download the Client template to bulk upload client objects to Axon. You can choose to upload a new client object or update an existing client object.

Upload New Items

The following table describes the fields of the Client template that you can use to upload new items:

Field	Type	Description
Client Name	Required	Short name of the client. Enter a name that other Axon users can recognize easily.
Long Name	Optional	Full name of the client.
Description	Required	Description of the client.
Parent Client Name	Optional	Parent name of the client that you want to create.
Lifecycle	Required	Stage of the client in the production lifecycle. You can select the following stages: - In Production - Obsolete
Axon Status	Optional	Status of the client in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Axon Viewing	Optional	Whether the client is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. Select Client Segmentation Owner.
Segment	Optional	The segment to which you want to assign the client to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Client template that you can use to update existing items:

Field	Type	Description
Client ID	Optional	ID for the client.
Client Name	Required	Short name of the client. Enter a name that other Axon users can recognize easily.
Long Name	Optional	Full name of the client.
Description	Required	Description of the client.
Parent Client Name	Optional	Parent name of the client that you want to create.
Lifecycle	Required	Stage of the client in the production lifecycle. You can select the following stages: - In Production - Obsolete
Axon Status	Optional	Status of the client in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Axon Viewing	Optional	Whether the client is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.

Legal Entity

Download the Legal Entity template to bulk upload legal entity data to Axon. You can choose to upload a new legal entity object or update an existing legal entity object.

Upload New Items

The following table describes the fields of the Legal Entity template that you can use to upload new items:

Field	Type	Description
Short Name	Required	Short name of the legal entity. Enter a name that other Axon users can recognize easily.
Long Name	Required	Full name of the legal entity.
Description	Optional	Description of the legal entity.
Parent Short Name	Optional	Short name of the parent of the legal entity.
Axon Status	Optional	Status of the legal entity in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Axon Viewing	Optional	Whether the legal entity is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the Legal Entity Owner role.
Segment	Optional	The segment to which you want to assign the legal entity to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Legal Entity template that you can use to update existing items:

Field	Type	Description
Legal ID	Optional	ID of the legal entity.
Short Name	Required	Short name of the legal entity. Enter a name that other Axon users can recognize easily.
Long Name	Required	Full name of the legal entity.
Description	Optional	Description of the legal entity.
Parent Short Name	Optional	Short name of the parent of the legal entity.
Axon Status	Optional	Status of the legal entity in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Axon Viewing	Optional	Whether the legal entity is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.

Org Unit

Download the Org Unit template to bulk upload organizational units to Axon. You can choose to upload a organizational unit or update an organizational unit.

Upload New Items

The following table describes the fields of the Org Unit template that you can use to upload new items:

Field	Type	Description
Org Unit Name	Required	Name of the local department, team, or unit.
Description	Optional	Relevant description about the organizational unit.
Reference	Required	Reference identifier for the organizational unit. The reference ID must be a string data type. If you enter a number, you must format the column to Text type. Otherwise, Microsoft Excel alters the reference ID by deleting trailing zeros.
Parent Org Unit Reference	Optional	Parent of the organizational unit if the organization belongs to a hierarchy. The parent record must exist in Axon.
Axon Status	Optional	The status of the org unit. You can select the following default values: - Active - Inactive - Pending - Review - Obsolete - Deleted You can customize the values if required.

Update Existing Items

The following table describes the fields of the Org Unit template that you can use to update existing items:

Field	Type	Description
Org Unit ID	Optional	ID of the organizational unit.
Org Unit Name	Required	Name of the local department, team, or unit.
Description	Optional	Relevant description about the organizational unit.
Reference	Required	Reference identifier for the organizational unit. The reference ID must be a string data type. If you enter a number, you must format the column to Text type. Otherwise, Microsoft Excel alters the reference ID by deleting trailing zeros.
Parent Org Unit Reference	Optional	Parent of the organizational unit if the organization belongs to a hierarchy. The parent record must exist in Axon.
Axon Status	Optional	The status of the org unit. You can select the following default values: - Active - Inactive - Pending - Review - Obsolete - Deleted You can customize the values if required.

People

Download the People template to bulk upload people data to Axon. Before you can create People objects, you must create the necessary Org Unit objects.

Upload New Items

The following table describes the fields of the People template that you can use to upload new items:

Field	Type	Description
First Name	Required	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
Last Name	Required	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
Function	Optional	Job title or role of the user.
Function Description	Optional	Job description of the role of the user.
Description	Optional	Description about the user.
Email	Required	Email address of the user. Must be unique. Axon sends emails to this address.
Password	Optional	A password to provide access to the user. The user can change the password later. Not required if you enable Single Sign-On authentication. The password must be at least eight characters long and contain at least one lowercase character, one uppercase character, one numeric digit, and one special character.
Axon Status	Optional	The status of the user in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Org Unit Reference	Optional	The reference identifier of the organizational unit that the user is associated with. Ensure that you enter a value in the Org Unit Reference or Org Unit Name column though both the columns are optional.
Org Unit Name	Optional	The name of the organizational unit that the user is associated with. Ensure that you enter a value in the Org Unit Reference or Org Unit Name column though both the columns are optional.
Profile	Required	A user profile that controls the tasks that the user can perform and the objects that the user can view. Select one of the following user profiles: - WebUser - Admin - SuperAdmin
Office Location	Optional	Office location of the user.
Internal Mail Code	Optional	Internal office mail code of the user.
Office Telephone	Optional	Office phone number of the user.
Mobile/Cell	Optional	Mobile phone number of the user.
LAN ID	Optional	Network ID of the user. 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.
Employment Type	Required	The type of employment of the user. Specify whether the employment of the user is external or internal.
Lifecycle	Required	The status of the employment of the user. You can select one of the following default statuses: - Working - Temporarily Inactive - Pending Deactivation - Left the Company You can also create statuses.

Update Existing Items

The following table describes the fields of the People template that you can use to update existing items:

Field	Type	Description
People ID	Optional	ID of the user.
First Name	Required	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
Last Name	Required	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
Function	Optional	Job title or role of the user.
Function Description	Optional	Job description of the role of the user.
Description	Optional	Description about the user.
Email	Required	Email address of the user. Must be unique. Axon sends emails to this address.
Password	Optional	A password to provide access to the user. The user can change the password later. Not required if you enable Single Sign-On authentication. The password must be at least eight characters long and contain at least one lowercase character, one uppercase character, one numeric digit, and one special character.
Axon Status	Optional	The status of the user in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Org Unit Reference	Optional	The reference identifier of the organizational unit that the user is associated with.
Org Unit Name	Optional	The name of the organizational unit that the user is associated with.
Profile	Required	A user profile that controls the tasks that the user can perform and the objects that the user can view. Select one of the following user profiles: - WebUser - Admin - SuperAdmin
Office Location	Optional	Office location of the user.
Internal Mail Code	Optional	Internal office mail code of the user.
Office Telephone	Optional	Office phone number of the user.
Mobile/Cell	Optional	Mobile phone number of the user.
LAN ID	Optional	Network ID of the user. 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.
Employment Type	Required	The type of employment of the user. Specify whether the employment of the user is external or internal.
Lifecycle	Required	The status of the employment of the user. You can select one of the following default statuses: - Working - Temporarily Inactive - Pending Deactivation - Left the Company You can also create statuses.

Product

Download the Product template to bulk upload products to Axon. You can choose to upload a new product or update an existing product.

Upload New Items

The following table describes the fields of the Product template that you can use to upload new items:

Field	Type	Description
Reference	Optional	A unique reference identifier for the product.
Product Name	Required	Short name of the product. Enter a name that other Axon users can recognize easily.
Long Name	Optional	Full name of the product.
Product Description	Required	Description of the product.
Parent Product	Optional	Short name of the parent product if the product belongs to a hierarchy.
Lifecycle	Required	Stage of the product in the governance lifecycle. Select one of the following default stages: - In Production - Obsolete You can also create lifecycle stages.
Axon Status	Optional	Status of the product in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Axon Viewing	Optional	Whether the product is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - Product Owner - Product Steward
Segment	Optional	The segment to which you want to assign the product to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Product template that you can use to update existing items:

Field	Type	Description
Product ID	Optional	ID of the product.
Reference	Optional	A unique reference identifier for the product.
Product Name	Required	Short name of the product. Enter a name that other Axon users can recognize easily.
Long Name	Optional	Full name of the product.
Product Description	Required	Description of the product.
Parent Product	Optional	Short name of the parent product if the product belongs to a hierarchy.
Lifecycle	Required	Stage of the product in the governance lifecycle. Select one of the following default stages: - In Production - Obsolete You can also create lifecycle stages.
Axon Status	Optional	Status of the product in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Axon Viewing	Optional	Whether the product is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.

Regulatory Object Templates

Use Regulatory object templates to describe the regulations that you employ in an organization and the geographical areas to which the regulation applies. Download templates for Regulatory objects from Axon to perform a bulk upload.

You can bulk upload the following types of objects:

•Geography
•Regulation
•Regulator
•Regulatory Theme

Geography

Download the Geography template to bulk upload geographical regions to Axon. You can choose to upload a new geography or update an existing geography.

Upload New Items

The following table describes the fields of the Geography template that you can use to upload new items:

Field	Type	Description
Geography Name	Required	Name of the geographical region or country in which you want to enforce a regulation.
Geography Definition	Optional	Description of the geographical region.
Parent Geography Name	Optional	Name of the parent geographical region. You can select US or EU.
Segment	Optional	The segment to which you want to assign the geography to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Geography template that you can use to update existing items:

Field	Type	Description
Geography ID	Optional	ID for the geographical region.
Geography Name	Required	Name of the geographical region or country in which you want to enforce a regulation.
Geography Definition	Optional	Description of the geographical region.
Parent Geography Name	Optional	Name of the parent geographical region. You can select US or EU.

Regulation

Download the Regulation template to bulk upload regulations to Axon. You can choose to upload a new regulation or update an existing regulation.

Upload New Items

The following table describes the fields of the Regulation template that you can use to upload new items:

Field	Type	Description
Reference	Required	Reference identifier for the regulation.
Short Name	Optional	Short name of the regulation. The most commonly used name or an acronym for the regulation, such as GDPR. Enter a name that users can recognize easily.
Regulation Long Name	Required	Full name of the regulation. For example, General Data Protection Regulation.
Description	Required	Description of the regulation.
Additional Info	Optional	Any additional information that provides more context to the regulation.
Publication Date	Required	The date of the original publication of the regulation.
Comments Date	Optional	The date by when you want the stakeholders of an organization to provide comments or opinions on the draft regulation.
Finalization Date	Optional	The date by when you want the stakeholders to submit comments and finalize the regulation.
Compliance Date	Required	The date by when you want to enforce the regulation. For example, 25th May 2018 for GDPR.
Legal Advice	Optional	A description of the legal advice.
Parent Regulation Name	Optional	Long name of the parent regulation.
Parent Ref.	Optional	A unique reference identifier for the parent regulation.
Regulation Maturity	Required	The level of maturity in understanding and interpreting the regulation. Select one of the following maturity stages: - Initial Draft - Open for Comments - Comments Incorporated - Finalizing - Finalized
Regulation Probability	Required	The extent to which a regulation is probable. Select Confirmed.
Axon Status	Optional	Status of the regulation in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Legal Advice Type	Optional	The type of legal advice. Select one of the following legal advice types: - Comment - Guideline - Legal Requirement
Regulation Stage	Required	The stage of the organization when a regulation is created or updated. Select one of the following stages: - Interpretation - Impact Assessment - Completed
Compliance Level	Required	The current state of the response of the organization to the regulation. Select one of the following compliance levels: - Unknown - Fully Compliant - Compliant with Exceptions - Materially Not Compliant
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. Select one of the following roles: - Regulation Owner - Regulation SME
Segment	Optional	The segment to which you want to assign the regulation to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Regulation template that you can use to update existing items:

Field	Type	Description
Regulation ID	Optional	ID for the regulation.
Reference	Required	Reference identifier for the regulation.
Short Name	Optional	Short name of the regulation. The most commonly used name or an acronym for the regulation, such as GDPR. Enter a name that users can recognize easily.
Regulation Long Name	Required	Full name of the regulation. For example, General Data Protection Regulation.
Description	Required	Description of the regulation.
Additional Info	Optional	Any additional information that provides more context to the regulation.
Publication Date	Required	The date of the original publication of the regulation.
Comments Date	Optional	The date by when you want the stakeholders of an organization to provide comments or opinions on the draft regulation.
Finalization Date	Optional	The date by when you want the stakeholders to submit comments and finalize the regulation.
Compliance Date	Required	The date by when you want to enforce the regulation. For example, 25th May 2018 for GDPR.
Legal Advice	Optional	A description of the legal advice.
Parent Regulation Name	Optional	Long name of the parent regulation.
Parent Ref.	Optional	A unique reference identifier for the parent regulation.
Regulation Maturity	Required	The level of maturity in understanding and interpreting the regulation. Select one of the following maturity stages: - Initial Draft - Open for Comments - Comments Incorporated - Finalizing - Finalized
Regulation Probability	Required	The extent to which a regulation is probable. Select Confirmed.
Axon Status	Optional	Status of the regulation in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Legal Advice Type	Optional	The type of legal advice. Select one of the following legal advice types: - Comment - Guideline - Legal Requirement
Regulation Stage	Required	The stage of the organization when a regulation is created or updated. Select one of the following stages: - Interpretation - Impact Assessment - Completed
Compliance Level	Required	The current state of the response of the organization to the regulation. Select one of the following compliance levels: - Unknown - Fully Compliant - Compliant with Exceptions - Materially Not Compliant

Regulator

Download the Regulator template to bulk upload regulator objects to Axon. You can choose to upload a new regulator object or update an existing regulator object.

Upload New Items

The following table describes the fields of the Regulator template that you can use to upload new items:

Field	Type	Description
Regulator Name	Required	Full name of the regulator.
Short Name	Required	Short name of the regulator. The most commonly used name or an acronym for the regulator. Enter a name that users can recognize easily.
Description	Optional	Description of the regulator.
Segment	Optional	The segment to which you want to assign the regulator to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Regulator template that you can use to update existing items:

Field	Type	Description
Regulator ID	Optional	ID for the regulator.
Regulator Name	Required	Full name of the regulator.
Short Name	Required	Short name of the regulator. The most commonly used name or an acronym for the regulator. Enter a name that users can recognize easily.
Description	Optional	Description of the regulator.

Regulatory Theme

Download the Regulatory Theme template to bulk upload regulatory themes to Axon. You can choose to upload a new regulatory theme or update an existing regulatory theme.

Upload New Items

The following table describes the fields of the Regulatory Theme template that you can use to upload new items:

Field	Type	Description
Reference	Required	Reference identifier for the regulatory theme. You can enter a reference identifier to provide content and uniquely identify the regulatory theme. If you leave this field empty, Axon assigns a new reference automatically.
Short Name	Optional	Short name of the regulatory theme. The most commonly used name or an acronym for the regulatory theme. Enter a name that users can recognize easily.
Regulatory Theme Long Name	Required	Full name of the regulatory theme.
Description	Required	Description of the regulatory theme.
Parent Regulatory Theme Name	Optional	Long name of the parent regulatory theme.
Parent Ref.	Optional	A unique reference identifier for the parent regulatory theme.
Axon Status	Optional	Status of the regulatory theme in Axon. Select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Segment	Optional	The segment to which you want to assign the regulatory theme to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Regulatory Theme template that you can use to update existing items:

Field	Type	Description
Regulatory Theme ID	Optional	ID for the regulatory theme. When you create an object, Axon automatically generates an ID for the object.
Reference	Required	Reference identifier for the regulatory theme. You can enter a reference identifier to provide content and uniquely identify the regulatory theme. If you leave this field empty, Axon assigns a new reference automatically.
Short Name	Optional	Short name of the regulatory theme. The most commonly used name or an acronym for the regulatory theme. Enter a name that users can recognize easily.
Regulatory Theme Long Name	Required	Full name of the regulatory theme.
Description	Required	Description of the regulatory theme.
Parent Regulatory Theme Name	Optional	Long name of the parent regulatory theme.
Parent Ref.	Optional	A unique reference identifier for the parent regulatory theme.
Axon Status	Optional	Status of the regulatory theme in Axon. Select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted

Data & Technology Object Templates

The Data & Technology Object templates contain the main Axon components that identify the systems and data present in an organization and how the systems relate to each other. You can use the data quality objects to control and measure the quality of customer data. Download templates for Data and Technology objects from Axon to perform a bulk upload.

You can bulk upload the following types of objects:

•Attribute
•Data Quality Report
•Data Quality Rule
•Data Set
•Glossary
•Interface
•System

Attribute

Download the Attribute template to bulk upload attributes to Axon. You can choose to upload a new attribute or update an existing attribute.

Upload New Items

The following table describes the fields of the Attribute template that you can use to upload new items:

Field	Type	Description
Reference Number	Optional	The unique reference ID of the attribute. If the Reference Number column is empty, you need to remove the column mapping to the Reference Number field when you perform a bulk upload. Alternatively, you can choose to delete the Reference Number column from the template before you perform a bulk upload.
Attribute Name	Required	Name of the attribute as known in the business.
Attribute Definition	Required	Definition of the attribute.
DB Format	Optional	The format of the attribute that is expressed in the following format: <data_type>(<data_length>) For example, to specify that the attribute is of the date data type that is 10 characters long, enter the following: DATE(10) Note: This field is required if you provide a value list for a data set.
Key	Optional	Indicates whether the attribute is a primary key.
Business Logic	Optional	Describes the relevant business logic for the attribute.
Attribute Requirement	Optional	Indicates if the field is mandatory, optional or conditional when a new row is created.
Attribute Data Set Ref.	Optional	A unique reference identifier of the data set that contains the attribute.
Attribute Data Set Name	Optional	Name of the data set that contains the attribute.
Attribute System	Optional	Short name of the system that contains the data set and the attribute.
Glossary Ref.	Optional	A unique reference identifier of the glossary that captures the attribute name.
Glossary Name	Optional	Name of the glossary that captures the attribute name.
Parent Glossary Name	Optional	Parent of the glossary that captures the attribute in the glossary hierarchy. The parent glossary term must exist in Axon.
Origin	Optional	The origin of the attribute. You can select one of the following types: Created/Set Here, Sourced, Unknown, or Enterprise Catalog.
Editability	Optional	Describes whether you can edit the attribute. You can select from the following editability options: - Read Only - Editable - Unknown You can also create other editability options.
Editability Role	Optional	The role of the user who can edit the attribute. You can select from the following editability roles: - Admin Only - Restricted User Groups - Most Users You can also create other editability roles.
DB Field Name	Optional	The name of the field in the database that stores the data. Can be an encoded string. For example, database.table.fieldname.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - Data Attribute Owner - Data Attribute Steward

Update Existing Items

The following table describes the fields of the Attribute template that you can use to update existing items:

Field	Type	Description
Attribute ID	Optional	ID of the attribute.
Reference Number	Optional	The unique reference ID of the attribute. If the Reference Number column is empty, you need to remove the column mapping to the Reference Number field when you perform a bulk upload. Or, you can choose to delete the Reference Number column from the template before you perform a bulk upload.
Attribute Name	Required	Name of the attribute as known in the business.
Attribute Definition	Required	Definition of the attribute.
DB Format	Optional	The format of the attribute that is expressed in the following format: <data_type>(<data_length>) For example, to specify that the attribute is of the date data type that is 10 characters long, enter the following: DATE(10) Note: This field is required if you provide a value list for a data set.
Key	Optional	Indicates whether the attribute is a primary key.
Business Logic	Optional	Describes the relevant business logic for the attribute.
Attribute Requirement	Optional	Indicates if the field is mandatory, optional or conditional when a new row is created.
Attribute Data Set Ref.	Optional	A unique reference identifier of the data set that contains the attribute.
Attribute Data Set Name	Optional	Name of the data set that contains the attribute.
Attribute System	Optional	Short name of the system that contains the data set and the attribute.
Glossary Ref.	Optional	A unique reference identifier of the glossary that captures the attribute name.
Glossary Name	Optional	Name of the glossary that captures the attribute name.
Parent Glossary Name	Optional	Parent of the glossary that captures the attribute in the glossary hierarchy. The parent glossary term must exist in Axon.
Origin	Optional	The origin of the attribute. You can select one of the following types: Created/Set Here, Sourced, Unknown, or Enterprise Catalog.
Editability	Optional	Describes whether you can edit the attribute. You can select from the following editability options: - Read Only - Editable - Unknown You can also create other editability options.
Editability Role	Optional	The role of the user who can edit the attribute. You can select from the following editability roles: - Admin Only - Restricted User Groups - Most Users You can also create other editability roles.

Data Quality Report

Download the Data Quality Report template to bulk upload data quality reports to Axon. You can choose to upload a new Data Quality report or update an existing Data Quality report.

Upload New Items

The following table describes the fields of the Data Quality Report template that you can use to upload new items:

Field	Type	Description
Report Date	Required	The date when the evaluation of the data was performed in the Data Quality system. The date of the Data Quality report must be in the DD/MM/YYYY format. Do not enter the date when the reports are uploaded to Axon. You can upload multiple reports for the same item and multiple items at the same time.
Data Quality Result	Required	The score, expressed as a number between 0 and 100, of items that meet the expectations of the quality rule. Axon displays this number as a percentage. Do not use a % sign when entering data. You can enter scores expressed with decimal places. Most Axon screens round off the score with a decimal value.
Data Quality Report URL	Optional	Link to the full report generated by the Data Quality system.
Exception Count	Optional	The number of records that did not meet standards based on some Data Quality system reports. Specify the exception information.
Volume	Optional	Number of observations in the report.
Data Quality Rule Reference	Required	The unique reference number of the local data quality rule.

Update Existing Items

The following table describes the fields of the Data Quality Report template that you can use to update existing items:

Field	Type	Description
Data Quality Report ID	Optional	ID of the Data Quality report.
Report Date	Required	The date when the evaluation of the data was performed in the Data Quality system. The date of the Data Quality report must be in the DD/MM/YYYY format. Do not enter the date when the reports are uploaded to Axon. You can upload multiple reports for the same item and multiple items at the same time.
Data Quality Result	Required	The score, expressed as a number between 0 and 100, of items that meet the expectations of the quality rule. Axon displays this number as a percentage. Do not use a % sign when entering data. You can enter scores expressed with decimal places. Most Axon screens round off the score with a decimal value.
Data Quality Report URL	Optional	Link to the full report generated by the Data Quality system.
Exception Count	Optional	The number of records that did not meet standards based on some Data Quality system reports. Specify the exception information.
Volume	Optional	Number of observations in the report.
Data Quality Rule Reference	Required	The unique reference number of the local data quality rule.

Data Quality Rule

Download the Data Quality Rule template to bulk upload standard or local data quality rules to Axon. You can upload new items for a data quality rule object. When you bulk upload data quality rules, a template must contain either Standard or Local data quality rules.

Upload New Items

The following table describes the fields of the Data Quality Rule template that you can use to upload new items:

Field	Type	Description
Rule Name	Required	Name of the rule.
Rule Description	Required	Description of the logic for the rule.
Reference	Optional	A unique reference number for a data quality rule. Based on this reference number, Axon loads the scores in the Data Quality report.
Technical Description	Optional	A technical description of the rule logic. Can include SQL or pseudo SQL.
Population Description	Optional	Describes the population in scope for the rule.
Measuring Method Description	Optional	The relevant information about the measurement process.
Amber Target	Required	A number from 0 to 100 that indicates the threshold value for the amber color.
Green Target	Required	A number that indicates the threshold value for the green color. Reflects the proportion of the measured data that achieved the performance level for the green target. Enter a number from 0 to 100. Do not enter characters such as %. Decimal Points are acceptable, although results are rounded. Some Data Quality measurement systems report deviation from a perfect score rather than stating the actual score. Do not enter the deviation percentage. If 5% deviation is reported, enter "95".
Axon Viewing	Optional	Whether the data quality rule is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Measured in System	Optional	Name of the system in which the rule is measured. This is often the name of the Data Quality profiling or measurement system used for the given data set. This field is required if you choose a local data quality rule.
Rule Type	Required	The type of rule that Axon supports. You can select one of the following types: - Completeness - Accuracy - Consistency - Validity - Timeliness You can also create other rule types.
Frequency	Required	Specifies how often the rule is measured. Select one of the following values: - Daily - Weekly - Monthly - Quarterly - AdHoc - Bi-Weekly
Lifecycle	Required	Stage of the data quality rule in the approval lifecycle. You can select the following default stages: - Active - Draft - Obsolete You can also create data quality rule lifecycle stages.
Axon Status	Optional	Status of the data quality rule in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Measuring Method	Optional	Specifies how the data quality rule is evaluated. You can specify one of the following options: - System Function - Technical Script - Business Extract You can also create other measuring methods.
Criticality	Required	Level of criticality. Select from one of the following options: - Low - Medium - High
Automation Level	Optional	Specifies how automated the Data Quality measurement process is. Select one of the following options: - Fully Automated - Partially Automated - Manual - Unknown You can also create other automation levels.
Standard Data Quality Rule Reference	Optional	The reference to the standard data quality rule that is attached to a glossary term and specifies how to validate the data related to the glossary.
Data Quality Rule Type	Optional	The type of data quality rule. Specify whether it is a local or standard data quality rule. If you leave the field empty, Axon considers the rule as a local data quality rule.
Attribute Ref.	Optional	A unique reference identifier for the attribute that the rule measures. Ensure that you enter a value in the Attribute Ref. or Attribute Name column though both the columns are optional.
Attribute Name	Optional	Name of the attribute that the rule measures. Ensure that you enter a value in the Attribute Ref. or Attribute Name column though both the columns are optional.
Attribute Data Set Name	Optional	Name of the data set that contains the attribute.
Attribute Data Set System Name	Optional	Short name of the system that contains the data set and the attribute.
Glossary Ref.	Optional	A unique reference identifier for the glossary that is associated with the standard data quality rule. If you choose a standard data quality rule type, ensure that you enter a value in the Glossary Ref. or Glossary Name column.
Glossary Name	Optional	Name of the glossary that is associated with the standard data quality rule. If you choose a standard data quality rule type, ensure that you enter a value in the Glossary Ref. or Glossary Name column.
Parent Glossary Name	Optional	Parent name of the glossary that is associated with the standard data quality rule.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the DQ Steward role.

Data Set

Download the Data Set template to bulk upload data sets to Axon. You can choose to upload a new data set or update an existing data set.

Upload New Items

The following table describes the fields of the Data Set template that you can use to upload new items:

Field	Type	Description
Reference Number	Optional	The unique identifier for the data set.
Data Set Name	Required	Name of the data set as known in the business.
Data Set Definition	Required	Description of the data set.
Data Set Usage Description	Optional	Additional information about the data set.
Axon Viewing	Optional	Whether the data set is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Data Set Type	Required	Type of the data set. You can select the following data set types: - Value List - Data Set - Report Default is Data Set. You can also create other data set types.
System Name	Required	Short name of the system that contains the data set.
System Parent Name	Optional	Short name of the parent of the system that contains the data set.
Lifecycle	Required	Stage of the data set in the governance lifecycle. You can select the following default stages: - Draft - Approved - Obsolete You can also create other lifecycle stages.
Axon Status	Optional	Status of the data set in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Glossary Ref.	Optional	Reference identifier for the glossary that the data set is associated with. Ensure that you enter a value in the Glossary Ref. or Glossary Name column though both the columns are optional.
Glossary Name	Optional	The glossary that the data set is associated with. Ensure that you enter a value in the Glossary Ref. or Glossary Name column though both the columns are optional.
Parent Glossary Name	Optional	Parent of the glossary in the glossary hierarchy. The parent glossary term must exist in Axon.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles. - Data Steward - Data Owner
Segment	Optional	The segment to which you want to assign the data set to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Data Set template that you can use to update existing items:

Field	Type	Description
Data Set ID	Optional	ID of the data set.
Reference Number	Optional	The unique identifier for the data set.
Data Set Name	Required	Name of the data set as known in the business.
Data Set Definition	Required	Description of the data set.
Data Set Usage Description	Optional	Additional information about the data set.
Axon Viewing	Optional	Whether the data set is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Data Set Type	Required	Type of the data set. You can select the following data set types: - Value List - Data Set - Report Default is Data Set. You can also create other data set types.
System Name	Required	Short name of the system that contains the data set.
System Parent Name	Optional	Short name of the parent of the system that contains the data set.
Lifecycle	Required	Stage of the data set in the governance lifecycle. You can select the following default stages: - Draft - Approved - Obsolete You can also create other lifecycle stages.
Axon Status	Optional	Status of the data set in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Glossary Ref.	Optional	Reference identifier for the glossary that the data set is associated with. Ensure that you enter a value in the Glossary Ref. or Glossary Name column though both the columns are optional.
Glossary Name	Optional	The glossary that the data set is associated with. Ensure that you enter a value in the Glossary Ref. or Glossary Name column though both the columns are optional.
Parent Glossary Name	Optional	Parent of the glossary in the glossary hierarchy. The parent glossary term must exist in Axon.

Glossary

Download the Glossary template to bulk upload glossaries to Axon. You can choose to upload a new glossary or update an existing glossary.

Upload New Items

The following table describes the fields of the Glossary template that you can use to upload new items:

Field	Type	Description
Name	Required	Name of the glossary.
Definition	Required	Definition of the glossary.
Ref.	Optional	A unique reference identifier for the glossary. If you leave this field empty, Axon automatically assigns a reference identifier.
Examples	Optional	Contextual examples of the glossary.
Business Logic	Optional	Business context in which the glossary is used.
Format Description	Optional	Description of the glossary format.
LDM Reference	Optional	Place of the glossary in the Logical Data Model.
Parent Name	Optional	Parent of the glossary in the glossary hierarchy. The parent glossary term must exist in Axon.
Parent Ref.	Optional	A unique reference identifier for the parent glossary.
Axon Viewing	Optional	Whether the glossary is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the glossary in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the glossary in the approval lifecycle. You can select the following default stages: - Draft - Being validated - Approved - Obsolete You can also create lifecycle stages.
Format Type	Required	Format in which the glossary is expressed. You can select the following data types: - Text - Number - Decimal - Percentage - Fraction - Date - Time - Datetime You can also create other data types.
KDE	Optional	Indicates whether or not the glossary is a key data element. You can add new key data element values from the Admin panel in addition to the default values, True and False, as necessary.
Security Classification	Required	Security classification of the glossary. You can select the following security classification options: - Public - Internal - Confidential - Secret You can also create other security classification options.
Type	Required	The type of glossary. You can select one of the following glossary types: - Domain. A domain describes a broad category of data concepts, for example, customer domain or transaction data domain. - Subdomain. A subdomain is a division within a domain that facilitates a separation of definitions across relevant themes, for example, client or transaction. - Term. A business term corresponds to a single concept, for example, Maturity Date. - Metric. A metric is a measurement of a specific business activity that may be a combination of other glossary concepts for the measurement. If you create additional glossary types from the Admin Panel, you can see the list in this field.
Confidentiality	Optional	The Confidentiality rating from the Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Confidentiality rating indicates the ability of a glossary to show the right information to the right users who have the right credentials. Confidentiality, Integrity, and Availability are crucial elements of security for a glossary. The default Confidentiality rating ranges from 1 to 3. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a glossary that is less secure. - 2 - Indicates average security of a glossary that is moderately secure. - 3 - Indicates strong security of a glossary that is the most secure. For example, if the Confidentiality rating is 2, the glossary is moderately secure. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel.
Integrity	Optional	The Integrity rating from the Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Integrity rating indicates the ability of a glossary to ensure that the information shown to the users have not been compromised. Confidentiality, Integrity and Availability are crucial elements of security for a glossary. The default Integrity rating ranges from 1 to 3. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a glossary that is less secure. - 2 - Indicates average security of a glossary that is moderately secure. - 3 - Indicates strong security of a glossary that is the most secure. For example, if the Integrity rating is 1, the glossary is less secure. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel.
Availability	Optional	The Availability rating from the Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Availability rating indicates the ability of a glossary to show the right information to the right users at the right time. Confidentiality, Integrity and Availability are crucial elements of security for a glossary. The default Availability rating ranges from 1 to 3. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a glossary that is less secure. - 2 - Indicates average security of a glossary that is moderately secure. - 3 - Indicates strong security of a glossary that is the most secure. For example, if the Availability rating is 3, the glossary is most secure. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel.
Alias Names	Optional	Alternate name for a glossary. Use synonyms for the glossary that is commonly used in your organization. You can add multiple alias names for a glossary by adding a comma (,) as a delimiter. If you use the CSV file format to bulk upload data, you must enter the comma separated alias names in double quotes (" ".) If you want to add a comma in a single alias name, you must create or edit a glossary manually and add the alias name.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - Glossary Definition Owner - Glossary Steward
Segment	Optional	The segment to which you want to assign the glossary to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the Glossary template that you can use to update existing items:

Field	Type	Description
ID	Optional	ID of the glossary.
Name	Required	Name of the glossary.
Definition	Required	Definition of the glossary.
Ref.	Optional	A unique reference identifier for the glossary. If you leave this field empty, Axon automatically assigns a reference identifier.
Examples	Optional	Contextual examples of the glossary.
Business Logic	Optional	Business context in which the glossary is used.
Format Description	Optional	Description of the glossary format.
LDM Reference	Optional	Place of the glossary in the Logical Data Model.
Parent Name	Optional	Parent of the glossary in the glossary hierarchy. The parent glossary term must exist in Axon.
Parent Ref.	Optional	A unique reference identifier for the parent glossary.
Axon Viewing	Optional	Whether the glossary is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the glossary in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the glossary in the approval lifecycle. You can select the following default stages: - Draft - Being validated - Approved - Obsolete You can also create lifecycle stages.
Format Type	Required	Format in which the glossary is expressed. You can select the following data types: - Text - Number - Decimal - Percentage - Fraction - Date - Time - Datetime You can also create other data types.
KDE	Optional	Indicates whether or not the glossary is a key data element. You can add new key data element values from the Admin panel in addition to the default values, True and False, as necessary.
Security Classification	Required	Security classification of the glossary. You can select the following security classification options: - Public - Internal - Confidential - Secret You can also create other security classification options.
Type	Required	The type of glossary. You can select one of the following glossary types: - Domain. A domain describes a broad category of data concepts, for example, customer domain or transaction data domain. - Subdomain. A subdomain is a division within a domain that facilitates a separation of definitions across relevant themes, for example, client or transaction. - Term. A business term corresponds to a single concept, for example, Maturity Date. - Metric. A metric is a measurement of a specific business activity that may be a combination of other glossary concepts for the measurement. If you create additional glossary types from the Admin Panel, you can see the list in this field.
Confidentiality	Optional	The Confidentiality rating from the Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Confidentiality rating indicates the ability of a glossary to show the right information to the right users who have the right credentials. Confidentiality, Integrity, and Availability are crucial elements of security for a glossary. The default Confidentiality rating ranges from 1 to 3. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a glossary that is less secure. - 2 - Indicates average security of a glossary that is moderately secure. - 3 - Indicates strong security of a glossary that is the most secure. For example, if the Confidentiality rating is 2, the glossary is moderately secure. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel.
Integrity	Optional	The Integrity rating from the Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Integrity rating indicates the ability of a glossary to ensure that the information shown to the users have not been compromised. Confidentiality, Integrity and Availability are crucial elements of security for a glossary. The default Integrity rating ranges from 1 to 3. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a glossary that is less secure. - 2 - Indicates average security of a glossary that is moderately secure. - 3 - Indicates strong security of a glossary that is the most secure. For example, if the Integrity rating is 1, the glossary is less secure. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel.
Availability	Optional	The Availability rating from the Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Availability rating indicates the ability of a glossary to show the right information to the right users at the right time. Confidentiality, Integrity and Availability are crucial elements of security for a glossary. The default Availability rating ranges from 1 to 3. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a glossary that is less secure. - 2 - Indicates average security of a glossary that is moderately secure. - 3 - Indicates strong security of a glossary that is the most secure. For example, if the Availability rating is 3, the glossary is most secure. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel.
Alias Names	Optional	Alternate name for a glossary. Use synonyms for the glossary that is commonly used in your organization. You can add multiple alias names for a glossary by adding a comma (,) as a delimiter. If you use the CSV file format to bulk upload data, you must enter the comma separated alias names in double quotes (" ".) If you want to add a comma in a single alias name, you must create or edit a glossary manually and add the alias name.

Interface

Download the Interface template to bulk upload interfaces to Axon. You can choose to upload a new interface object or update an existing interface object.

Upload New Items

The following table describes the fields of the Interface template that you can use to upload new items:

Field	Type	Description
Interface Name	Required	Name of the interface.
Reference	Optional	Reference ID for the interface. The reference ID must be a string data type. If you enter a number, you must format the column to Text type. Otherwise, Microsoft Excel alters the reference ID by deleting trailing zeros.
Asset ID	Optional	A unique identifier or a serial number for a system or an interface that the IT or Property department assigns.
Synchronization Control	Optional	Description of the rules that control the synchronization of information between the two connected interfaces.
Interface Description	Required	Description of the system interface.
Transfer Method	Optional	Protocol or medium used to move information between the source and target system. You can select the following methods: - FTP - SFTP - SCP - HTTP - HTTPS - SOAP - MQSERIES - EMAIL You can also create other transfer methods.
Transfer Format	Optional	Format or file type used to flow information between the source and target system. You can select the following formats: - XML - XBRL - JSON - DELIMITED - XLS You can also create other transfer formats.
Interface Classification	Optional	Classification of the system interface that best describes its purpose. You can select the following default interfaces: - BAU - Reconciliation - Ref Data Distribution - Migration You can also create interface classifications.
Lifecycle	Required	Stage of the system interface in the production lifecycle. You can select the following default stages: - In Production - Being Decommissioned - Decommissioned You can also create lifecycle stages.
Axon Status	Optional	Status of the system interface in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Source System Name	Required	Short name of the system from which the information flows out.
Target System Name	Required	Short name of the system to which the information flows in.
Automation Level	Required	Level of automation of the interface. You can select the following the automation levels: - Manual - File based - Manual - Re-keyed - Partially Automated - Fully Automated - Unknown Default is Unknown.
Frequency	Optional	Frequency at which data flows between the source and target system. You can select the following frequencies: - Ad-Hoc - Monthly - Weekly - Daily - Realtime - Unknown You can also create other frequency options.
Axon Viewing	Optional	Whether the system interface is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles. - Interface Owner - Interface Steward

Update Existing Items

The following table describes the fields of the Interface template that you can use to update existing items:

Field	Type	Description
Interface ID	Optional	ID of the interface.
Interface Name	Required	Name of the interface.
Reference	Optional	Reference ID for the interface. The reference ID must be a string data type. If you enter a number, you must format the column to Text type. Otherwise, Microsoft Excel alters the reference ID by deleting trailing zeros.
Asset ID	Optional	A unique identifier or a serial number for a system or an interface that the IT or Property department assigns.
Synchronisation Control	Optional	Description of the rules that control the synchronization of information between the two connected interfaces.
Interface Description	Required	Description of the system interface.
Transfer Method	Optional	Protocol or medium used to move information between the source and target system. You can select the following methods: - FTP - SFTP - SCP - HTTP - HTTPS - SOAP - MQSERIES - EMAIL You can also create other transfer methods.
Transfer Format	Optional	Format or file type used to flow information between the source and target system. You can select the following formats: - XML - XBRL - JSON - DELIMITED - XLS You can also create other transfer formats.
Interface Classification	Optional	Classification of the system interface that best describes its purpose. You can select the following default interfaces: - BAU - Reconciliation - Ref Data Distribution - Migration You can also create interface classifications.
Lifecycle	Required	Stage of the system interface in the production lifecycle. You can select the following default stages: - In Production - Being Decommissioned - Decommissioned You can also create lifecycle stages.
Axon Status	Optional	Status of the system interface in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Source System Name	Required	Short name of the system from which the information flows out.
Target System Name	Required	Short name of the system to which the information flows in.
Automation Level	Required	Level of automation of the interface. You can select the following the automation levels: - Manual - File based - Manual - Re-keyed - Partially Automated - Fully Automated - Unknown Default is Unknown.
Frequency	Optional	Frequency at which data flows between the source and target system. You can select the following frequencies: - Ad-Hoc - Monthly - Weekly - Daily - Realtime - Unknown You can also create other frequency options.
Axon Viewing	Optional	Whether the system interface is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.

System

Download the System template to bulk upload systems to Axon. You can choose to upload a new system or update an existing system.

Upload New Items

The following table describes the fields of the System template that you can use to upload new items:

Field	Type	Description
System Name	Required	Short name of the system. Enter a name that other Axon users can recognize easily.
System Long Name	Optional	Full name or long name of the system.
Asset ID	Optional	A unique identifier for the system or the interface. The IT or Property department designates the Asset ID.
External	Required	A flag for systems that are not owned or controlled by the client organization from which a data feed is taken. Select True or False.
System Description	Required	Description of the system and the business purpose.
System URL	Optional	Link to another page where related information is mentioned. Include the network protocol in the link. For example, enter https://www.website.com.
Parent System Name	Optional	Short name of the parent system if the system belongs to a hierarchy.
Axon Viewing	Optional	Whether the system is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the system in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the system in the production lifecycle. You can select the following default stages: - In Production - Being Decommissioned - Decommissioned You can also create lifecycle stages.
System Type	Required	Whether the system is a software application or one of several file types. You also need to specify whether the system is hosted internally inside your organization or externally outside your organization.
System Classification	Optional	Classification of the system that best describes its function. You can select the Data Warehouse classification, or create your own classification options.
Confidentiality	Optional	The Confidentiality rating from the Confidentiality, Integrity, and Availability (CIA) rating of a system. Confidentiality rating indicates the ability of a system to show the right information to the right users who have the right credentials. Confidentiality, Integrity, and Availability are crucial elements of security for a system. The default Confidentiality rating ranges from 1 to 3. You can add a maximum of nine ratings from the Admin panel. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a system that is less secure. - 2 - Indicates average security of a system that is moderately secure. - 3 - Indicates strong security of a system that is the most secure. For example, if the Confidentiality rating is 2, the system is moderately secure.
Integrity	Optional	The Integrity rating from the Confidentiality, Integrity, and Availability (CIA) rating of a system. Integrity rating indicates the ability of a system to ensure that the information shown to the users have not been compromised. Confidentiality, Integrity and Availability are crucial elements of security for a system. The default Integrity rating ranges from 1 to 3. You can add a maximum of nine ratings from the Admin panel. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a system that is less secure. - 2 - Indicates average security of a system that is moderately secure. - 3 - Indicates strong security of a system that is the most secure. For example, if the Integrity rating is 1, the system is less secure.
Availability	Optional	The Availability rating from the Confidentiality, Integrity, and Availability (CIA) rating of a system. Availability rating indicates the ability of a system to show the right information to the right users at the right time. Confidentiality, Integrity and Availability are crucial elements of security for a system. The default Availability rating ranges from 1 to 3. You can add a maximum of nine ratings from the Admin panel. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a system that is less secure. - 2 - Indicates average security of a system that is moderately secure. - 3 - Indicates strong security of a system that is the most secure. For example, if the Availability rating is 3, the system is most secure.
User Email	Optional	Email address of the user. Must be unique. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Optional	The role of the user. You can select the following roles: - System Business Owner - System Steward
Segment	Optional	The segment to which you want to assign the system to. This column appears if a SuperAdmin user has created segments in the Admin Panel.

Update Existing Items

The following table describes the fields of the System template that you can use to update existing items:

Field	Type	Description
System ID	Optional	ID of the system.
System Name	Required	Short name of the system. Enter a name that other Axon users can recognize easily.
System Long Name	Optional	Full name or long name of the system.
Asset ID	Optional	A unique identifier for the system or the interface. The IT or Property department designates the Asset ID.
External	Required	A flag for systems that are not owned or controlled by the client organization from which a data feed is taken. Select True or False.
System Description	Required	Description of the system and the business purpose.
System URL	Optional	Link to another page where related information is mentioned. Include the network protocol in the link. For example, enter https://www.website.com.
Parent System Name	Optional	Short name of the parent system if the system belongs to a hierarchy.
Axon Viewing	Optional	Whether the system is available for public viewing or not. You can select one of the following options: - Public - Non-Public Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you set this field as Non-Public.
Axon Status	Optional	Status of the system in Axon. You can select one of the following statuses: - Active - Inactive - Pending Review - Obsolete - Deleted
Lifecycle	Required	Stage of the system in the production lifecycle. You can select the following default stages: - In Production - Being Decommissioned - Decommissioned You can also create lifecycle stages.
System Type	Required	Whether the system is a software application or one of several file types. You also need to specify whether the system is hosted internally inside your organization or externally outside your organization.
System Classification	Optional	Classification of the system that best describes its function. You can select the Data Warehouse classification, or create your own classification options.
Confidentiality	Optional	The Confidentiality rating from the Confidentiality, Integrity, and Availability (CIA) rating of a system. Confidentiality rating indicates the ability of a system to show the right information to the right users who have the right credentials. Confidentiality, Integrity, and Availability are crucial elements of security for a system. The default Confidentiality rating ranges from 1 to 3. You can add a maximum of nine ratings from the Admin panel. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a system that is less secure. - 2 - Indicates average security of a system that is moderately secure. - 3 - Indicates strong security of a system that is the most secure. For example, if the Confidentiality rating is 2, the system is moderately secure.
Integrity	Optional	The Integrity rating from the Confidentiality, Integrity, and Availability (CIA) rating of a system. Integrity rating indicates the ability of a system to ensure that the information shown to the users have not been compromised. Confidentiality, Integrity and Availability are crucial elements of security for a system. The default Integrity rating ranges from 1 to 3. You can add a maximum of nine ratings from the Admin panel. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a system that is less secure. - 2 - Indicates average security of a system that is moderately secure. - 3 - Indicates strong security of a system that is the most secure. For example, if the Integrity rating is 1, the system is less secure.
Availability	Optional	The Availability rating from the Confidentiality, Integrity, and Availability (CIA) rating of a system. Availability rating indicates the ability of a system to show the right information to the right users at the right time. Confidentiality, Integrity and Availability are crucial elements of security for a system. The default Availability rating ranges from 1 to 3. You can add a maximum of nine ratings from the Admin panel. Each digit in the rating has the following indicators: - 1 - Indicates weak security of a system that is less secure. - 2 - Indicates average security of a system that is moderately secure. - 3 - Indicates strong security of a system that is the most secure. For example, if the Availability rating is 3, the system is most secure.

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.

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.

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.

Role Templates

Use Role templates to explain how you can assign different stakeholder roles for an object. Download templates for Roles from Axon to perform a bulk upload.

If an object in a role 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 Capability Role template, the Capability Ref. and Capability Name columns are optional. You need to fill in the Glossary Ref. or Glossary Name column before you bulk upload the Capability role template.

You can bulk upload the following types of roles:

•Business Area
•Capability
•Client
•Committee
•Data Set
•Glossary
•Interface
•Legal Entity
•Policy
•Process
•Product
•Project
•Regulation
•System

Business Area Role

Download the Business Area Role template to bulk upload business area roles to Axon.

The following table describes the fields of the Business Area Role template:

Field	Type	Description
Business Area Name	Required	Name of the business area.
Business Area Parent Name	Optional	Name of the parent business area if the business area belongs to a hierarchy.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the Business Area Head role.

Capability Role

Download the Capability Role template to bulk upload capability roles to Axon.

The following table describes the fields of the Capability Role template:

Field	Type	Description
Capability Ref.	Optional	A unique reference identifier for the capability.
Capability Name	Optional	Name of the capability.
Parent Capability Name	Optional	Parent name of the capability if the capability belongs to a hierarchy.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the Capability Owner role.

Client Role

Download the Client Role template to bulk upload client roles to Axon.

The following table describes the fields of the Client Role template:

Field	Type	Description
Client Name	Required	Short name of the client. Enter a name that users can recognize easily.
Client Parent Name	Optional	Parent name of the client that you want to create.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the Client Segmentation Owner role.

Committee Role

Download the Committee Role template to bulk upload committee roles to Axon.

The following table describes the fields of the Committee Role 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	Parent name of the committee that you want to create.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the Committee Chair role.

Data Set Role

Download the Data Set Role template to bulk upload data set roles to Axon.

The following table describes the fields of the Data Set Role template:

Field	Type	Description
Data Set Ref.	Optional	A unique reference identifier for the data set.
Data Set Name	Optional	Name of the data set.
Data Set System Name	Optional	Name of the system that the data set belongs to.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles. - Data Steward - Data Owner

Glossary Role

Download the Glossary Role template to bulk upload glossary roles to Axon.

The following table describes the fields of the Glossary Role template:

Field	Type	Description
Ref.	Optional	A unique reference identifier for the glossary.
Name	Optional	Name of the glossary.
Parent Name	Optional	Parent name of the glossary term. The glossary parent name must exist in Axon.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles: - Glossary Definition Owner - Glossary Steward

Interface Role

Download the Interface Role template to bulk upload interface roles to Axon.

The following table describes the fields of the Interface Role template:

Field	Type	Description
Interface Ref.	Optional	A unique reference 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.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles. - Interface Owner - Interface Steward

Legal Entity Role

Download the Legal Entity Role template to bulk upload legal entity roles to Axon.

The following table describes the fields of the Legal Entity Role template:

Field	Type	Description
Legal Entity Name	Required	Short name of the legal entity. Enter a name that other Axon users can recognize easily.
Legal Entity Parent Name	Optional	Parent name of the legal entity that you want to create.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the Legal Entity Owner role.

Policy Role

Download the Policy Role template to bulk upload policy roles to Axon.

The following table describes the fields of the Policy Role template:

Field	Type	Description
Policy Ref.	Optional	A unique reference identifier for the policy.
Policy Name	Optional	Short name of the policy. Enter a name that users can recognize easily.
Policy Parent Name	Optional	Parent name of the policy that you want to create.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles: - Policy Owner - Policy Steward

Process Role

Download the Process Role template to bulk upload process roles to Axon.

The following table describes the fields of the Process Role template:

Field	Type	Description
Process Ref.	Optional	A unique reference identifier for the process.
Process Name	Optional	Name of the process.
Parent Process Name	Optional	Parent name of the process.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select one the following roles: - Process Owner - Process Steward

Product Role

Download the Product Role template to bulk upload product roles to Axon.

The following table describes the fields of the Product Role template:

Field	Type	Description
Product Name	Required	Short name of the product. Enter a name that users can recognize easily.
Product Parent Name	Optional	Parent name of the product if the product belongs to a hierarchy.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles: - Product Owner - Product Steward

Project Role

Download the Project Role template to bulk upload project roles to Axon.

The following table describes the fields of the Project Role 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	Parent name of the project that you want to create.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles: - Project Manager - Project Steward

Regulation Role

Download the Regulation Role template to bulk upload regulation roles to Axon.

The following table describes the fields of the Regulation Role template:

Field	Type	Description
Regulation Ref.	Optional	A unique reference identifier for the regulation.
Regulation Name	Optional	Short name for the regulation. The most commonly used name or an acronym for the regulation, such as GDPR. Enter a name that users can recognize easily.
Parent Regulation Name	Optional	Parent name of the regulation that you want to create.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles: - Regulation Owner - Regulation SME

System Role

Download the System Role template to bulk upload system roles to Axon.

The following table describes the fields of the System Role template:

Field	Type	Description
System Name	Required	Short name of a system that other Axon users can recognize easily.
User Email	Optional	Unique email address of the user. Axon sends emails to this email address.
User First Name	Optional	First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Last Name	Optional	Last Name of the user. Specify the name as it is recorded in the LDAP directory server of your organization.
User Lan ID	Optional	Network ID of the user.
Governance Role	Required	The role of the user. You can select the following roles: - System Business Owner - System Steward

Data Marketplace Templates

The Data Marketplace template allows you to create or update categories for data collections in Axon Data Marketplace. Download templates for Data Marketplace objects from Axon to perform a bulk upload.

Upload New Items

The following table describes the fields of the Category template that you can use to upload new items:

Field	Type	Description
ID	Required	A unique reference identifier for the category.
Name	Required	Name of the category
Status	Required	Status of the category. You can select one of the following statuses: - Active - Inactive
Description	Optional	Description of the category.
Parent ID	Optional	Parent ID of the category in the category hierarchy.

Upload Existing Items

The following table describes the fields of the Category template that you can use to update items:

Field	Type	Description
ID	Required	A unique reference identifier for the category. Note: Do not modify the value when you update a category.
Name	Required	Name of the category
Status	Required	Status of the category. You can select one of the following statuses: - Active - Inactive
Description	Optional	Description of the category.
Parent ID	Optional	Parent ID of the category in the category hierarchy.