You can create listener transactions to keep track of the changes in a document when it is in another pipeline. For example, if you are creating an order fulfillment pipeline in which the order document is dropped into an outbound shipment pipeline with its own set of statuses for shipment, you can configure a status change listener transaction in the order fulfillment pipeline to keep track of the statuses the order document goes through in the outbound shipment pipeline.
The transaction details screen for a listener allows multiple drop statuses to be added. A validation is performed to prevent the removal of a transaction drop status record if there is a pipeline listener record for that drop status. When setting the statuses listened to in the pipeline, specify which drop status to use for each listened to status. When a child order changes status, the parent order is updated with the specific drop status for the status to which the child order has just changed.
This listener listens to all the same statuses as the previous three listeners combined and drops into whichever drop status that the previous three listeners did.
Listeners that change status on an order raise an event upon status change. Listeners raise the event for each order line that has a status change. The ON_STATUS_CHANGE event is raised for each order line using the Listener transaction.
To configure a status change listener: