Styling with Modifier Sequences
Last edited: December 15, 2003 08:14 AM

Beginning with TouchPRO version 5.20 users of TouchPRO have the ability (by using Manager) to add or modify PLU’s in their database, and control the sequencing of Modifier choices and windows that are presented to the order taker. This ability or feature is called a Modifier Sequence, and requires that the stylist of the application prepare a minimal number of chains and windows that will accomplish the task for 95% to 99% of most scenarios (with the biggest exception to this being a pizza menu).
Modifier Groups (ModGrp)

Every PLU in the database is assigned into 1 of 100 Modifier Groups (0-99). Each of these groups like Sales Groups or Departments may be named for convenience and clarity. If a PLU is to appear in a specific Modifier window at anytime during order entry, it should be assigned an appropriate Modifier Group, to group it with similar choices of Modifiers.

In addition to a name, each Modifier Group may be assigned the number of choices that the order taker will be allowed to choose. The possible values for this setting are Many (infinite – until done is pressed) or 1 to 9. If a Modifier Group was set to 3 choices, the order taker would be allowed to touch up to 3 items on the window.
Modifier Sequences

Every PLU in the database may be linked to 1 of 100 Modifier Sequences (0-99). Anytime the PLU is ordered in TouchPRO, this sequence will be initiated.

Each of the Modifier Sequences may be customized by the store operator (in Manager) with a name, and up to 5 Modifier Groups to be presented as choices to the order taker. For example an Entree Modifier Sequence may contain 3 modifier Groups;

    * Meat Temps – to ask how to cook the meat.
    * Potato – to ask Fries, baked potato, etc.
    * Dressing – to ask what kind of dressing to put on the salad.

In TouchPRO, when an entree (or PLU that uses this Modifier Sequence) is ordered, 3 windows will appear in sequence, containing PLU’s that correspond to these groupings.
The Mechanics

Everything explained to this point is what the store operator will see. However, these actions do not take place in an entirely automatic fashion. The following are the styling considerations that the application stylist must consider to make this flexibility available to the user.
Windows

Except for custom situations, only 2 windows need to be created. One window will allow for 1 to 9 choices of an item, and will contain an AutoPLU region. This window should also contain as a title the new variable Mod Group Name. This will display to the user which window is currently being displayed. Name this window “ModAccpt” – to indicate that it is a window that will stay open until touch has been accepted.

Create a second window named “ModWait4” (as in Wait for Move on) for situations where an unlimited number of touches should be allowed. On this window, place the same elements as the “ModAccpt” window, with the addition of a finished button with the “Move ON” instruction in it.
Instruction Chains

When a Modifier sequence is initiated, for each step in the sequence TouchPRO will attempt to run one of two instruction chains. If the step in the sequence calls for Modifier Group #23 – TouchPRO will first attempt to run a chain named “ModGrp23.CHN” – this would be a custom written chain that has special considerations in it, which is beyond the scope of this article. If this chain is not found, TouchPRO will next attempt to run a chain named “ModGrp_X.CHN”. This is the default chain that will catch all generic situations – and will handle the majority of all modifier sequences.

Listed below, is a sample “ModGrp_X.CHN” that should work in most applications. Below that is an explanation of any new variables and instructions that were added for use in this instruction chain.
The Generic ModGRP_X.CHN

IF ModGrpCh=0 ;0 Choices=Wait 4 move on style
Window = MODWAIT4 
Sequence: Populate ;Fill up autoPLU’s with ModGrp
                 

IF Status>0 ;If PLU’s in this ModGRP?
Wait for ‘Move On’
END IF           
                 

Jump To ‘END’     
END IF           
                 

IF ModGrpCh>0 ;Fixed number of choices
Window = MODACCPT 
Sequence: Populate ;Fill up autoPLU’s with ModGrp
END IF           
                 

IF Status>0 ;If PLU’s in this ModGRP?
REPEAT for ModGrpCh ;Loop for number of choices
Accept Touch     
End REPEAT       
END IF           
                 

‘END’             
Close 1 window   
Sequence: Next ;Perform next ModGRP in sequenc
Variables and Commands

1. ModGrpCh – This is the Mod Group Choices variable. It will contain a value between 0 and 9, indicating the setting (found in Manager) for the current Modifier Group in the sequence. A 0 indicates Many choices – while a 1-9 indicates a finite number of choices. This will therefore determine which window the user is presented with, and the method of moving on.

2. Sequence Populate – This new instruction will populate the AutoPLU region with PLU’s that match the current modifier group in the sequence. It should be performed after opening the window, to insure that when the window is closed – the previous AutoPLU criteria will be restored properly.

3. Status – This variable will contain a 0 after the Sequence Populate, if no PLU’s were found to match the current Modifier group in the sequence. This variable will contain a 1 if valid PLU’s were found. Therefore in this chain, this test is performed so that the user is not presented with an empty window in the event that there are no PLU’s for the modifier Group in question.

4. Sequence Next – This instruction will advance to the next step in the current Modifier Sequence. Which will start the entire process over again. This is how a list of questions may be asked in a specified order.