Applies to:
- Winshuttle Foundation
UpdateProcessStatusList
Winshuttle Workflow allows you to export workflow data to both SharePoint lists and to predefined database tables. Exporting workflow data to SharePoint lists can be done automatically by specifying the appropriate SharePoint status lists in your workflow, or it can be done explicitly by using an SVAdm operation. Exporting to a database must be done with the SVAdm operation.
In addition:
- SharePoint list field values from your DocEx and FormEx sites can also be incorporated into the SharePoint workflow summary lists.
- Workflow data can be exported to any database for which you have an ADO.NET data provider.
- You can include other SharePoint list field values in your database when exporting
This SVAdm operation takes a current snapshot of all workflow data starting at the specified site and its subsites.
Note: If you want to do only a single site without the subsite(s), omit the -recurse option from the command.
It is safe to run these commands multiple times against the same SharePoint status lists. If an entry already exists for a process or assignment, it will be updated but not duplicated. In addition, you will not get duplicate entries for the same workflow objects.
-verbose: All the operations being performed are shown to the user
Usage
Without configuration file:
svadm -o updateprocessstatuslist -url <URL to the root site to export> -statusurl <URL to the status lists you created above> -statuslist <name of the process status list you created above> -recurse -verbose
With configuration file:
svadm -o updateprocessstatuslist -url <URL to the root site to export> -config <path to your database configuration file> -recurse -verbose
Note:
The approach using the configuration file is similar to the approach without one, but differs in the destination for the data. With this approach, you can specify a database and have your workflow and (optionally) SharePoint data exported to this database. Although the database has a predefined schema that must be used, you can add more database fields to contain additional data from the SharePoint lists.
See below the Options table for a sample configuration file and output
Options
|
Name |
Description |
|
-recurse |
Repeats the operation in the specified SharePoint site hierarchy. |
|
-config |
Path to the database configuration file, e.q. c:\database\mydata |
|
-url |
URL e.g. HTTP://server/site |
|
-statusurl |
http://server/status site |
|
-statuslist |
Name of the list. For example, MyAssignmentStatusList |
Sample output and configuration file
Sample configuration file
<Export>
<ConnectionString>Provider=sqloledb;Data Source=<SQL SERVER MACHINE>\SQLEXPRESS;Initial Catalog=<DB name>;User Id=<username>;password=<password></ConnectionString>
<FieldMaps>
<FieldMap SharePointFieldName="SVProcessName" DatabaseFieldName="SVProcessName"/>
</FieldMaps>
</Export>
This table is created in the database is:
USE [<DB Name>]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[Process](
[SVProcessId] [numeric](18, 0) NULL,
[SVProcessDefinitionName] [varchar](1000) NULL,
[SVProcessDefinitionDescription] [varchar](1000) NULL,
[SVProcessDefinitionCreationDate] [datetime] NULL,
[SVUTCProcessDefinitionCreationDate] [datetime] NULL,
[SVProcessDefinitionAuthor] [varchar](1000) NULL,
[SVProcessDefinitionVersion] [varchar](50) NULL,
[SVProcessDuration] [varchar](50) NULL,
[SVSite] [varchar](1000) NULL,
[SVSharePointListName] [varchar](1000) NULL,
[SVProcessName] [nchar](1000) NULL,
[SVCreationDate] [datetime] NULL,
[SVUTCCreationDate] [datetime] NULL,
[SVDueDate] [datetime] NULL,
[SVUTCDueDate] [datetime] NULL,
[SVCompletionDate] [datetime] NULL,
[SVOriginatorLoginName] [varchar](1000) NULL,
[SVOriginatorFullName] [varchar](1000) NULL,
[SVOriginatorEmail] [varchar](1000) NULL,
[SVReferenceId] [varchar](1000) NULL,
[SVProcessStatus] [varchar](50) NULL,
[SVWasForced] [varchar](1000) NULL,
[SVNote] [varchar](1000) NULL,
[SVUTCCompletionDate] [datetime] NULL,
[SVItemStatus] [varchar](50) NULL,
[Title] [varchar](200) NULL,
[SVFilePath] [varchar](200) NULL,
[SVFolder] [varchar](200) NULL,
[SVFileBaseName] [varchar](200) NULL
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO