Database Reference
In-Depth Information
As always, initially we assign working variables for each part of the message container
and do validation for the container's consistency. After that, we go through the VETRO
steps.
Technically, it's a sequence of flow stages, and in each step we check for the task step
name, for instance,
filter
:
fn:exists($body/*:CTUMessage/*:ProcessHeader/
*:ExecutionPlan/*:taskList/*:task/*:invoke/*:serviceTask/
*:taskSteps[@flow='request']/*:
filter
)
In each stage (where it's necessary), we can use the
Publish
operation (from
Stage Ac-
tions
) to invoke the Audit Proxy service. It's also done by using
Routing Options
. The
auditing level for every process is maintained by the EP element:
Search WWH ::
Custom Search