The DcsProxy Activity
The DcsProxy activity lets you invoke a DCS operation from within a workflow, either in another DCS service or any WF implementation. After you build and deploy your service, you can implement a workflow to invoke a service operation. For more information, see Invoking a Service from a DCS Workflow.
The following table describes the properties exposed by this activity.
Property Name |
Description |
|---|---|
Context |
The context that the workflow should use to invoke the DCS operation. For more information, see DCS Context. |
Instance |
The DCS proxy object to use if one already exists. This lets you re-use an existing proxy object rather than creating a new one for this service invocation. |
Interface Type |
The interface type of the service to invoke. Services that implement the IBLService interface or derive from the DCSProxyBase object are compatible with the DcsProxy activity. Proxies generated by the Deploy Assembly recipe or from the ProxyBuilder tool are suitable. For more information, see Deploying DCS Services. |
MethodInvoked |
Optional. A method handler to invoke after the DCS service call. |
MethodInvoking |
Optional. A method handler to invoke before the DCS service call. |
MethodName |
The name of the service operation that the activity should invoke. |
OperationId |
The unique identifier of the process that the workflow should invoke. If this is unspecified, DCS generates an automatic identifier that you can read for later use. |
Request |
The request object to send when invoking the operation. The type must match that specified by the service interface. If the service does not require a request object, this property does not appear. |
Returns |
The response object returned by the operation. The type must match that specified by the service interface. If the service does not return an object, this property does not appear. |