Tagging Overview
  • 28 Oct 2020
  • 1 Minute to read
  • Dark
    Light
  This documentation version is deprecated, please click here for the latest version.

Tagging Overview

  • Dark
    Light

Article summary

Overview

A Tag in Decisions works similarly to tags in other search functions. This feature can be applied to Decisions objects like documents, Reports, Forms, and Flows to be easily searchable or quickly identifiable. Similar objects in Decisions can have the same tag applied to them for convenience when grouping these objects.

Tags can be added in multiple ways in Decisions. Their use is encouraged, as they help tremendously in scenarios from managing shared environments to managing large-scale builds. For more complex builds, adding a tag to an object could be conditional based on the Flow logic; thus, the Add Tag step would be used to create a tag as part of the workflow process. This use case requires the Add Tag step to reference the object ID, which can be mapped from the object properties in the Flow. 

Tags can also be added while in most Designer Studios and even from the action menu of most Decisions objects from the Designer Folder. The tag will appear in a global search by name and is defined as a TagList object. The action menu of the TagList object is accessible from the search for tag management or to reference the TagList ID.

Tagging Decisions Objects
For more information on applying tags to other Designer Elements (known as Decisions Objects), please visit our Tagging Decisions Objects article.




Was this article helpful?