The following are items of note concerning keywords:
Encrypted keywords are not supported in the Classic Client interface (Core-based Workflow does support Keyword Type encryption).
-
Within Workflow life cycles, users with rights to tasks that modify keywords can modify restricted Keyword Values upon task execution, regardless of their restricted user rights.
-
Within Workflow life cycles, users with rights to tasks that modify keywords can modify encrypted Keyword Values upon task execution, regardless of their encrypted keyword user rights.
-
When using E-Forms that display user interaction, encrypted keywords are displayed masked when the user does not have rights to view encrypted Keyword Values and the user cannot change values that they do not have rights to regardless of the user's ad hoc task rights.
-
Actions in Workflow that add or change Keyword Values to a document do not adhere to the Keyword Must Be Unique and Keyword Must Exist Keyword Type settings. Pay close attention when configuring these actions.
-
If an action changes a Keyword Value to a value that is larger than the allowed length, the value may be truncated, ignored, or not saved.
-
Actions that involve comparing keywords configured for Case Sensitive Searching must match the keywords exactly or the desired results may not be achieved. Pay close attention to any configured Case Sensitive settings in your system. Property names are not case sensitive in the core-based clients.
-
Actions with the work with AutoFill Keyword Sets are not compatible with external AutoFill Keyword Sets.
-
If you will be using Workflow AutoFill Keyword Set actions, you must associate your AutoFill Keyword Sets at the Document Type level.