Please enable JavaScript.
Coggle requires JavaScript to display documents.
Request Generator Tasks, Autopilot # (Workflow (ShipmentPlan
…
-
-
Notes
Param file should be stiched together on demand for downstream reqgen processor. Need a custom processor for this
Only one concurrent run of request processor at a time. It should wait if the processor is already running
-
TMAPI calls need not be crafted from Request generator. There should be a single processor that does TMAPI calls
Listeners are not really required. All information is present in the response xml mostly #
-
-
-
Listener flowfile will not have any payload, only attributes: eg: shipmentId & shipmentLegId #
What will be the xml format of the NEN event raised when Shipment is created. WIll it have both shipment number and shipment leg id?
Initially, the idea was to create listeners on NEN queues to check if the requests were successful