|
SharePoint Condition |
Description
Monitors for the occurrence of a SharePoint event and evaluates as TRUE upon occurrence. The SharePoint condition can be used as one of the following workflow elements:
-
Trigger element - Launches a workflow when the monitored condition evaluates to TRUE.
-
Wait element - Suspends workflow execution until the monitored condition evaluates to TRUE.
-
Conditional element - Determines the course of a workflow depending on whether or not the monitored condition evaluates as TRUE.
Practical Usage
Frequently used to monitor a SharePoint site or list for a specific action or event to take place (for example, item added or deleted, workflow started, group deleted, etc.).
Parameters
General
Property | Type | Description |
---|---|---|
Site URL | String | The SharePoint site URL in which to monitor. |
Scope | Options | The SharePoint range to monitor. The available
options are:
|
List title | Text | The title of the list to monitor. This parameter is available only if the Scope parameter is set to List. |
Events
(Selecting multiple options will cause this condition to evaluate each selection as an OR statement as opposed to an AND statement. In this case, it will react to the first event that occurs.)
Property | Type | Description |
---|---|---|
Supported in SharePoint 2007 or higher | ||
Item added | Yes/No | If selected, the condition will monitor for items to be added to the site/list. |
Item Updated | Yes/No | If selected, the condition will monitor for items to be updated in the site/list. |
Item Deleted | Yes/No | If selected, the condition will monitor for items to be deleted from the site/list. |
Item checked in | Yes/No | If selected, the condition will monitor for items to be checked in the site/list. |
Item checked out | Yes/No | If selected, the condition will monitor for items to be checked out of the site/list. If you check out an item, you will reserve it for your use so that others cannot change it while you are working on it. |
Item unchecked out | Yes/No | If selected, the condition will monitor for items to be unchecked out (also known as discarded checkout) from the site/list. You can uncheck out an item if you want it to go back to the way it was before you checked it out. This will undo all of the changes that you made to the item. |
Item file moved | Yes/No | If selected, the condition will monitor for a file that is represented by an item from a document library to be moved from the site/list. |
Item attachment added | Yes/No | If selected, the condition will monitor for an attachment to be added to a list item in the specified site/list. |
Item attachment deleted | Yes/No | If selected, the condition will monitor for an attachment to be deleted from a list item in the specified site/list. |
Field added | Yes/No | If selected, the condition will monitor for a field to be added to the site/list. |
Field updated | Yes/No | If selected, the condition will monitor for a field to be updated in the site/list. |
Field deleted | Yes/No | If selected, the condition will monitor for a field to be deleted from the site/list. |
Supported in SharePoint 2010 or higher | ||
Workflow started | Yes/No | If selected, the condition will monitor for a SharePoint workflow to be started from the site/list. |
Workflow postponed | Yes/No | If selected, the condition will monitor for a SharePoint workflow to be postponed from the site/list. |
Workflow completed | Yes/No | If selected, the condition will monitor for a SharePoint workflow to be completed from the site/list. |
List added | Yes/No | If selected, the condition will monitor for a list to be added to the site/list. |
List deleted | Yes/No | If selected, the condition will monitor for a list to be deleted from the site/list. |
Supported in SharePoint 2013 or higher | ||
Group added | Yes/No | If selected, the condition will monitor for a group to be added to the specified site/list. |
Group updated | Yes/No | If selected, the condition will monitor for a group to be updated in the specified site/list. |
Group deleted | Yes/No | If selected, the condition will monitor for a group to be deleted from the specified site/list. |
Group user added | Yes/No | If selected, the condition will monitor for a user to be added to a group in the specified site/list. |
Group user deleted | Yes/No | If selected, the condition will monitor for a user to be deleted from a group in the specified site/list. |
Role definition added | Yes/No | If selected, the condition will monitor for a role definition (or permission level) to be added to an item in the specified site/list. A role definition is a collection of rights bound to a specific item. |
Role definition updated | Yes/No | If selected, the condition will monitor for a role definition (or permission level) to be updated in the specified site/list. |
Role definition deleted | Yes/No | If selected, the condition will monitor for a role definition (or permission level) to be deleted from an item in the specified site/list. |
Behavior
The Behavior tab properties dictate how the system should react upon the occurrence of a condition. These properties are significant in determining whether the condition should act as a trigger object (used to fire off workflow execution), wait object (used to suspend workflow execution) or conditional (decision making) object.
Additional Notes
AMTrigger
When the Key event is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the Database - SQL query activity and Email action. The fields that AMTrigger generates can be used to determine properties of the object that caused the workflow to launch, such as the type of trigger, when the trigger was activated and what system event or condition took place to activate the trigger. Along with a collection of global AMTrigger fields that are created and populated by every instance of AMTrigger, a unique set of AMTrigger fields exclusive to each Automate trigger are created as well.
To view AMTrigger values exclusive to the Process condition, see AMTrigger - Process.
AMCondition
When the Process condition is used in the middle of a workflow as wait or conditional object, it automatically creates an AMCondition dataset. Similar to AMTrigger, the fields that AMCondition generates can be used to determine properties of the object that caused the condition to activate. Along with a collection of global AMCondition fields that are created and populated by every instance of AMCondition, a unique set of AMCondition fields exclusive to each Automate condition are created as well.
To view AMCondition values exclusive to the SharePoint condition, see AMCondition - SharePoint.