AX 72 BulkUploadReferenceGuide en

Informatica® Axon Data Governance
7.2
Bulk Upload Reference Guide

Informatica Axon Data Governance Bulk Upload Reference Guide
7.2
April 2021
© Copyright Informatica LLC 2018, 2021
This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be
reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC.
Informatica and the Informatica logo are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A
current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade
names or trademarks of their respective owners.
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial
computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the
extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights
reserved. Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta
Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated.
All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights
reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved.
Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright
© Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo
Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All
rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © International Business Machines Corporation. All rights reserved. Copyright ©
yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright © University of Toronto. All rights reserved. Copyright © Daniel
Veillard. All rights reserved. Copyright © Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved.
Copyright © PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved.
Copyright © Red Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC
Corporation. All rights reserved. Copyright © Flexera Software. All rights reserved. Copyright © Jinfonet Software. All rights reserved. Copyright © Apple Inc. All rights
reserved. Copyright © Telerik Inc. All rights reserved. Copyright © BEA Systems. All rights reserved. Copyright © PDFlib GmbH. All rights reserved. Copyright ©
Orientation in Objects GmbH. All rights reserved. Copyright © Tanuki Software, Ltd. All rights reserved. Copyright © Ricebridge. All rights reserved. Copyright © Sencha,
Inc. All rights reserved. Copyright © Scalable Systems, Inc. All rights reserved. Copyright © jQWidgets. All rights reserved. Copyright © Tableau Software, Inc. All rights
reserved. Copyright© MaxMind, Inc. All Rights Reserved. Copyright © TMate Software s.r.o. All rights reserved. Copyright © MapR Technologies Inc. All rights reserved.
Copyright © Amazon Corporate LLC. All rights reserved. Copyright © Highsoft. All rights reserved. Copyright © Python Software Foundation. All rights reserved.
Copyright © BeOpen.com. All rights reserved. Copyright © CNRI. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various
versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or
agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software
copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License
Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any
kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California,
Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and
redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.
This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or
without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http://www.dom4j.org/ license.html.
The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to
terms available at http://dojotoolkit.org/license.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations
regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at
http:// www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software
are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at
http:// www.pcre.org/license.txt.
This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://
www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://
httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/
release/license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/
license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/
licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/
Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/
license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/
software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/
iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/
index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt;
http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/
EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://
jdbc.postgresql.org/license.html; http://protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/
LICENSE; http://web.mit.edu/Kerberos/krb5-current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/
master/LICENSE; https://github.com/hjiang/jsonxx/blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/
LICENSE; http://one-jar.sourceforge.net/index.php?page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-
lang.org/license.html; https://github.com/tinkerpop/blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/
intro.html; https://aws.amazon.com/asl/; https://github.com/twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/
LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and
Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary
Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://
opensource.org/licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/
licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).
This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab.
For further information please visit http://www.extreme.indiana.edu/.
This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject
to terms of the MIT license.
See patents at https://www.informatica.com/legal/patents.html.
DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied
warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The
information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation
is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES
OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH
OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at
infa_documentation@informatica.com.
Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE
INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.
Publication Date: 2021-04-30

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Product Availability Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1: Bulk Upload Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Bulk Upload Data Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Bulk Uploading Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Select Template File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Map Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Upload Template File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Change Request Guidelines for Bulk Uploading Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Assign Segments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Assigning a Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Bulk Delete Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Bulk Deleting Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Bulk Delete Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Bulk Deleting Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2: Bulk Upload Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Bulk Upload Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Template Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Object Identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Business & Change Object Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Committee. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Organizational Object Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Business Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Org Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
People. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4 Table of Contents
Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Regulatory Object Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Geography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Regulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Regulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Regulatory Theme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Data & Technology Object Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Data Quality Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Data Quality Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Relationship Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Attribute X Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Attribute X Physical Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Business Area X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Business Area X Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Business Area X System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Capability X Business Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Capability X Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Capability X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Capability X Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Capability X Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Capability X Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Capability X System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Committee X Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Committee X Committee. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Data Set X Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Data Set X Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Data Set X Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Glossary X Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Glossary X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Glossary X Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Interface X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Legal Entity X Geography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Local Data Quality Rule X Technical Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
People X People. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Policy X Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Policy X Business Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Policy X Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Table of Contents 5
Policy X Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Policy X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Policy X Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Policy X Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Policy X Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Policy X Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Policy X Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Policy X System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Process X Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Process X Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Process X Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Process X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Process X Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Process X Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Process X Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Process X System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Process X System Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Product X Business Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Product X Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Product X Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Project X Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Project X Business Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Project X Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Project X Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Project X Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Project X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Project X Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Project X Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Project X Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Project X System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Regulation X Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Regulation X Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Regulation X Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Regulation X Regulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Regulation X Regulatory Theme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Regulator X Geography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Segment X Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Standard Data Quality Rule X Technical Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
System X Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
System X Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
System X Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
System X Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6 Table of Contents
System X Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Role Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Business Area Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Capability Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Client Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Committee Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Data Set Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Glossary Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Interface Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Legal Entity Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Policy Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Process Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Product Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Project Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Regulation Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
System Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Data Marketplace Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Consumer Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Table of Contents 7
Preface
Use the Bulk Upload Reference Guide to learn how to bulk upload data to Informatica Axon. If you have large
amounts of objects, relationships, and roles to enter in Axon, you can use the option to bulk upload data
using Microsoft Excel templates. This guide covers the tasks that you can perform using the bulk upload
option in the Axon Web interface.
Informatica Resources
Informatica provides you with a range of product resources through the Informatica Network and other online
portals. Use the resources to get the most from your Informatica products and solutions and to learn from
other Informatica users and subject matter experts.
Informatica Network
The Informatica Network is the gateway to many resources, including the Informatica Knowledge Base and
Informatica Global Customer Support. To enter the Informatica Network, visit
https://network.informatica.com.
As an Informatica Network member, you have the following options:
• Search the Knowledge Base for product resources.

• View product availability information.
• Create and review your support cases.
• Find your local Informatica User Group Network and collaborate with your peers.
Informatica Knowledge Base

Use the Informatica Knowledge Base to find product resources such as how-to articles, best practices, video
tutorials, and answers to frequently asked questions.
To search the Knowledge Base, visit https://search.informatica.com. If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team at
KB_Feedback@informatica.com.
Informatica Documentation
Use the Informatica Documentation Portal to explore an extensive library of documentation for current and
recent product releases. To explore the Documentation Portal, visit https://docs.informatica.com.
8
If you have questions, comments, or ideas about the product documentation, contact the Informatica
Documentation team at infa_documentation@informatica.com.
Informatica Product Availability Matrices

Product Availability Matrices (PAMs) indicate the versions of the operating systems, databases, and types of
data sources and targets that a product release supports. You can browse the Informatica PAMs at
https://network.informatica.com/community/informatica-network/product-availability-matrices.
Informatica Velocity
Informatica Velocity is a collection of tips and best practices developed by Informatica Professional Services
and based on real-world experiences from hundreds of data management projects. Informatica Velocity
represents the collective knowledge of Informatica consultants who work with organizations around the
world to plan, develop, deploy, and maintain successful data management solutions.
You can find Informatica Velocity resources at http://velocity.informatica.com. If you have questions,
comments, or ideas about Informatica Velocity, contact Informatica Professional Services at
ips@informatica.com.
Informatica Marketplace
The Informatica Marketplace is a forum where you can find solutions that extend and enhance your
Informatica implementations. Leverage any of the hundreds of solutions from Informatica developers and
partners on the Marketplace to improve your productivity and speed up time to implementation on your
projects. You can find the Informatica Marketplace at https://marketplace.informatica.com.
Informatica Global Customer Support

You can contact a Global Support Center by telephone or through the Informatica Network.
To find your local Informatica Global Customer Support telephone number, visit the Informatica website at
the following link:
https://www.informatica.com/services-and-training/customer-success-services/contact-us.html.
To find online support resources on the Informatica Network, visit https://network.informatica.com and
select the eSupport option.
Preface 9
Chapter 1
Bulk Upload Data

This chapter includes the following topics:
• Bulk Upload Data Overview, 10

• Bulk Uploading Data, 11
• Assign Segments, 14
• Bulk Delete Relationships, 16
• Bulk Delete Roles, 17
Bulk Upload Data Overview

If you have large amounts of objects, relationships, and roles to enter in Axon, you can use the option to bulk
upload data. You can download a Microsoft Excel template from Axon to bulk upload object, roles, and
relationships.
A WebUser with the New or Edit permission, Admin, and SuperAdmin can bulk upload data to Axon. If a web
user has the New permission for an object, the user can upload a new file but cannot upload existing items. If
a web user has the Edit permission, the user can update existing items but cannot upload a new file. A web
user can upload new items or update existing relationships and roles for objects that they can add or edit.
When you bulk upload new objects, Axon assigns you as the default stakeholder for the objects. If you have
configured default roles for a facet in the Admin Panel, Axon assigns the default roles to the user who bulk
uploads data.
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 to Axon.
• Remove existing relationships from Axon.
After you select the upload type, you can choose the object, relationship, or role. You can also perform a
keyword search to find the exact object, relationship, or role that you want to upload.
You can bulk upload objects, such as Attribute, People, Process, and Regulation. You can bulk upload
relationships, such as Attribute X Attribute, Policy X Glossary, and System X Product. You can bulk upload
roles, such as Data Set Role, Glossary Role, and Interface Role.
You can use a Microsoft Excel template that you have created to upload data to Axon. Informatica
recommends that you use the templates that Axon provides.
You can bulk assign objects to a segment. You can specify the segment to which you want to assign the
objects, enter the object details in the template, and upload the template to Axon. If you do not provide a
10
segment for an object, Axon assigns the default Enterprise segment to the object. If you enter a segment for
a parent object, you must enter the same segment for child objects.
You can use a comma-separated-value (CSV) file format to bulk upload 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.
Note: You must have the necessary permission to create or update Axon objects before you can bulk upload
data.
Bulk Uploading Data

To bulk upload data, you must use a Microsoft Excel template. Enter the data in the template and upload the
filled template to Axon.
The following image shows the tasks that you must perform to upload data to Axon:
1. Enter data in the Microsoft Excel template and select the template file in Axon.
2. Map the columns in the template to the columns in Axon.
3. Upload the template to Axon.
Select Template File

1. In the Axon toolbar, click Create > Upload from file.
Axon displays the Upload From File page. Use the wizard to choose options related to bulk uploading of
data. The first step of the wizard is Choose File.
2. From the Upload Type list, select the type of item that you want to upload. The type of upload items
include Object, Relationship, and Role.
3. Based on the type of upload item, select the type of a relationship, object, or role in the field to the right
of the Upload Type list.
When you start typing a keyword in the search box, Axon suggests the matching object, relationship, or
role that you want to upload.
4. Choose whether you want to upload new items or update existing items.
The options to upload a new item or update an existing item appear based on the type of item that you
choose to upload.
Bulk Uploading Data 11

5. Click Download Template.
A Microsoft Excel template is downloaded to the Downloads folder.
6. In the Microsoft Excel template, add the data that you want to add or update in Axon, and then save the
file.
Note:
• In the template, columns with headers in red color are required.
• The template includes columns for custom fields that the Admin or SuperAdmin might have created.
• If a custom field requires a value, make sure that you enter a supported value before you save the file.
• If a field in the template requires a date, make sure that you enter the date in the DD/MM/YYYY
format.
• If a field in the template requires a time, make sure that you enter the time in the 24 hours format.
• If the administrator has defined mandatory workflow approvals for the facet, Axon ignores the values
that you enter in the bulk upload file for the Axon Status field. Instead, Axon assigns the values that
the administrator has configured for these fields in the Admin Panel.
For more information on workflows, see the Informatica Axon Data Governance 7.2 User Guide.
7. Click Choose File and select the template file.
8. To cancel the upload when Axon detects a conflict, select Cancel on warning.
9. Click Next — Map Columns.
The following guidelines apply if the administrator has configured automatic change requests and you select
the Cancel on warning option when you upload a template file:
• If a WebUser has created an object and specified an admin user as a stakeholder, Axon does not start the
change request if the WebUser updates the object. The admin user must update the object to start the
change request automatically. Also, if the WebUser specifies a value for the Lifecycle field when updating
the object, Axon ignores the value and applies the default value that the admin has configured for the
Lifecycle field in the Admin Panel.
• If a WebUser has created an object and specifed the same user as a stakeholder, Axon automatically
starts a change request for the object. If the WebUser specifies a value for the Lifecycle field when
updating the object, Axon ignores the value and applies the default value that the admin has configured
for the Lifecycle field in the Admin Panel.
Map Columns
After you upload the template, you need to map the template columns with the Axon properties to start the
bulk upload process.
1. In the Map Columns step of the wizard, map the columns in the Microsoft Excel template to the
properties that Axon supports. Double-click a column in the Column in Uploaded File column and select
the value that corresponds to the value in the Axon Field column.
Note:
• The Axon Status and Axon Viewing columns of the template are not populated automatically. If you
want to map these column values to the values in the Axon Field column, ensure that the template file
contains values for the Axon Status and Axon Viewing columns.
• If you want to bulk upload objects with default values for custom fields, you must not map the non-
mandatory custom fields with the Axon properties.
2. To continue with the bulk upload wizard steps, click Next Start Upload.
12 Chapter 1: Bulk Upload Data

Upload Template File
1. In the Upload step of the wizard, review the progress of the upload task. If the upload fails, you can
download the error report to troubleshoot the upload.
Axon displays a progress bar and a message to indicate the progress of the upload task.
2. To view the status of the bulk upload job, click Go to My Jobs.
Axon displays the list of pending tasks in the My Jobs page of the Activity Stream tab. You can open the
My Jobs page from the People object to view the progress of the upload task in the Status column at
any time.
3. From the Action column in the My Jobs page, you can upload a fixed file again, or download the original
file that you uploaded.
4. Optionally, click the Notifications icon on the Axon toolbar and click the Bulk Upload tab to see the
progress of the pending task.
Change Request Guidelines for Bulk Uploading Data

Note the following guidelines for automatic change requests when you upload data using the bulk upload
templates.
Requirements for Automatic Change Requests

To automatically start a change request when a user creates or updates an object using the bulk upload
template, the following conditions must be met:
• The administrator has configured automatic change requests in the Axon Admin Panel. For more
information, see the Configure Default Values for Automatic Change Requests topic in the Axon Data
Governance 7.2 Administrator Guide.
• A user with a data steward role must be specified as stakeholder for the object.
Guidelines for Cancel on Warning Option

If the administrator has configured automatic change requests, and you select the Cancel on warning option
when you upload a bulk update template file, the upload operation is not cancelled under the following
situations. During these situations, Axon updates the objects in the template file and displays warnings in the
bulk upload report.
Bulk update objects that specify admin user as stakeholder
If a WebUser or admin user updates the object, Axon does not automatically start a change request. To
start a change request automatically, you must edit the object and specify a WebUser with steward role
as a stakeholder for the object.
If a WebUser or admin user specifies a value for the Lifecycle field when updating the object, Axon
ignores the value and applies the default value that the admin has configured for the Lifecycle field in
the Default Change Requests section of the Axon Admin Panel.
Bulk update objects that specify WebUser as stakeholder
If a WebUser or admin user updates the object, Axon automatically starts a change request because a
WebUser is specified as a stakeholder.
If a WebUser or admin user specifies a value for the Lifecycle field when updating the object, Axon
ignores the value and applies the default value that the admin has configured for the Lifecycle field in
the Default Change Requests section of the Axon Admin Panel.
Note: If you use an API to upload objects, and you specify the true value for the stopOnWarning parameter,
the upload operation is not cancelled when the above conditions apply. To use the API, see the Create,
Update, and Delete Objects and Relationships chapter in the Axon Data Governance 7.2 REST API Guide.
Bulk Uploading Data 13

Assign Segments
You can choose to assign objects to a single or multiple segments in bulk.
If you want to assign all the objects in a template file to the same segment, you can select the segment in the
first step of the bulk upload wizard. If a template file has objects that need to be assigned to more than one
segment, you can provide the segment information in the template file.
When you perform a bulk upload task, in the Segment field, select a segment to which you want to assign
objects. If you want the objects to be available to everyone in the organization, select the Enterprise
segment. If you want to assign the objects to multiple segments in the template, select the Multiple segment.
Note: The segment list appears only if a SuperAdmin user has created segments in the Admin Panel.
The following image shows the first step of the Bulk Upload wizard:
You can assign only a single segment to an object. When you download the bulk upload template for an
object, the template contains an additional Segment column in which you can specify the segment. If you
select a segment in the Segment field and select another segment in the Segment column of the template,
Axon considers the segment that you mentioned in the Segment field instead of the segment mentioned in
the template.
If you select the Multiple segment option, download the bulk template for an object and enter multiple
segment names in the Segment column of the template. For example, you can assign five glossaries to
segment A, five glossaries to segment B, and five glossaries to segment C.
You cannot assign a segment to the following types of objects:
• Attributes
• Org Unit
• People
• Data Quality Rule
• System Interface
When you bulk update the existing items, you cannot view the Segment column in the template.
Use the Segment x Object relationship template to reassign objects from one segment to another.

Assigning a Segment
Use bulk upload templates to assign objects to a segment or multiple segments.

Axon displays the Upload From File page. Use the wizard to assign segments to objects in bulk. The first
step of the wizard is Choose File.
2. From the Upload Type list, select Object.
3. Based on the type of upload item, select the type of an object in the field to the right of the Upload Type
list.
When you start typing a keyword in the search box, Axon suggests the matching object, relationship, or
role that you want to upload.
4. In the Segment field, select a segment to which you want to assign objects. If you want the objects to be
available to everyone in the organization, select the Enterprise segment. If you want to assign the
objects to multiple segments in the template, select the Multiple segment.
Note: If you select a segment in the Segment field and select another segment in the template, Axon
considers the segment that you mentioned in the Segment field.
5. Choose whether you want to upload new items or update existing items.
The options to upload a new item or update an existing item appear based on the type of item that you
choose to upload.
7. In the Microsoft Excel template, add the data that you want to add or update in Axon, and then save the
file. Enter the segment names in case you choose to assign multiple segments.
Note: The Axon Status and Axon Viewing columns of the template are not populated automatically. If
you want to map these column values to the values in the Axon Field column, ensure that the template
file contains values for the Axon Status and Axon Viewing columns.
any time.
15. From the Action column in the My Jobs page, you can upload a fixed file again, or download the original
file that you uploaded.
16. Optionally, click the Notifications icon on the Axon toolbar and click the Bulk Upload tab to see the
progress of the pending task.
Assign Segments 15
Bulk Delete Relationships
Use bulk upload templates to delete relationships between the objects. The templates are same as the ones
you use to create relationships between object.
When you delete relationships, Axon removes the existing relationships between the objects. You can delete
relationships between objects in bulk instead of deleting the relationship for each object from the Axon
interface.
To update relationships in bulk, you have to first delete the existing relationships and then create the
relationships that you want.
If the Admin or SuperAdmin user has configured mandatory workflow when you delete a relationship from the
Axon interface, Axon will start the same workflow when you delete the relationship using the bulk upload
template. Axon starts mandatory workflows when you delete relationships for the following facets:
• Glossary
• System
• Data Set
• Process
For more information on workflows, see the Informatica Axon Data Governance User Guide.
Bulk Deleting Relationships

When you perform a bulk delete task, use bulk upload templates to remove the relationships between
objects.

Axon displays the Upload From File page. Use the wizard to choose options related to bulk deleting of
relationships.
2. From the Upload Type list, select Relationship.
3. Select a relationship in the field next to the Upload Type list.
When you start typing a keyword in the search box, Axon suggests matching relationships from which
you can select the relationship that you want to delete.
4. From the Upload Option list, choose Remove Existing Items.
6. In the Microsoft Excel template, enter the details of the objects for which you want to delete the
relationships.

any time.
After the bulk delete operation completes, Axon removes the relationships between the objects.
Bulk Delete Roles

Use bulk upload templates to delete roles for the objects. The templates are same as the ones you use to
create roles for object.
When you delete roles, Axon removes the existing roles for the objects. You can delete roles for objects in
bulk instead of deleting the role for each object from the Axon interface.
To update roles in bulk, you have to first delete the existing roles and then create the roles that you want.
Bulk Deleting Roles

When you perform a bulk delete task, use bulk upload templates to remove the roles for objects.

Axon displays the Upload From File page. Use the wizard to choose options related to bulk deleting of
roles.
2. From the Upload Type list, select Role.
3. Select a role in the field next to the Upload Type list.
When you start typing a keyword in the search box, Axon suggests matching roles from which you can
select the role that you want to delete.
4. From the Upload Option list, choose Remove Existing Items.
6. In the Microsoft Excel template, enter the details of the objects for which you want to delete the roles.
Bulk Delete Roles 17

any time.
After the bulk delete operation completes, Axon removes the roles for the objects.

Chapter 2
Bulk Upload Templates

This chapter includes the following topics:
• Bulk Upload Templates, 19

• Template Types, 20
• Business & Change Object Templates, 21
• Organizational Object Templates, 33
• Regulatory Object Templates, 48
• Data & Technology Object Templates, 55
• Relationship Templates, 88
• Role Templates, 127
• Data Marketplace Templates, 136
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.
• Remove existing relationships and roles from Axon.
If you are part of a segment, you can bulk upload data that belongs to the segment that you can access. If
you do not provide a segment for an object, Axon assigns the default Enterprise segment to the object. An
object and its parent object must be in the same segment. If you enter a segment for a parent object, you
need to enter the same segment for child objects.
19
If an object belongs to a private segment, the related objects can be part of the same private segment or
Enterprise segment. If an object belongs to one private segment, the related objects cannot be part of
another private segment.
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
• 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.
Object Identifier
An object identifier (ID) is a unique integer that you can use while you update existing objects using bulk
upload templates.
When an object is created, Axon automatically generates a unique numeric value for the ID column. Axon
uses the ID value for its internal logic. You cannot configure the ID value. The ID column is hidden by default
in Unison search. When you bulk update existing items, you can specify the IDs in the template to uniquely
identify the objects. You can view the ID column only in bulk update templates. The ID column in the template
is in the following format: <Facet Name> ID. For example, when you bulk update the Policy template, you can
enter the Policy ID values to uniquely identify Policy objects.
20 Chapter 2: Bulk Upload Templates

The ID column is different from the Ref. column that is present in both bulk upload and bulk update
templates. You can configure the value in the Ref. column. If you do not specify a value in the Ref. column,
Axon automatically assigns a reference identifier to an Axon object. The Ref. column can have alphanumeric
values. You can provide external source references in the Ref. column in Axon. For example, in a process
diagram, you can configure reference identifiers for each step in a process for better clarity and
understanding.
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.
Business & Change Object Templates 21

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
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:
Committee ID Optional A unique integer that identifies the committee. When you
create a committee, Axon automatically generates an 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
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.
- Public
- 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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the committee in the production lifecycle.

- In Effect
- Obsolete
Committee Type Required Type of the committee.

- 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:
Name Required Name of the policy. Enter a name that other Axon users can
recognize easily.
Ref. 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.
Description Required Description 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 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.
- Public
- Non-Public
Axon Status Optional Status of the policy in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
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.

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.

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.

The following table describes the fields of the Policy template that you can use to update existing items:
ID Optional A unique integer that identifies the policy. When you create a
policy, Axon automatically generates an ID for the policy.
Name Required Name of the policy. Enter a name that other Axon users can
recognize easily.
Ref. Optional Reference identifier for the policy. If you leave this field
empty, Axon assigns a new reference identifier
automatically.
Internal Required Indicates whether the policy is internal or external.
URL Optional Link to another page where the policy is mentioned in detail.
Description Required Description 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 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.
- Public
- Non-Public
Axon Status Optional Status of the policy in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the policy in the approval lifecycle.

- Draft
- Enforced
- Obsolete
You can also create policy lifecycle stages.
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:
Name Required Name of the process.
Ref. Optional Reference identifier for the process. If you leave this field

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. (*)
Duration Optional The time duration for the process that you create.
Parent 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.
- Public
- Non-Public
Axon Status Optional Status of the process in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
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.

- 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.

- Process Owner
- Process Steward
Segment Optional The segment to which you want to assign the process to.
(*) 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.

The following table describes the fields of the Process template that you can use to update existing items:
ID Optional A unique integer that identifies the process. When you

create a process, Axon automatically generates an ID for the
process.
Name Required Name of the process.
Ref. Optional Reference identifier for the process. If you leave this field
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. (*)
Duration Optional The time duration for the process that you create.
Parent 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.
- Public
- Non-Public
Axon Status Optional Status of the process in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted

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.

- 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:
Reference Optional Reference identifier for the project. If you leave this field
Project Name Required Name of the project. Enter a name that other Axon users
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.
- Public
- Non-Public
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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Project Lifecycle Required Stage of the project in the project management lifecycle.
- 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 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

- Project Manager
- Project Steward
Segment Optional The segment to which you want to assign the project to.

The following table describes the fields of the Project template that you can use to update existing items:
Project ID Optional A unique integer that identifies the project. When you
create a project, Axon automatically generates an ID for the
project.
Reference Optional Reference identifier for the project. If you leave this field
Project Name Required Name of the project. Enter a name that other Axon users
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.
- Public
- 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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Project Lifecycle Required Stage of the project in the project management lifecycle.
- 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.
• Business Area
• Client
• Capability
• Legal Entity
• Product
• People
• Org Unit
Organizational Object Templates 33

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:
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.
- Public
- Non-Public
Axon Status Optional Status of the business area in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the business area in the governance lifecycle.

- Operating
- Obsolete
You can also create the lifecycle stages.


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

The following table describes the fields of the Business Area template that you can use to update existing
items:
Business Area ID Optional A unique integer that identifies the business area. When you
create a business area, Axon automatically generates an ID
for the business area.
Description Required Description of the business area.
Parent Business Area Optional Parent name of the business area if the business area
Axon Viewing Optional Whether the business area is available for public viewing or
not.
- Public
- Non-Public
Axon Status Optional Status of the business area in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the business area in the governance lifecycle.

- 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:
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.
- Public
- 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.

- 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.


You can select the Capability Owner role.
Segment Optional The segment to which you want to assign the capability to.

The following table describes the fields of the Capability template that you can use to update existing items:
Capability ID Optional A unique integer that identifies the capability. When you
create a capability, Axon automatically generates an ID for
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.
- Public
- 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.

- 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
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:
Client Name Required Short name of the client. Enter a name that other Axon users
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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Axon Viewing Optional Whether the client is available for public viewing or not.
- Public
- Non-Public


Select Client Segmentation Owner.
Segment Optional The segment to which you want to assign the client to. This
in the Admin Panel.

The following table describes the fields of the Client template that you can use to update existing items:
Client ID Optional A unique integer that identifies the client. When you create a
client, Axon automatically generates an ID for the client.
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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Axon Viewing Optional Whether the client is available for public viewing or not.
- Public
- 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:
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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Axon Viewing Optional Whether the legal entity is available for public viewing or
not.
- Public
- Non-Public

You can select the Legal Entity Owner role.
Segment Optional The segment to which you want to assign the legal entity to.

The following table describes the fields of the Legal Entity template that you can use to update existing
items:
Legal ID Optional A unique integer that identifies the legal entity. When you
create a legal entity, Axon automatically generates an ID for
the legal entity.
Short Name Required Short name of the legal entity. Enter a name that other Axon
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.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Axon Viewing Optional Whether the legal entity is available for public viewing or
not.
- Public
- 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:
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.

The following table describes the fields of the Org Unit template that you can use to update existing items:
Org Unit ID Optional A unique integer that identifies the organizational unit.
When you create an organizational unit, Axon
automatically generates an ID for 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
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:
First Name Required First name of the user. Specify the name as it is recorded in
Last Name Required Last name of the user. Specify the name as it is recorded in
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.

- 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.

The following table describes the fields of the People template that you can use to update existing items:
People ID Optional A unique integer that identifies the user. When you create a
People object, Axon automatically generates an ID for the
People object.
First Name Required First name of the user. Specify the name as it is recorded in
Last Name Required Last name of the user. Specify the name as it is recorded in
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.

- 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.

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:
Reference Optional A unique reference identifier for the product.
Product Name Required Short name of the product. Enter a name that other Axon
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
Axon Status Optional Status of the product in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted

Axon Viewing Optional Whether the product is available for public viewing or not.
- 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.

- Product Owner
- Product Steward
Segment Optional The segment to which you want to assign the product to. This
in the Admin Panel.

The following table describes the fields of the Product template that you can use to update existing items:
Product ID Optional A unique integer that identifies the product. When you create
a product, Axon automatically generates an ID for 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
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

Axon Status Optional Status of the product in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Axon Viewing Optional Whether the product is available for public viewing or not.
- Public
- Non-Public
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.
• 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:
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.

The following table describes the fields of the Geography template that you can use to update existing items:
Geography ID Optional A unique integer that identifies the geographical region.

When you create a geographical region, Axon automatically
generates an 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:
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.
Regulatory Object Templates 49

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.

- 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.
- 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

Select one of the following roles:
- Regulation Owner
- Regulation SME
Segment Optional The segment to which you want to assign the regulation to.

The following table describes the fields of the Regulation template that you can use to update existing items:
Regulation ID Optional A unique integer that identifies the regulation. When you
create a regulation, Axon automatically generates an 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.

- 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.
- 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:
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.

The following table describes the fields of the Regulator template that you can use to update existing items:
Regulator ID Optional A unique integer that identifies the regulator. When you
create a regulator, Axon automatically generates an ID for
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:
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 Required Full name of the regulatory theme.

Name
Description Required Description of the regulatory theme.
Parent Regulatory Theme Optional Long name of the parent regulatory theme.
Name
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.

The following table describes the fields of the Regulatory Theme template that you can use to update
existing items:
Regulatory Theme ID Optional A unique integer that identifies the regulatory theme. When
you create a regulatory theme, Axon automatically generates
an ID for the regulatory theme.
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 Required Full name of the regulatory theme.

Name
Description Required Description of the regulatory theme.
Parent Regulatory Theme Optional Long name of the parent regulatory theme.
Name
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.
• Attribute
• Data Quality Report
• Data Set
• Glossary
Data & Technology Object Templates 55

• 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:
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.
Data Set Ref. Optional A unique reference identifier of the data set that contains
the attribute.
Data Set Name Optional Name of the data set that contains the attribute.
System Short Name 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.

- Data Attribute Owner
- Data Attribute Steward

The following table describes the fields of the Attribute template that you can use to update existing items:
Attribute ID Optional A unique integer that identifies the attribute. When you
create an attribute, Axon automatically generates an ID for
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.
Data Set Ref. Optional A unique reference identifier of the data set that contains
the attribute.
Data Set Name Optional Name of the data set that contains the attribute.
System Short Name 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.
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.
Note:
• Make sure that the attributes you update already exist in Axon.
• In the template, enter the values in the correct format that is required by the fields. When you upload the
template, Axon validates your entries and displays an error if the formats are incorrectly entered.
• Ensure that you enter a value in the Attribute Data Set Ref. or Attribute Data Set Name column though
both the column are optional.
• Ensure that you enter a value in the Glossary Ref. or Glossary Name column though both the columns are
optional.
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:
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 Required The unique reference number of the local data quality rule.
Reference

The following table describes the fields of the Data Quality Report template that you can use to update
existing items:
Data Quality Report ID Optional A unique integer that identifies the Data Quality report.
When you create a Data Quality report, Axon automatically
generates an ID for the Data Quality report. When you
update a Data Quality report, it is recommended that you
enter the ID though this field is optional.
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 Required The unique reference number of the local data quality rule.
Reference

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 the 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:
Rule Name Required Name of the rule.

Bulk upload fails if rules with the same names exists for
different data sets or attributes.
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 Optional The relevant information about the measurement process.
Description
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.
- Public
- Non-Public
as Non-Public.
System Measured In 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.
- Active
- Draft
- Obsolete
You can also create data quality rule lifecycle stages.
Axon Status Optional Status of the data quality rule in Axon.

- 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 Optional The reference to the standard data quality rule that is attached
Reference 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.
Note:
1. You need to have Data Set edit permissions to bulk upload
local data quality rules.
2. You need to have Glossary edit permissions to bulk upload
standard data quality rules.
Hour Optional The scheduled time duration in the 24 hours format to run the
Data Quality rule.
Enter a value from 0-23.
You can configure Hour field if you select one of the following
options in the Frequency field:
- Ad-hoc
- Daily
- Weekly
- Monthly
- Quarterly
- Bi-Weekly
Day Optional The scheduled time duration in the days format to run the Data
Quality rule.
Enter a value from 1-7. For example, if you enter 1, Axon runs
the Data Quality rule on every Sunday.
You can configure Day field if you select one of the following
- Weekly
- Bi-Weekly
Month Optional The scheduled time duration in the months format to run the
Data Quality rule.
the Data Quality rule on every January.
You can configure Month field if you select Quarterly option
in the Frequency field.
Date Optional The scheduled time duration in the dates format to run the Data
Quality rule.
Enter the value from 1-31.
You can configure Date field if you select one of the following
- Quarterly
- Bi-Weekly
Start Date Optional The scheduled start date in the DD/MM/YYYY format to run the
Data Quality rule.
You can configure Start Date field if you select Ad-hoc in the
Frequency field.

Execute Rule Optional The option to enable or disable execution of the local data
quality rule. Select one of the following values:
- True. Enables execution of the local data quality rule.
- False. Disables execution of the local data quality rule.
The default value is False.
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 Optional Short name of the system that contains the data set and the
Name 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
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

You can select the DQ Steward role.

The following table describes the fields of the Data Quality Rule template that you can use to update existing
items:
Data Quality Rule ID Optional A unique integer that identifies the data quality rule. When you
create a data quality rule, Axon automatically generates an ID
for the data quality rule.
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 Optional The relevant information about the measurement process.
Description
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.
- Public
- Non-Public
as Non-Public.
System Measured In 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
Hour Optional The scheduled time duration in the 24 hours format to run the
Data Quality rule.
Enter a value from 0-23.
Make sure that you configure the Hour field if you select one of
the following options in the Frequency field:
- Ad-hoc
- Daily
- Weekly
- Monthly
- Quarterly
- Bi-Weekly
Day Optional The scheduled time duration in the days format to run the Data
Quality rule.
the Data Quality rule on every Sunday.
You can configure Day field if you select one of the following
- Weekly
- Bi-Weekly
Month Optional The scheduled time duration in the months format to run the
Data Quality rule.
the Data Quality rule on every January.
Make sure that you configure the Month field if you select
Quarterly option in the Frequency field.
Date Optional The scheduled time duration in the dates format to run the Data
Quality rule.
Enter the value from 1-31.
You can configure Date field if you select one of the following
- Quarterly
- Bi-Weekly

Start Date Optional The scheduled start date in the DD/MM/YYYY format to run the
Data Quality rule.
You can configure Start Date field if you select Ad-hoc in the
Frequency field.
Execute Rule Optional The option to enable or disable execution of the local data
quality rule. Select one of the following values:
- True. Enables execution of the local data quality rule.
- False. Disables execution of the local data quality rule.
The default value is False.
Lifecycle Required Stage of the data quality rule in the approval lifecycle.
- Active
- Draft
- Obsolete
You can also create data quality rule lifecycle stages.
Axon Status Optional Status of the data quality rule in Axon.

- 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
- Manual
- Unknown
You can also create other automation levels.

Standard Data Quality Rule Optional The reference to the standard data quality rule that is attached
Reference 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
If you leave the field empty, Axon considers the rule as a local
data quality rule.
Note:
1. You need to have Data Set edit permissions to bulk upload
local data quality rules.
2. You need to have Glossary edit permissions to bulk upload
standard data quality rules.
Note: When you update an automatically created local data quality rule, you must update only the following
fields: Amber Target, Green Target, and Frequency.
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:
Ref. Optional The unique identifier for the data set.
Name Required Name of the data set as known in the business.
Definition Required Description of the data set.
Usage Optional Additional information about the data set.
Axon Viewing Optional Whether the data set is available for public viewing or not.
- Public
- Non-Public
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 Short Name Required Short name of the system that contains the data set.
Parent System Short 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.

- Draft
- Approved
- Obsolete
You can also create other lifecycle stages.
Axon Status Optional Status of the data set in Axon.

- 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.
optional.
Parent Glossary Name Optional Parent of the glossary in the glossary hierarchy.

You can select the following roles.
- Data Steward
- Data Owner
Segment Optional The segment to which you want to assign the data set to.

The following table describes the fields of the Data Set template that you can use to update existing items:
ID Optional A unique integer that identifies the data set. When you
create a data set, Axon automatically generates an ID for
the data set.
Ref. Optional The unique identifier for the data set.
Name Required Name of the data set as known in the business.
Definition Required Description of the data set.
Usage Optional Additional information about the data set.
Axon Viewing Optional Whether the data set is available for public viewing or not.
- Public
- Non-Public
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 Short Name Required Short name of the system that contains the data set.
Parent System Short 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.

- Draft
- Approved
- Obsolete
You can also create other lifecycle stages.
Axon Status Optional Status of the data set in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted

Glossary Ref. Optional Reference identifier for the glossary that the data set is
associated with.
optional.
Glossary Name Optional The glossary that the data set is associated with.
optional.
Parent Glossary Name Optional Parent of the glossary in the glossary hierarchy.
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:
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.

Parent Ref. Optional A unique reference identifier for the parent glossary.

Axon Viewing Optional Whether the glossary is available for public viewing or not.
- Public
- Non-Public
Axon Status Optional Status of the glossary in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the glossary in the approval lifecycle.

- Draft
- Being validated
- Approved
- Obsolete
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
The default Integrity rating ranges from 1 to 3. Each digit in
the rating has the following indicators:
secure.
moderately secure.
most secure.
For example, if the Integrity rating is 1, the glossary is less
secure.

Availability Optional The Availability rating from the Confidentiality, Integrity,

Availability rating indicates the ability of a glossary to show
the right information to the right users at the right time.
The default Availability rating ranges from 1 to 3. Each digit
in the rating has the following indicators:
secure.
moderately secure.
most secure.
For example, if the Availability rating is 3, the glossary is
most secure.
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.

- Glossary Definition Owner
- Glossary Steward
Segment Optional The segment to which you want to assign the glossary to.

The following table describes the fields of the Glossary template that you can use to update existing items:
ID Optional A unique integer that identifies the glossary. When you

create a glossary, Axon automatically generates an ID for
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.

Parent Ref. Optional A unique reference identifier for the parent glossary.
Axon Viewing Optional Whether the glossary is available for public viewing or not.
- Public
- Non-Public
Axon Status Optional Status of the glossary in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the glossary in the approval lifecycle.

- Draft
- Being validated
- Approved
- Obsolete

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 rating indicates the ability of a glossary to
right credentials.
The default Confidentiality rating ranges from 1 to 3. Each
secure.
moderately secure.
most secure.
For example, if the Confidentiality rating is 2, the glossary
is moderately secure.
Availability (CIA) rating of a glossary.
Integrity rating indicates the ability of a glossary to ensure
compromised.
The default Integrity rating ranges from 1 to 3. Each digit in
secure.
moderately secure.
most secure.
For example, if the Integrity rating is 1, the glossary is less
secure.

Availability Optional The Availability rating from the Confidentiality, Integrity,

Availability rating indicates the ability of a glossary to show
The default Availability rating ranges from 1 to 3. Each digit
secure.
moderately secure.
most secure.
For example, if the Availability rating is 3, the glossary is
most secure.
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:
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
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.

- In Production
- Being Decommissioned
- Decommissioned
Axon Status Optional Status of the system interface in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Source System Short Required Short name of the system from which the information
Name flows out.

Target System Short 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
- 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.
- Public
- Non-Public

- Interface Owner
- Interface Steward

The following table describes the fields of the Interface template that you can use to update existing items:
Interface ID Optional A unique integer that identifies the interface. When you
create a interface, Axon automatically generates an ID for
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
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.

- In Production
- Decommissioned
Axon Status Optional Status of the system interface in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Source System Short Required Short name of the system from which the information
Name flows out.
Target System Short 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
- 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.
- Public
- 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:
Short Name Required Short name of the system. Enter a name that other Axon
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.
Description Required Description of the system and the business purpose.
URL Optional Link to another page where related information is mentioned.

Parent Short 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.
- Public
- Non-Public
Axon Status Optional Status of the system in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the system in the production lifecycle.

- In Production
- Decommissioned

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.
Classification Optional Classification of the system that best describes its function.
You can select the Data Warehouse classification, or create
your own classification options.

and Availability (CIA) rating of a system.
Confidentiality rating indicates the ability of a system to
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
- 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.
Availability (CIA) rating of a system.
Integrity rating indicates the ability of a system to ensure
compromised.
Confidentiality, Integrity and Availability are crucial elements
The default Integrity rating ranges from 1 to 3. You can add a
maximum of nine ratings from the Admin panel. Each digit in
moderately secure.
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 rating indicates the ability of a system to show
Confidentiality, Integrity and Availability are crucial elements
The default Availability rating ranges from 1 to 3. You can
moderately secure.
secure.
For example, if the Availability rating is 3, the system is most
secure.

- System Business Owner
- System Steward
Segment Optional The segment to which you want to assign the system to. This
in the Admin Panel.

The following table describes the fields of the System template that you can use to update existing items:
ID Optional A unique integer that identifies the system. When you create
a system, Axon automatically generates an ID for the
system.
Short Name Required Short name of the system. Enter a name that other Axon
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.
Description Required Description of the system and the business purpose.
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 Short 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.
- Public
- Non-Public
Axon Status Optional Status of the system in Axon.

- Active
- Inactive
- Pending Review
- Obsolete
- Deleted
Lifecycle Required Stage of the system in the production lifecycle.

- In Production
- Decommissioned
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.
Classification Optional Classification of the system that best describes its function.
You can select the Data Warehouse classification, or create
your own classification options.


and Availability (CIA) rating of a system.
Confidentiality rating indicates the ability of a system to
right credentials.
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.
moderately secure.
secure.
For example, if the Confidentiality rating is 2, the system is
moderately secure.
Integrity rating indicates the ability of a system to ensure
compromised.
The default Integrity rating ranges from 1 to 3. You can add
a maximum of nine ratings from the Admin panel. Each digit
secure.
moderately secure.
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 rating indicates the ability of a system to show
The default Availability rating ranges from 1 to 3. You can
secure.
moderately secure.
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 Physical 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
Relationship Templates 89
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:
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 Short 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 Short Optional Short name of the source system that contains the data set and
Name 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.
Short Name
Interface Target System Optional System to which the information flows in.
Short Name
Attribute X Physical Field

Download the Attribute X Physical Field relationship template to bulk upload the relationships between Axon
attributes and Enterprise Data Catalog fields.
When you bulk upload the Attribute X Physical Field relationship template, Axon validates the operation
based on the following details:
• The Enterprise Data Catalog instance is configured, available, and running.

• The field name, field identifier, and field type are present in Enterprise Data Catalog.

• You have the required permissions to access the physical fields in Enterprise Data Catalog.
The following table describes the fields of the Attribute X Physical Field relationship template:
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 Name 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 Short Optional Short name of the system that contains the data set and
Name 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:
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
Parent Business Area Optional Name of the parent business area if the business area belongs
Name 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:
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 Parent Optional Name of the parent business area if the business area belongs
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:
System Short Name Required Short name of a system or an acronym that other Axon users can
recognize easily for a system.
Parent System Short Name Optional Name of the parent system if the system belongs to a hierarchy.

Relationship Type Required The type of relationship between the business area and system.
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:
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 Parent Area Optional Name of the parent business area if the business area belongs
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:
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.
recognize easily.
hierarchy.
Relationship Type Required The type of relationship between the capability and client.
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:
Glossary Ref. Optional A unique identifier for the glossary.
must exist in Axon.
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.
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:
recognize easily.

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:
Process Ref. Optional A unique reference identifier for the process.
recognize easily.
Parent Process Name Optional Name of the parent process if the process belongs to a hierarchy.
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.
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:
Product Name Required Name of the product.
Product Parent Name Optional Name of the parent product if the product belongs to a hierarchy.
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.
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:
Parent System Short Name Optional Short name of the parent system if the system belongs to a
hierarchy.
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:
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.
recognize easily.
hierarchy.
Relationship Type Required The type of relationship between the committee and capability.
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:
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
Source Committee Parent Optional Name of the parent source committee if the committee belongs
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
Target Parent Committee Optional Name of the parent target committee if the committee belongs
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:
Client Name Required Short name of the client. Enter a name that other Axon users can
recognize easily.
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 Short Optional Short name of the system that contains the data set.
Name
Data Set Parent System Optional Short name of the parent of the system that contains the data
Short Name set.
Relationship Type Required The type of relationship between the data set and client.
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:
Legal Entity Short Name Required Name of the legal entity. Enter a name that other Axon users can
recognize easily.
Parent Legal Entity Short Optional Name of the parent legal entity if the legal entity belongs to a
Name hierarchy.
Name
Short Name set.
Relationship Type Required The type of relationship between the data set and legal entity.

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:
Product Parent Name Optional Name of the parent product if the product belongs to a
hierarchy.
Name
Short Name set.
Relationship Type Required The type of relationship between the data set and product.
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:
Parent Client Name Optional Name of the parent client that you want to create.
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:
Source Glossary Ref. Optional A unique identifier for the source glossary.
Source Glossary Name Optional Name of the source glossary.
Source Parent Glossary Optional Name of the parent source glossary. The source glossary parent
Name 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 Optional Name of the parent target glossary. The target glossary parent
Name name must exist in Axon.
glossaries.
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:
hierarchy.
must exist in Axon.
Relationship Type Required The type of relationship between the glossary and product.

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:
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 Source System Optional Short name of the system from which the information flows
Short Name out.
Interface Target System Optional Short name of the system to which the information flows in.
Short Name
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:
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
hierarchy.
Relationship Type Required The type of relationship between the geography and legal entity.

Local Data Quality Rule X Technical Reference
Download the Local Data Quality Rule X Technical Reference relationship template to bulk upload the
relationships between a local data quality rule and technical reference.
The following table describes the fields of the Local Data Quality Rule X Technical Reference relationship
template:
Ref. Optional The unique identifier for the local data quality rule.
Rule Name Optional Name of the local data quality rule.
Technical Rule Reference Required A reference link that associates the Attribute object and rule in
Informatica Data Quality.
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:
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
Employee Last Name Optional Last name of the employee. Specify the name as it is recorded
Employee LAN ID Optional Network ID of the employee.

LAN ID might be required if you want to enable Single Sign-On
authentication.
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:
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.
Attribute Name Optional Name of the attribute. Enter a name that other Axon users
Name attribute.
Relationship Type Required The type of relationship between the policy and attribute.
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:
recognize easily.
hierarchy.
Business Area Name Required Name of the business area. Enter a name that other Axon

Parent Business Area Optional Name of the parent business area if the business area
Name 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:
recognize easily.
Parent Policy 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.
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:
recognize easily.
hierarchy.

Data Set Name Optional Name of the data set. Enter a name that other Axon users
Name
Relationship Type Required The type of relationship between the policy and data set.
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:
Description Optional Description about the relationship between the policy and
glossary.
recognize easily.
Parent Policy Name Optional Name of the parent policy if the policy belongs to a hierarchy.
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:
recognize easily.

Parent Policy Name Optional Name of the parent policy if the policy belongs to a hierarchy.
Parent Legal Short Name Optional Short name of the parent legal entity if the legal entity
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:
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 Parent Policy Optional Name of the parent of source policy. The parent name must
Name 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.
policies.

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:
process.
Policy Name Optional Name of the policy. Enter a name that other Axon users
hierarchy.
Process Name Optional Name of the process. Enter a name that other Axon users
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:
hierarchy.
hierarchy.
Relationship Type Required The type of relationship between the policy and product.

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:
project.
recognize easily.
Parent Policy 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.
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:
recognize easily.
hierarchy.
System Short Name Required Short name of a system or an acronym that other Axon users
can recognize easily for a system.
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:
recognize easily.
hierarchy.
recognize easily.
Name attribute.
Relationship Type Required The type of relationship between the process and attribute.
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:
recognize easily.
hierarchy.
Relationship Type Required The type of relationship between the process and client.

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:
recognize easily.
Data Set Name Optional Name of the data set. Enter a name that other Axon users can
recognize easily.
Name
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:
Description Optional Description of relationship between the process and glossary.
must exist in Axon.
recognize easily.
Relationship Type Required The type of relationship between the process and glossary.
- 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:
recognize easily.
hierarchy.
Relationship Type Required The type of relationship between the process and legal entity.
- 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:
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.
recognize easily.
Parent Process Name Optional Parent of the process.
Predecessor Process Ref. Optional A unique reference identifier for the predecessor process.
Predecessor Process Optional Name of the predecessor process.

Name
Predecessor Parent Optional Parent of the predecessor process.

Process Name

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:
Product Parent Name Optional Name of the parent product if the product belongs to a hierarchy.
recognize easily.
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:
recognize easily.
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:
recognize easily.
Interface Source System Optional Short name of the system from which the information flows out.
Short Name
Interface Target System Optional Short name of the system to which the information flows in.
Short Name
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:
Product Ref. Optional A unique reference identifier for the product.
Product Name Optional Name of the product. Enter a name that other Axon users
hierarchy.
Business Area Name Required Name of the business area. Enter a name that other Axon
Business Area Parent Optional Name of the parent business area if the business area
Name belongs to a hierarchy.
Relationship Type Required The type of relationship between the product and business
area.

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:
Product Name Optional Name of the product. Enter a name that other Axon users can
recognize easily.
hierarchy.
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.
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:
Product Name Optional Name of the product. Enter a name that other Axon users can
recognize easily.
hierarchy.
Parent Legal Short Name Optional Short name of the parent legal entity if the legal entity
Relationship Type Required The type of relationship between the product and legal entity.

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:
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.
recognize easily.
Attribute System Short Optional Name of the system that contains the data set and attribute.
Name
Relationship Type Required The type of relationship between the project and attribute.
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:
recognize easily.
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:
recognize easily.
recognize easily.
hierarchy.
Relationship Type Required The type of relationship between the project and capability.
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:
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.

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:
recognize easily.
Name
Relationship Type Required The type of relationship between the process and data set.
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:
Description Optional The description about the relationship between the glossary and
project.
must exist in Axon.
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:
Description Optional The description about the relationship between the project and
process.
recognize easily.
hierarchy.
recognize easily.
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:
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.
hierarchy.
recognize easily.

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:
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 Optional Name of the parent of source project. The parent name must
Name 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 Optional Name of the parent of target project. The parent name must
Name exist in Axon.
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:
Description Optional Description about the relationship between the project and
system.

recognize easily.
hierarchy.
Relationship Type Required The type of relationship between the project and system.
- 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:
Regulation Ref. Optional A unique reference identifier for the regulation.
Regulation Name Optional Name of the regulation. Enter a name that other Axon
Parent Regulation Name Optional Name of the parent regulation if the regulation belongs to
a hierarchy.
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:
a hierarchy.
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:
a hierarchy.
Project Name Optional Name of the project. Enter a name that users can
recognize easily.
hierarchy.
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:
Regulator Reg Reference Required Reference identifier for the relationship between a
regulator and regulation.
a hierarchy.
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:
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 Optional Parent object of the regulatory theme.

Name
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:
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:
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.
Standard Data Quality Rule X Technical Reference

Download the Standard Data Quality Rule X Technical Reference relationship template to bulk upload the
relationships between a standard data quality rule and technical reference.
The following table describes the fields of the Standard Data Quality Rule X Technical Reference relationship
template:
Ref. Optional The unique reference number for the standard data quality rule.
Automation Optional The option to automatically generate a local data quality rule.
- True. Generates local data quality rules automatically.
- False. Does not generate local data quality rules
automatically.

Rule Name Optional Name of the standard data quality rule.
Technical Rule reference Required The Option to link the standard rule with a rule in Informatica
Data Quality.
You can link standard rule to a single technical rule reference in
Informatica Data Quality.
Glossary Reference List Optional A comma-separated list that contains unique reference values
for the glossary.
Note:
- If technical rule reference has multiple input parameters, you
must enter all the Glossary reference values.
- If the technical rule reference has a single input parameter,
Axon updates reference value for the glossary that is
associated with the standard data quality rule.
- The bulk upload fails, if the Glossary reference values
contains special character ,.
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:
Client Parent Name Optional Name of the parent client if the client belongs to a hierarchy.
Relationship Type Required The type of relationship between the system and client.

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:
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 Name of the data set that acts as a strategic data set.
Strategic Data Set System Optional Short name of the system that contains the data set that
Short Name acts as a strategic data set.
Relationship Type Required . The type of relationship between the system and glossary.
- 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:
System Short Name Required Name of the system. Enter a name that other Axon users can
recognize easily.
Legal Entity Short Name Required Name of the legal entity. Enter a name that other Axon users can
recognize easily.
Parent Legal Entity Short Optional Name of the parent legal entity if the legal entity belongs to a
Name 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:
hierarchy.
System Short 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 Optional The type of relationship between the product and the legal
Type entity. Select Risk Owning Entity or Booking Entity.
Legal Entity Short Name Optional Short name of the legal entity.
Legal Entity Parent Name Optional Name of the parent legal entity if the legal entity belongs to a
hierarchy.
System X Resource
Download the System X Resource relationship template to bulk upload the relationships between an Axon
system and Enterprise Data Catalog resource.
When you bulk upload the System X Resource relationship template, Axon validates the operation based on
the following details:
• The Enterprise Data Catalog instance is configured, available, and running.

• The resource name and resource identifier are present in Enterprise Data Catalog.
• You have the required permissions to access the resources in Enterprise Data Catalog.
The following table describes the fields of the System X Resource relationship template:
System Short Name Required Short name of a system that other Axon users can recognize
easily.
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.
If a role assignment is configured for a facet in the Admin Panel, enter the email address of the user that is
assigned to a role from the predefined list.
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:
User Email Optional Unique email address of the user. Axon sends emails to this
email address.
Role Templates 127

User Last Name Optional Last name of the user. Specify the name as it is recorded in the
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:
Capability Name Optional Name of the capability.
Parent Capability Name Optional Parent name of the capability if the capability belongs to a
hierarchy.
email address.

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:
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.

email address.

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:
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.
email address.

You can select the Committee Chair role.
Role Templates 129

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:
Ref. Optional A unique reference identifier for the data set.
Name Optional Name of the data set.
System Short Name Optional Name of the system that the data set belongs to.
email address.

- 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:
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.
email address.


- 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:
Interface Ref. Optional A unique reference identifier for the system interface.
Interface Source System Optional System from which the information flows out.
Short Name
Interface Target System Optional System to which the information flows in.
Short Name
email address.

- Interface Owner
- Interface Steward
Role Templates 131

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:
Legal Entity Name Required Short name of the legal entity. Enter a name that other Axon
Legal Entity Parent Name Optional Parent name of the legal entity that you want to create.
email address.

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:
Ref. Optional A unique reference identifier for the policy.
Name Optional Short name of the policy. Enter a name that users can recognize
easily.
Parent Name Optional Parent name of the policy that you want to create.
email address.


- 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:
Ref. Optional A unique reference identifier for the process.
Name Optional Name of the process.
Parent Name Optional Parent name of the process.
email address.

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:
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.
Role Templates 133

email address.

- 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:
recognize easily.
Project Parent Name Optional Parent name of the project that you want to create.
email address.

- 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:
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.
email address.

- 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:
Short Name Required Short name of a system that other Axon users can recognize
easily.
email address.
User Last Name Optional Last Name of the user. Specify the name as it is recorded in the
Role Templates 135


- 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.
Category
Download the Category template to bulk upload data collection categories to Axon Data Marketplace. You
can create a new categorie or update an existing category.
Upload New Items

The following table describes the fields of the Category template that you can use to upload new items:
ID Required A unique reference identifier for the category.
Name Required Name of the category
Status Required Status of the category.

- Active
- Inactive
Description Optional Description of the category.
Parent ID Optional Parent ID of the category in the category hierarchy.

The following table describes the fields of the Category template that you can use to update items:
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.

- Active
- Inactive
Description Optional Description of the category.
Parent ID Optional Parent ID of the category in the category hierarchy.
Consumer Access
Download the Consumer Access template to bulk upload consumer access details to Axon Data Marketplace.
You can create a new consumer access template.
Upload New Items

The following table describes the fields of the Consumer Access template that you can use to upload new
items:
Data Collection Customer Required A unique reference identifier for the data collection.
Facing ID Reference
Consumer Required A consumer user reference identifier.
Status Required Status of the data collection. The status must be active.
Target Name Required Name of the delivery target for the data collection .
Target Location Required Name of the delivery location for the data collection.
Format Required Name of the delivery format for the data collection.
Method Required Name of the delivery method for the data collection.
Approver Optional An approver user reference identifier.
Data Marketplace Templates 137

Data Collection
Download the Data Collection template to bulk upload data collections to Axon Data Marketplace. You can
create a new data collection or update an existing data collection.
Upload New Items

The following table describes the fields of the Data Collection template that you can use to upload new
items:
Name Required Name of the data collection.
Description Optional Description of the data collection.
Status Optional Status of the data collection. You can select one of the following statuses:
- Published
- Unpublished
Data Set ID Optional A comma-separated list of the data sets.
Owner Optional A comma-separated list of the data collection owners.
Technical Owner Optional A comma-separated list of the data collection technical owners.
Category ID Required The reference ID of the category to assign to the data collection.
Policies Optional A comma-separated list of policies to link to the data collection.
Prefix Optional The prefix that you want to assign to the data collection reference identifiers.
Delivery Option Optional A comma-separated list of delivery options for the data collection.

The following table describes the fields of the Data Collection template that you can use to update items:
Name Required Name of the data collection.
Data Collection Reference Required The reference ID for the data collection.
Description Optional Description of the data collection.
Status Optional Status of the data collection. You can select one of the following options:
- Published
- Unpublished
Data Set ID Optional A comma-separated list of the data sets.
Owner Optional A comma-separated list of the data collection owners.
Technical Owner Optional A comma-separated list of the data collection technical owners.

Category ID Required The reference ID for the category to assign to the data collection.
Policies Optional A comma-separated list of policies to link to the data collection.
Prefix Optional The prefix that you want to assign to the data collection reference identifiers.
Delivery Option Optional A comma-separated list of delivery options for the data collection.
Data Marketplace Templates 139

Index
A O
assign segment object templates
bulk upload 15 business and change 21
data and technology 55
Data Marketplace 136
B organizational 33
regulatory 48
bulk delete
relationships 16
roles 17
bulk update template
R
ID 20 relationships
bulk upload bulk delete 16
object 10 roles
relationship 10 bulk delete 17
role 10
segment 14, 15
templates 11, 19
bulk upload templates
S
object templates 21, 33, 48, 55, 136 segment
relationship templates 88 bulk upload 14
role templates 127
140

AX 72 BulkUploadReferenceGuide en

Uploaded by

Copyright:

Available Formats

AX 72 BulkUploadReferenceGuide en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AX 72 BulkUploadReferenceGuide en

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What templates are described in the document?

What templates are described in the document?

Informatica® Axon Data Governance

Bulk Upload Reference Guide

See patents at https://www.informatica.com/legal/patents.html.

Publication Date: 2021-04-30

Chapter 1: Bulk Upload Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2: Bulk Upload Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

As an Informatica Network member, you have the following options:

• Search the Knowledge Base for product resources.

Informatica Knowledge Base

Informatica Product Availability Matrices

Informatica Global Customer Support

Bulk Upload Data

• Bulk Upload Data Overview, 10

Bulk Upload Data Overview

• Add new objects, relationships, and roles to Axon.

Bulk Uploading Data

Select Template File

Bulk Uploading Data 11

12 Chapter 1: Bulk Upload Data

Change Request Guidelines for Bulk Uploading Data

Requirements for Automatic Change Requests

Guidelines for Cancel on Warning Option

Bulk update objects that specify admin user as stakeholder

Bulk update objects that specify WebUser as stakeholder

Bulk Uploading Data 13

You cannot assign a segment to the following types of objects:

14 Chapter 1: Bulk Upload Data

1. In the Axon toolbar, click Create > Upload from file.

Bulk Deleting Relationships

1. In the Axon toolbar, click Create > Upload from file.

16 Chapter 1: Bulk Upload Data

Bulk Delete Roles

Bulk Deleting Roles

1. In the Axon toolbar, click Create > Upload from file.

Bulk Delete Roles 17

18 Chapter 1: Bulk Upload Data

Bulk Upload Templates

• Bulk Upload Templates, 19

Bulk Upload Templates

• Add new objects, relationships, and roles to Axon.

• Business & Change

20 Chapter 2: Bulk Upload Templates

Business & Change Object Templates

You can bulk upload the following types of objects:

Upload New Items

Field Type Description

Description Required Description of the committee.

Business & Change Object Templates 21

Classification Required Classification of the committee.

Axon Status Optional Status of the committee in Axon.

Lifecycle Required Stage of the committee in the production lifecycle.

Committee Type Required Type of the committee.

User Lan ID Optional Network ID of the user.

Governance Role Optional The role of the user.

Update Existing Items