Run If (2024)

This help site is based on the available in-product assistance as of December 2016. Please note that this site is provided as a convenience and it does not go through rigorous layout testing.

This workflow actionsets a condition to dictate the logic that is processed at runtime. E.g. the workflowactions contained within the Run If action will only execute if the condition evaluates to true.

Note:Any actions within theRun if action will run in the same context that the Runifaction is configured to.

This actionissimilar tothe Set a condition action.

To use the workflow action:

Alternatively

  • Left-clicking the pearl, mouse-over Insert Action and then the Categories to reveal the actions, click the required action from the list.

To change the settings used by the action:

  • On the action’s title click the down arrow to activate a drop-down

  • Select Configure; OR

  • Double-click the action's icon.

For more information on the other options in the drop-down, please refer to the Getting started with the Nintex Workflow designer.

Run If (1)

Action Settings

Condition

There aretwelve types of conditions that can be used here. These are:

  • If current item field equals value

This condition typeevaluates if an individual field of the current item matches or compares to a certain value/column.

  • If any value equals value

This condition allows the use of two fields, two workflow variables or two lookups to compare at runtime.

  • Title field contains keywords

This conditionallowsa comparison to beperformed that determines if the item's title contains certain specific words.

  • Modified in a specific date span

This condition evaluates to true if the current item is modified between two specified dates.

  • Modified by a specific person

This condition evaluates to true if the item has been modified by a specific person. The username is case sensitive.

Once the name has been entered clickCheck name button to validate user.

  • Person is a valid SharePoint user

This condition checks if the specified user is a member of the SharePoint site.

  • Created in a specifcdate span

This condition checks if the item was created between the specified dates.

If manually entering information, ensure that the date format matches that used in the SharePoint environment.

  • Created by a specific person

This condition checks if an item was created by a specific user.

Once the name has been entered click theCheck name button to validate user.

  • The file type is a specific type

This condition checks if the file type extension of the current item is of the specified type.

  • The file type in a specific range kilobytes

This condition checks if the file size of a document is between the specified sizes, in kilobytes.

The followingtwo conditions are available whenrunning the workflow action as theworkflow owner (impersonation):

  • Check list item permissions

This condition checks if the permissions of a specified user matches or is higher than the specified permission level provided for an item in a list. It does not check that the users have specific permission levels. A user can be a single user, multiple users or a group. For the condition to evaluate as true, the user/s must have at least the permissions that the permission levels provide.

  • Check list item permissions levels

This condition checks if permission levels of a specified user matches or is higher than the permission levels for an item within this list. A user can be a single user or multiple users but cannot be a group for this condition. For the condition to evaluate as true, the users must have the permission levels specified in the condition.

There are manyoperators that can be used within this condition, e.g.equals, not equals to, greater than, less than, is empty, contains etc. Enter datamanually into the text box or uselookups to dynamically build the values at run time.

AddConditions

Multiple conditionscan be constructed by using theAdd conditionoption.

SpecifyAndorOrbetween thecondition statements.

Conditions are evaluated in order, from first to last condition (top to bottom). For example, the first two conditions are evaluated, and then that result is evaluated against the next condition. This pattern continues until a final result is reached.​

Related Topics

Run If (2024)
Top Articles
Latest Posts
Article information

Author: Chrissy Homenick

Last Updated:

Views: 6518

Rating: 4.3 / 5 (54 voted)

Reviews: 93% of readers found this page helpful

Author information

Name: Chrissy Homenick

Birthday: 2001-10-22

Address: 611 Kuhn Oval, Feltonbury, NY 02783-3818

Phone: +96619177651654

Job: Mining Representative

Hobby: amateur radio, Sculling, Knife making, Gardening, Watching movies, Gunsmithing, Video gaming

Introduction: My name is Chrissy Homenick, I am a tender, funny, determined, tender, glorious, fancy, enthusiastic person who loves writing and wants to share my knowledge and understanding with you.