[BigB]

HI all !

-5.5 CU02
-Issue is propagating Release date changes to shipments in non-linear graph.

Date changes will arrive for Releases already planned to shipment(s) but not shipped.
The goal is to propagate the date changes to the related shipment(s) and re-drive the stops.

Order Release agent:
IF ON EDITABLE SHIPMENT plus ORDER RELEASE MOD EDIT SHIPMENT works great.
The shipment is updated and the stops re-driven.
If the new dates make the shipment infeasible, the event is raised and we have an agent to catch it and notify.
-ALL ok here

Problem:
IF ON EDITABLE SHIPMENT only works when all the shipments for the Release are in a linear graph.

The client splits Releases if they are over the TL weight max.
This creates multiple shipments with the 'same' source and dest.
This is not a linear graph and thus the IF ON EDITABLE SHIPMENT and the OR MOD action cannot be used.

Thus, we are using ORDER RELEASE MOD PROPAGATE CHANGES, since this does not require all related shipment to be in a linear graph.

However, this agent action will not update the dates on the related shipments or re-drive the stops. It only updates the dates on the Order Release.

We cannot find a working agent action to do this.
Even if we raise a custom shipment event for each related shipment, there isn't a Shipment agent action to say.. Re-drive the stops based on the Order Release dates.

The client does not want to re-plan the shipments.

Does anyone have a solution to force a re-drive in this example or any suggestions ?

Thanks a lot !

-Brian