The simplest workflow action is the notification action. If a rule is triggered, this notify list will be appended to any existing notify lists (ie: normal notification rules). :

| One time notification when rule is hit
: |

Auto Change Feature

> | Perform AutoChange updates in separate entry.
| (Advantage: Full history in case a field is modified and then automatically changed in the same entry) (Disadvantage: An extra entry will appear every time the autochange rule is used. This can complicate the use of fields (ie:mDateLastModified) in any OGNL formulas.)
> | Archive

Tags

Workflow rules are checked in a sequential list, until a rule is passed without the continue building attribute set, or the list is exhausted. However, when a rule is triggered (Definition passes), the rule may change choose to goto any other tagged rule to continue the sequence from that rule. (automatically turns on ContinueBuilding attribute for this rule) This allows more flexibility when building rules (ie: skipping forwards/backwards). It can also be more meaningful to the administrator.

Goto Tag:

Advanced Auto Change (Auto Creation)

> | Normal: Auto-update fields above update rules matching this workflow rule.
> | Create new item(s) based on selected workflow rule(s). The field action of the selected rule allows you to define the initial values for the new item. |
| Number of items to create (more than 1 will create duplicates of the same item): |
| Maximum number of items to create when triggering this rule from Event Scheduling: |
| Update items matching the selected rule (instead of creating new items): | >
> | Create a new item using autochange fields above as field defaults (setting subject/project is a good idea so issue is seen properly).

CSV Lookup:
Choose a CSV file with two columns, Field A and Field B. Given the current value for Field A, Field B will be automatically updated with the corresponding value retrieved from the CSV file.

CSV Filename: |
Field A: |
Field B: |

Send SOAP Request:
Filling out the fields below will cause FIT to send the XML SOAP message to the specified host URL when this workflow rule is triggered. The SOAPAction field must contain the name of the operation/SOAPAction of the webservice that is being invoked.

Webservice Host URL: |
SOAPAction: |
SOAP Message: | <SUB wfSoapMessage>