Glossary Subdomain

Column	Type	Description
Reference ID	Optional	Reference ID is the unique reference identifier for the asset. If you don't specify a reference ID, the system automatically assigns a unique value to the object. The identifier that you enter here appears in the Reference ID field on the user interface. The system uses the following format to generate a reference ID: <Prefix>-<Number> Example: ‘SDOM-1’, ‘DS-10’ If you specify a reference ID, ensure that the value that you enter doesn’t use the format that is used by the system to automatically generate reference IDs. Type of Entry: Alphanumeric characters, including spaces and special characters. There is no limitation on special characters to be used in names. Example: ‘SUB ID-18’, ‘SD REF:98’
Name	Required	Name for the asset. Consider entering a unique name so that you can distinguish this asset from other assets. Type of Entry: Alphanumeric characters, including spaces and special characters. There is no limitation on special characters to be used in names. Example: ‘Sub Domain_1’, ‘Personal Data’, ‘Corporate Risk Data
Description	Optional	Definition of the asset. The description appears in the asset page. You can enter a detailed description of the asset so that users can understand how it is used in your governance context. Type of Entry: Formatted text. To add an image to the description, use the following syntax: <p><img src=""data:image/png;base64,""> <img src=""data:image/png;base64,""></p> You can add only an image of Base64 format to the description. Other image formats are not supported.
Alias Names	Optional	Alternate names used to refer to the asset. Make sure this name is not the same value as the primary name of asset. You can enter a meaningful business reference name that would help users to identify the asset. Type of Entry: Alphanumeric characters, separated by comma, including spaces and special characters. Example: If the primary name of asset is Wind pipe, you can enter Air pipe, flute as the alias names.
Business Logic	Optional	Description of any business logic that is relevant to the asset. Type of Entry: Formatted text
Examples	Optional	Enter an example that is representative of the asset. Type of Entry: Alphanumeric characters, including spaces and special characters. There is no limitation on special characters to be used in examples. To enter multiple values, use a comma to separate each value. Example: For the subdomain ‘Product Identifer,’ examples can be 'Model Number' or 'Brand Name'
Lifecycle	Optional	Lifecycle status of the asset. The default status is Published. You can select one of the following options: - Draft. Typically used when you are creating a fresh asset. - In Review. Typically used when an asset is being reviewed by stakeholders. Note: Informatica recommends that you don't use a bulk import template to set an asset lifecycle to In Review. - Published. Typically used when an asset has been reviewed and accepted by stakeholders and is ready for use by the wider organization. - Obsolete. Typically used when a business asset is no longer in use. Once an asset is in the Obsolete status, the only other status change allowed is Published.
Security Level	Optional	Security Level of the asset with respect to the sensitivity of the information. This is manually specified for the asset and is suitable only as a governance record. It is not related to data classification or any other system classification. You can select one of the following options: - Public. The assets can be freely used, reused, and distributed without repercussions. - Internal. The assets are strictly accessible to internal employees who are granted access. - Confidential. Confidential assets are mostly protected by laws and access to these assets would require confidential data. - Restricted. Restricted assets, if compromised or accessed without authorization, can cause irreparable damage to the organization.
Operation	Required	Select an operation for the asset. You can select one of the following options: - Create. You want to create the asset. - Update. You want to modify an existing asset. In this case, the Reference ID column is mandatory, along with the columns that you want to modify. For example, if you want to modify the Lifecycle of an asset, you must enter the Reference ID and Lifecycle values, but you don't need to specify values for the other fields, including the fields that are marked as mandatory. - Delete. You want to delete an existing asset. In this case, the Reference ID is the only column that is mandatory. You don't need to specify values for any field, including mandatory fields. Before you delete an asset, ensure that you have removed or deleted all associated relationships and parent-child relationships of the asset.
Parent: Subdomain	Optional	Enter the reference ID or the name of the parent Glossary Subdomain asset. To form a hierarchy use one of the following columns: - Parent: Metric - Parent: Subdomain - Parent: Domain - Parent: Business Term Ensure that you specify only one parent Glossary Subdomain asset.
Parent: Domain	Optional	Enter the reference ID or the name of the parent Glossary Domain asset. To form a hierarchy use one of the following columns: - Parent: Metric - Parent: Subdomain - Parent: Domain - Parent: Business Term Ensure that you specify only one parent Glossary Domain asset.
Stakeholder: Governance Administrator	Optional	User or user group that you want to assign as stakeholders of the asset under the Governance Administrator role. If you enter the name of the user, the user becomes a stakeholder of the asset. If you enter a user group here, all users that belong to the user group become stakeholders of the asset. You can also remove a user or user group as a stakeholder of the asset. Ensure that the users or user groups that you specify are already assigned the relevant user role. For example, to add a user as a stakeholder with the Governance Owner stakeholder role on an asset, the user must already be assigned the Governance Owner user role from the Administrator console. Type of Entry: Email address of the user, first name followed by the last name with a space in between, or last name followed by comma then the first name, without any spaces in between. To enter multiple values, use a semicolon to separate each value. Do not use a space to separate different values. If you want to add a user and a user group as the stakeholders of an asset, ensure that you enter the user names and the user group names in separate rows. To add a stakeholder, you can optionally prefix the term ADD: to the user or user group. To remove a stakeholder, you must mandatorily prefix the term DELETE: to the user or user group. Examples: To add users: “steve@yourorg.com;John Admin;Rhodes,Jane” To add users using the ADD prefix: “ADD:steve@yourorg.com;John Admin;Rhodes,Jane” To remove users using the DELETE prefix: “DELETE:steve@yourorg.com;John Admin;Rhodes,Jane”
Stakeholder: (Stakeholder role name)	Optional	User or user group that you want to assign as stakeholders of the asset under the (Stakeholder role name) stakeholder role. If you enter the name of the user, the user becomes a stakeholder of the asset. If you enter a user group here, all users that belong to the user group become stakeholders of the asset. You can also remove a user or user group as a stakeholder of the asset. Ensure that the users or user groups that you specify are already assigned the relevant user role. For example, to add a user as a stakeholder with the Governance Owner stakeholder role on an asset, the user must already be assigned the Governance Owner user role from the Administrator console. Type of Entry: Email address of the user, first name followed by the last name with a space in between, or last name followed by comma then the first name, without any spaces in between. To enter multiple values, use a semicolon to separate each value. Do not use a space to separate different values. If you want to add a user and a user group as the stakeholders of an asset, ensure that you enter the user names and the user group names in separate rows. To add a stakeholder, you can optionally prefix the term ADD: to the user or user group. To remove a stakeholder, you must mandatorily prefix the term DELETE: to the user or user group. Examples: To add users: “steve@yourorg.com;John Admin;Rhodes,Jane” To add users using the ADD prefix: “ADD:steve@yourorg.com;John Admin;Rhodes,Jane” To remove users using the DELETE prefix: “DELETE:steve@yourorg.com;John Admin;Rhodes,Jane” The template displays all the stakeholder roles that are relevant for the asset. For more information about stakeholder roles, see the Asset Management help.