If users call the "modify start time" function as bulk operation over single start and cyclic orders then you get a hint that it is not possible.
If users call the "modify start time" function as bulk operation over single start orders then a form is provided to modify the start time.
If users call the "modify start time" function as bulk operation over cyclic orders then a form is provided to modify the period (without a date).
Desired Behavior
The bulk operation to modify daily plan orders allows to add orders for single starts and cylic starts in the same request.
The period of cyclic orders cannot be changed.
The start time can be updated for orders using single starts and for the period begin of cyclic orders.
If the period of the cyclic order extends over two daily plan dates after the shifting, the period is truncated so that only the first day is taken into account.
The start time can be specified
relative to the current point in time ("now"),
relative to the current start time indicated by a number of days ("+/- days")
relative to the current start time indicated by a timespan ("+/-HH:MM:SS")
Past start times can be the result of an operation that modifies the start time. In this situation the following applies:
Orders for Single Start: orders are moved to past start times. As a result the orders will start immediately when submitted to Controller and Agent.
Cyclic Orders:
If the end time of the order's period is in the past, then the cyclic order is dropped. Instead, an order for a single start is created that will be executed immediately when submitted to the Controller and Agent.
If the begin of the order's period is in the past and its end time is in the future, then the cyclic order is created for future cycles only.
If the begin and the end of the order's period are in the future then the order will hold all cycles.
Feature
High
