Using the Content Handler

Skelta Workflow.NET 2004 Help

The Content Handler can be used for interacting with the application data. The actions in the workflow can access and update the application data using the Context object of the Content Handler. More than one Content Handler can be configured for a workflow. Each Content Handler that is so configured is identified by its name.

The Content Handler can be configured in the WorkflowNET.Config.Xml file, in the workflow element, as shown below.

<workflow name="Workflow1">

							 ...

							  <contenthandler name="contenthandler1" 
							class="ApplicationContentHandler1" assembly="C:\Program 
							Files\Skelta\Workflow.NET\Bin\ContentHandler.dll" param="C:\Program 
							Files\Skelta\Workflow.NET \content.xml"/ >

							  <contenthandler name="contenthandler2" 
							class="ApplicationContentHandler2" assembly="C:\Program 
							Files\Skelta\Workflow.NET\Bin\ContentHandler.dll " param="C:\Program 
							Files\Skelta\Workflow.NET \content.xml"/ >

							 ...

							</workflow>

The class attribute refers to the class that implements the Workflow.NET.Interfaces.IContentHandler interface. Any value can be set to the param attribute, for initializing the Content Handler. The value of the param attribute is passed to the Content Handler during initialization.

Once the Content Handler is configured, the content names appear directly in the Resource Filter and the Condition Builder, with the content name prefixed. Content Handlers can be developed specific to the application, by implementing the Workflow.NET.Interfaces.IContentHandler interface. Refer to the API documentation for more details.

Skelta Workflow.NET 2004 provides a default implementation of the Content Handler that reads and updates data in the application database. This Content Handler uses an XML file for configuring the application tables or views from which the data is to be read.

Skelta - A BPM Workflow Software Company