Hi!
I am working on a SIM interface project for the Micros 3700. I'm using the MI (menu item) event to read each menu item that is added to an order, and outputting XML to a display.
My problem:
1. I get menu item details for each button or macro press.
2. I get menu item details for condiments (a SLU group) if a NON-default condiment is added ("ADD Rainbow Sprinkles")
3. I get menu item details for condiments if a DEFAULT condiment is removed ("NO Choco Sprinkles")
(Default condiments are displayed as "stay-down" buttons in the SLU group)
4. If I add a non-default condiment, and then ("oops, no, I don't want peanuts, I want almonds...") I remove the non-default condiment, I do NOT get an MI event.
5. Similarly, if I remove a default condiment, and then re-add it ("Wait, no--I DO want rainbow sprinkles"), I do NOT get an MI event.
6. In either case 4, or case 5, my XML output (and the display) continues to include condiments that the user doesn't expect to be there.
7. If I add any other item (including another non-default condiment) I get a subsequent MI event--and the details for that event are correct (the added-then-removed condiment is gone).
Is this an issue with the Micros POS system configuration? (That is, I can set a value with the POS Configurator to cause the remove/re-add default item problem to go away?)
Failing that, is there another event I can listen to that lets me identify that the condiment list has changed?
Thanks!
John M.
I am working on a SIM interface project for the Micros 3700. I'm using the MI (menu item) event to read each menu item that is added to an order, and outputting XML to a display.
My problem:
1. I get menu item details for each button or macro press.
2. I get menu item details for condiments (a SLU group) if a NON-default condiment is added ("ADD Rainbow Sprinkles")
3. I get menu item details for condiments if a DEFAULT condiment is removed ("NO Choco Sprinkles")
(Default condiments are displayed as "stay-down" buttons in the SLU group)
4. If I add a non-default condiment, and then ("oops, no, I don't want peanuts, I want almonds...") I remove the non-default condiment, I do NOT get an MI event.
5. Similarly, if I remove a default condiment, and then re-add it ("Wait, no--I DO want rainbow sprinkles"), I do NOT get an MI event.
6. In either case 4, or case 5, my XML output (and the display) continues to include condiments that the user doesn't expect to be there.
7. If I add any other item (including another non-default condiment) I get a subsequent MI event--and the details for that event are correct (the added-then-removed condiment is gone).
Is this an issue with the Micros POS system configuration? (That is, I can set a value with the POS Configurator to cause the remove/re-add default item problem to go away?)
Failing that, is there another event I can listen to that lets me identify that the condiment list has changed?
Thanks!
John M.