Service Orders Flushing Policy
The client adapter framework allows two distinct behaviors for flushing enqueued service orders from the heap which is temporarily allocated to the protocol message to the heap where the flow controller injects service orders into the main Fulfillment Provisioning flow. This behavior is controlled by the provca::OrderQueueFactory::flushPolicy parameter.
As soon as possible
The first possible flush policy is to flush service orders as soon as possible. In this case, service orders are released in the main Fulfillment Provisioning flow as soon as possible either via the pass or fail port of the ClientAdapter instance.
In order to activate this mode, the flushPolicy attribute should be set to FlushAsap.
At commit
The second flush policy is to flush service orders once the execution of the protocol message flow is completed, that is, once the protocol message comes to an EndPoint. If the EndPoint is a pass point, then all the service orders are flushed on the pass port of the ClientAdapter. Otherwise, all the service orders that have been attached to the incoming protocol message are flushed on the cancel port of the ClientAdapter.
In order to select this flush policy, the flushPolicy attribute must be set to FlushAtCommit.