- Winshuttle Foundation
Manually Exporting Process Data
Exporting Workflow data
- Exporting Workflow data
- Auto export to SharePoint Lists
- Explicit Export to SharePoint Lists
- Explicit Export to a Database
- Manually Exporting Process Data
You can tell the system to explicitly export process and assignment data using the SVAdm tool.
This data can be exported to a Process Status Lists, or to a database.
- Exporting data to a Workflow Process Status List
- Exporting data to Databases (with an ADO.NET connector.)
Exporting data to a Workflow Process Status ListBack to top
- To export to a Workflow Process Status list, create a list with that type in a new or existing SharePoint site.
- Open the command prompt and navigate to \Program Files\Sharevis\bin
- Run the following command:
svadm -o updateprocessstatuslist -url http://<your site>/<your site path> -statusurl http://<your site>/<your status site> -statuslist <your status list's name>
Specifies the site from which you want to collect process data.
Specifies the site where you want to put the process data.
Specifies the list where you want to put the process data.
The following example will collect all of the process data from the Human Resources site http://spserver/hr and place it in a list named HR Process Data on the site /statusrollup:
svadm -o updateprocessstatuslist -url http://spserver/hr -statusurl http://spserver/statusrollup -statuslist "HR Process Data"
This will collect process data from only the /hr site itself. If you have subsites under your Human Resource site that you also want to include, use the -recurse option.
For example, this command will collect all process data from all subsites under /hr:
svadm -o updateprocessstatuslist -url http://spserver/hr -statusurl http://spserver/statusrollup -statuslist HR Process Data –recurse
Exporting data to DatabasesBack to top
Another option when manually exporting data is to export your data to a database via its ADO.NET connector. Workflow provides a database script for creating the correct tables in SQL Server, and this script can be modified to work with other databases. This script creates two tables: Assignment and Process for holding the respective data. Before exporting Workflow process data, you must use the script to create the tables in your database.
To use SVAdm to export process data to a database, you must provide a configuration file that contains information the system needs to do the export. This configuration file will contain an ADO.NET connection string to the database, and a list of SharePoint and database fields that describes the map between the two. This configuration file is specified in an XML format.
<ConnectionString>Provider=sqloledb;Data Source=svdemo12;Initial Catalog=sharevis_reports;Integrated Security=SSPI;</ConnectionString>
<FieldMap SharePointFieldName="MyTest" DatabaseFieldName="MyT2"/>
<FieldMap SharePointFieldName="DocumentStatus" DatabaseFieldName="DS"/>
<FieldMap SharePointFieldName="Division" DatabaseFieldName="Division"/>
This configuration file's connection string only describes the database server (svdemo12) and the database (sharevis_reports) into which to place the data. It is up to you to ensure that you have the privileges to access the database using the connection string provided. Connection strings are documented in numerous places at Microsoft's Web site and at other sites on the Internet.
The second part of the configuration describes how the SharePoint fields map to database fields in your database tables. In the above example, values from the SharePoint field MyTest would be placed into the database field named MyT2, etc. In the case of missing fields in either the SharePoint lists or the database table, that field will be skipped during synchronization. You must also ensure that the data types in SharePoint and in your database are consistent.