Pandoras Box

[jackkrooss]

This issue covers both editing orders and circumventing lots of issues with the order state. In order to circumvent the strategy is to:

• Eliminate partial reserves
• Eliminate HOLD
• Only permit editing of the order when it is status CSR-RESERVE
• Only permit changing status to OPEN when the status is CSR-RESERVE
• Permit CLOSING the order anytime, but leave no way to reopen

There is still a problem, but it may not impact operations if constrained as above. So here is the problem. Below are screen shots from two multi-line orders. I shipped two of the lines in each order, but in 241 it was 2 and 3, and in 240 it was 1 and 3. Order and process status of the entire order is different which is likely simply due to how the order lines were parsed. The problem here is that 1) it is confusing but more important 2) we can not test the status to determine state. Note also we get a hieroglyph in Location in the second one. (AARGH). If we dug in and figured out why these two cases result in different order states we might be able to do something about it, but at least for now, my inclination is to just winnow things down to what works, if that is possible.

So, I have taken out the labels for Order AND Process. Users will just have to look at the order lines they have selected to see the state of different items withing the order.

Also, now we can hopefully add an edit function. What is envisioned is that the new Edit button will first check to make sure that we are in CSR-REVIEW (like the Open button now does) and then jump to the Edit/Create screen and populate it with the order. Note once an order is opened it can no longer be edited.

So, what is done is the rework of the Order Manager screen. What needs to be done is the trigger function for the Edit button and the repopulate.

Also, I took the partial reserve out of the Demand Manager, so we never will get into those wacky states.

[jackkrooss]

I think this is done. Suggest closing issue.