shogun32
Well-Known Member
- Joined
- Feb 8, 2019
- Threads
- 89
- Messages
- 14,766
- Reaction score
- 12,312
- Location
- Northern VA
- First Name
- Matt
- Vehicle(s)
- '19 GT/PP, '23 GB Mach1, '12 Audi S5 (v8+6mt)
- Vehicle Showcase
- 2
may well be so. But all this (gratuitous) contorted logic is supposed to be embedded into the ordering system database. ie. on INSERT into ORDERS should trigger a stored procedure that does all the silly allocation check nonsense and throw an exception and rollback the transaction and scream at the guy at the other end of the frontend.Like I said, training at Ford for specialty programs like this one is SERIOUSLY poor!
What we have here is Corp IT not doing their damn job, or not being told of the kafka-esque ordering rube goldberg nonsense. There is zero rational reason to artificially constrain availability of certain options. If the Penske paintshop can only do 200 cars a year, then 'SELECT count(*) from Orders where Painted_stripes=1 > 200', then pop up dialog box, "you'll get your car in 18 months or even later. Do you want to wait or remove the option?" Sales agents are only good for bringing people coffee and snacks. Intelligence properly belongs in the backoffice database.
Sponsored