Determining Requirements
In the <requirements> section, you can determine the requirements that need to be met in order for the transition to take place. The section may be included under <transition>, but is optional. If a requirement is determined, but is not met, the respective transition will not be performed.
All <requirements> may contain the "workItemTypeFilter" attribute so that not all work items are checked.
- Possible values of the "workItemTypeFilter" attribute:
- SuggestNewTerm
- SuggestNewTermToExistingEntry
- RequestTranslation
- SuggestTermChanges
- SuggestEntryChanges
Multiple values are permitted and must be separated with a semicolon.
Element name | Description |
<requireComment> | Determines whether a comment needs to be added when the transition is performed. Example: <transitionname='Accept'from='Suggested'to='Accepted'><requirements><requireCommentworkItemTypeFilter="SuggestNewTerm;SuggestTermChanges"/></requirements></transition> |
<requireLanguage> | Determines the languages in which terms need to exist for this transition. Example: <transitionname='Accept'from='Suggested'to='Accepted'><requirements><requireLanguages>1033;de-DE</requireLanguages></requirements></transition> |
<requireParameters> | Can be used to offer the user a selection of certain workflow parameters (e.g. languages to be translated in the further course of the workflow). For the setup, we recommend getting the assistance of Across Services. If you are interested, please contact your account manager at Across. |