Tag repository

understand the tag repository as a single source for accessing a categorized set of tags, minimizing duplicate tags and administrator confusion the tag repository enables users to add or manage tags through four main capabilities add tag values from active tags created on the tag definition page create a new key or value pair directly within the repository import tags in bulk from external sources store tags pushed by other applications or services tags created directly from the tag repository are labeled non compliant because they lack definitions however, the administrator can still use these tags and update their definitions later on from the tag definitions docid\ bk pjyh9cgzyhqfxthev3 page viewing the tag repository all tags added to the repository are uniformly applicable at an account level, making the system straightforward to understand the tag repository only has active tag keys the tag repository page displays all the tags for the applications or services used under the used by column, you can view all associated tags with one or more applications to identify governed tags, a column has been added to indicate whether a tag has a definition (tags formally defined with the necessary details to specify how they should be used, values they can take, or overall purpose) non compliant tag values with the defined constraints are also displayed in the tag definition page click the view details option of a specific tag to view the latest tag editor, creator and creation date method 1 add tag values from active tags created on the tag definition page the system is designed to prevent errors if you, as the tag administrator, add tag values that are outside the constraints established on the tag definitions page, the system will display an error message and stop the addition of such values, ensuring the integrity of the tag repository to add a tag value go to the tag repository go to the page and look for the tag key that requires an update click the view details option and select add tag values add all the required values, separated by commas the set constraints are displayed to ensure that the values added are compliant an error message will be displayed for non compliant values once all values are added, click the add tag(s) button the window closes, and a new message displays on the page “tag value(s) successfully added you have successfully added values \[name], \[name] to key \[name]” to delete a tag value select the tag that requires the update click the expandable icon to review the definition of compliance for each value select the value that needs to be deleted and click the options icon select the delete option a new window pops up requesting to confirm this action click the delete value button to confirm the deletion otherwise, click cancel once deleted, the window closes, and a message displays “tag value \[name] deleted successfully you have successfully deleted tag value \[name] from the tag \[name]” method 2 create a new key or value pair directly within the repository an administrative control capability at an account level allows the enabling or disabling of the creation of tags directly to the tag repository for additional details, see administrative control docid\ jcdr38ddartltzua kfgv if you create a new tag using a tag key already in the repository but without a tag value, the system will suggest similar tag keys already available, ensuring consistency and avoiding duplication to add a tag go to the tag repository page and click the add tags button a new window opens select whether you will add new tag(s) or bulk add tags enter a unique tag key the tag management allows tag keys with a minimum of 1 character and a maximum of 256 characters, including numbers from 0 to 9 and special characters (!@$% (); / \ ) enter all the tag values associated with the key, separated by commas once you have completed all the information, click the add tags button at the bottom of the window edit tag value once tags are added, they can be managed and edited directly in the repository, with changes validated according to the associated tag definition and automatically reflected where applicable changes are validated according to the associated tag definition and, for enumerated tags, are also reflected in the corresponding tag definition validation behavior varies based on the configuration free input (string) the value must meet the defined rules, and the following message informs the user that the update will be applied in the tag repository the modified tag value will be updated in the tag repository enumerated list users can only select predefined values in an enumerated list, which defines a fixed set of allowed values in the tag definition and does not allow free text the following message informs the user of the impact of the update modifying a tag value updates it in the repository and changes the associated enum in the "environment" tag definition modifying a tag value can affect related tag definitions in the following ways if an administrator modifies a tag value in the tag repository and the corresponding tag definition uses a regex or string constraint, or if no tag definition exists, the system displays the following message "the modified tag value will be updated in the tag repository " if an administrator modifies a tag value in the tag repository and the corresponding tag definition uses an enum list constraint, the system displays the following message "the modified tag value will be updated in the tag repository and the corresponding enum value within the associated tag definition " in this case, the updated tag value in the tag repository is also reflected in the corresponding enum value in the tag definition to delete a tag account administrators can delete tags with no associated resources/applications you will have the option to delete all unused tags or delete an unused tag to delete an unused tag go to the tag repository on the page, look for the tag key that needs to be eliminated click the view details option and select delete to delete all unused tags from the tag repository table, select all the tags that need to be removed and click the delete tags button at the top method 3 import tags to the tag repository page this functionality enables the efficient simultaneous importation of many tags into the repository to create multiple tags account administrators can define account specific tags in bulk and upload a json/csv template to create multiple tags perform the following procedure to import tags in bulk from the tag repository page, select the add tags button a window opens select the bulk add tags option drag, drop, or choose the json or csv file containing the tags you want to import the file should not exceed 1 mb in size the template should have two mandatory fields tag key and tag value otherwise, an alert message displays ' this file is missing the required columns or this file exceeds the 1 mb file size limit ' a sample file is available for reference; download and review this sample before uploading your import file if you no longer want to import the file you selected, click the remove link to discard it if you no longer want to continue with this operation, click cancel to exit this window when the system validates the file, click the upload button to proceed with the import a notification indicates whether the process has been completed successfully or partially the system imports tags that are unavailable in the tag repository to ensure data integrity, the system imports only the value once for duplicate entries you can maintain the same file and continue adding tags as needed when uploading the same file with the latest updates, only the new entries are imported when you import a tag key with the same name as an existing tag, it will automatically follow the current tag rules for example, if you import a tag key called 'team' and 'team' already exists in the tag rules, the new 'team' tag will be compliant any values that do not meet the rules will be marked, indicating they require attention the import report in the notification details the success or failure of each entry in the import file, providing a clear understanding of the import process it also explains the reason for failure (for example, a tag already exists, an empty field, or a duplicate value) method 4 store tags in the tag repository page tags from cloud providers and external sources, such as servicenow, can be sent to the tag repository through various bridge applications and services this integration enables applications to store tag information in the tag repository instead of within their own systems once applications send tag information to the repository, the repository will manage the lifecycle of those tags the used by a column in the tag repository table allows you to view all the applications that currently use a particular tag discovered tags are pushed by the applications to the repository, and any updates, such as new or deleted tag values, will be reflected in the tag repository whenever a push occurs when discovered tags are sent to the repository, any duplicate tag key/value pairs will be reconciled if tags are pushed without an associated tag definition, the tag repository will indicate that the definition is missing for those tags tags that are stored with the same key as an existing tag definition will automatically be considered compliant for example, if a tag is pushed to the tag repository, but a tag key with the same name already has an existing tag definition, then the newly pushed tag will automatically be compliant because a definition for that tag key already exists in such cases, tag keys will not be duplicated however, tags discovered from external sources may not comply with the tag definitions and could be deemed non compliant if an application or service adds a new value to an existing tag key in their respective application, that value will be added to the repository as well for example, if an application or service uses the 'environment' tag from the common tag repository and does not find a suitable value to tag with, it may create a new value called production in this case, the new tag value should also be appended to the list of values for the 'environment' tag in the repository the tag administrator is responsible for ensuring that all values comply with the established rules