Let's explore the tagging of workflows. Tagging introduces the same kind of tagging you're familiar with from vCenter server. Tagging allows you to add tags to Orchestrator objects and search for them.
Tagging involves the following procedures.
Let's start by tagging a workflow manually.
glbTest
and then press Enter.author
, then press Ctrl + S and then enter the value for the tag, such as Daniel
.
You can tag a workflow using a workflow.
Tags have been integrated into Orchestrator since 5.5.1. There are two types of tags: global tags and private tags. A global tag is visible to all users whereas non-global (private) tags are only visible to the user who places the tag.
Tags are not stored with the workflows. Importing and exporting a workflow to a different Orchestrator will not preserve the tags; however, several websites state that this is the case.
The JavaScript behind the tags is straightforward:
JavaScript tags |
Function |
|
This allows tagging an object with a global tag. |
|
This allows tagging an object with a private tag. |
|
This allows listing an object's global tags. |
|
This allows listing an object's private tags. |
|
This allows finding an object by its tags. |
|
This allows untagging a global tag from an object. |
|
This allows untagging a private tag from an object. |
For using vCenter tags see recipe Custom Attributes and Tags (vAPI) in Chapter 12, Working with vSphere.