Plug-ins
Plug-ins are nodes within a workflow that interact in some way with SharePoint or external environments. Winshuttle Designer provides several plug-ins for commonly-used tasks.
The following sections describe each plug-in type in detail, and give examples of how they can be set.
On this page
Designer plug-ins table
Using the plug-in Sync attribute
All Winshuttle Designer Plug-ins include an attribute called sync. This value indicates whether or not the workflow should continue immediately after executing the plug-in’s code.
- If this value is set to True (the default), the workflow engine will execute the code associated with the plug-in, and once it completes, the engine will automatically mark the node as having been completed, and the workflow will progress.
- If this value is set to False, the workflow engine will not mark the node as having been completed, and thus, the workflow will not proceed. It is then the responsibility of some other processing to mark the node as complete, allowing the workflow to proceed.
An example of where this can be used is in the series of deferred plug-ins included with Designer. A deferred version of a plug-in will insert the plug-in information into a queue, and then later be processed by SVService. The actual plug-in in this case only writes the information to the database, and does not do any of the real processing.
If you leave the sync attribute set to True, the workflow will continue immediately after the database write, since this is all the plug-in does. In this case, the workflow will continue, and at some point in the future, SVService will run and do the underlying processing of the deferred plug-in. This workflow continuation may or may not be what you want, depending on the circumstance. If you set the sync attribute to False, the workflow will wait until SVService has completed the processing before continuing.
NOTE: See the Winshuttle Foundation Help for more information about SVService.
Important Note regarding plug-ins that update SharePoint Lists
Any plug-ins that update SharePoint lists cannot update SharePoint lists that contain columns with Lookup. These fields are considered read-only. Trying to assign a value to a read-only field crashes the process.
Plug-in Variants list
Deployment variants enable you to specify values for parameters that depend upon the deployment profile. Variants can have different values for different profiles.
Example: A solution using the Add Attachment plug-in could have a different value for the file parameter depending upon which profile is used. A Development profile could use a value of D:\ (for the drive location), whereas the Publishing profile could use a value of C: drive.
The following table lists available variants associated with certain Plug-ins.
Plug-in | Variant(s) |
file | |
sourcefile | sourcefolder | destinationfile | destinationfolder | |
directory | site | list | folder | |
site | list | |
directory | site | list | folder | |
site | list | folder | file | |
folderurl | |
rootfolder | |
sitecollectionurl | path | |
directory | site | list | folder | |
site | list | itemid | |
url | |
connectionstring | |
connectionstring | |
site | list | |
filepath | |
site | sitegroup | usersite | userlist | |
connectionstring | |
connectionstring | |
connectionstring | |
site | list | folder | |
fileurl | |
sourcepath | destinationsite | destinationfolder | destinationpath | |
server | connectionstring | |
site,list | |
site | list | itemid | folder | filepath | |
site | list | itemid | folder | filepath | |
site | list | |
site | |
site | list | |
site | list | |
site | list | folder | file | |
wsdl | username | password | domain | |
webservicename | statusfield | waitduration |user | |
file | xslsite | xsldocumentlibrary | xslfile |