For the July mission, I asked the community What's your favorite workflow action and why? And for everyone who's interested, I've listed the actions mentioned and also why people love them so. Perhaps you haven't used one of these before. Are you inspired?
|Favorite Workflow Action||What the community has to say|
You can bundle a collection of actions in an action container which can then be collapsed and expanded to make your workflow design more consistent and clean.
With this action you can assign a task to one or more users, and then request a specific action such as all must agree, or first response applies, or majority choose the outcome. The list of outcomes are chosen by the workflow designer.
Allows the workflow to perform basic string concatenations for use within other actions at runtime.
Allows a time period to be added or subtracted from a date to create a new date.
Allows the workflow to make a call to a SOAP web service method.
Forces all existing batched operations to be committed. Batched operations are operations performed by workflow actions that do not commit immediately.
Allows the workflow to copy items from the current library to another library within SharePoint.
|Looping/ Run If/ For Each family|
Perform a regular expression on a block of text. You can perform an operation on the specified string using a regular expression (pattern), including replacing, splitting, and extracting strings, as well as checking for a match.
This action allows you to request one or more users to process an approval as part of the workflow.
Assigns a task to a specified user. To complete the task, the user must provide a value for each data item specified in the action configuration.
The state machine action provides a construct where you can define the number of states a workflow can be in, the workflow will continue to move between these states based on approval tasks, and until you tell the workflow to end.
This action will direct the flow of actions based on the value of a single variable. A branch for each possible defined value is used to determine which branch of workflow actions will run.
With this action you can send an HTTP request to a URL, and perform a variety of requests, including GET, POST, PUT, SOAP 1.1, SOAP 1.2, and customized request methods. You can also use this action to call ASMX web services.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.