Sunday, May 26, 2013

SharePoint Server 2010 Visual Studio Custom Workflow Activities

Code—The code activity allows you to drop code into the
template. If you don’t want to go through the process of
creating a custom activity, or you don’t think the code will
be reused, this activity may be your best choice.


If-else—You’ve guessed it, the if-else activity allows you to
make logical decisions in the workflow. You can add additional
else-if branches. Each branch requires a method
that calculates whether the condition is met or not.


Parallel—The parallel activity allows you to run two or
more trunks of activities in parallel. Otherwise, the activities
would have to run in sequence.




Terminate—The terminate activity terminates the
workflow.



While—A while activity is used for looping. Activities
inside the workflow can repeat themselves over and over
again; at the same time, the while condition is still true.




CopyItemActivity—This CopyItemActivity activity allows you to create a copy of a
list item or document in another document library or list. This activity is useful for
archiving or moving documents.


CreateTask—The CreateTask activity creates tasks in task lists. See chapter 10
on task processing for more information.


OnWorkflowModifed (and EnableWorkflowModification)—OnWorkflowModified
activity responds when the workflow is modified. With Workflow Modifications,
users can change the behavior of a workflow after it has already started (see
chapter 9 on workflow forms for more information).




sendEmail—The sendEmail activity uses the exchange server specified in Share-
Point Central Administration to send emails to users.


SetState—The SetState activity is used to set the state of the workflow. When a
workflow starts, a new column is created in the list or library. Instead of the default
In-progress or Completed, you can define custom states to show in this column.


The LogToHistoryListActivity activity logs to
the workflow’s history list. You may want to use other
logging mechanisms such as logging to the Event log
on the Server. This is helpful when you have errors
that you may not want end users to see.
 

No comments:

Post a Comment