Features

    Dispatching

    One of the coolest features Delivery Manager brings to the table is a FIFO (first in, first out) driver list that’s used on the dispatch screen. Here’s a picture of the dispatch screen so you can get a better idea of what the list looks like.

[img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvryMgrdispatch.gif[/img:bqfjr099]

    It’s simple to dispatch a check, just follow these three steps:

      1. Select a check by touching it (highlighting it), then touch the TAG button. This puts a check mark next to the check, indicating that it will be dispatched when you touch the DONE button. If you make a mistake and tag the wrong check, simply highlight the check again and touch the TAG button to turn the check mark off.
      2. Select a driver.
      3. Touch the DONE button. Now the tagged check(s) are dispatched and ownership is magically transformed over to the selected driver.

    As you can see the screen is divided into two lists: a Checks List and an Available Driver List. Let’s talk a bit about these lists.

        The Checks List

        The Checks List is a list of all the checks marked “to be delivered”. The list has a series of columns and you can sort the list by any of the columns by touching the column header. For instance if you wanted to see the Checks List sorted by time elapsed since order, you’d touch the Time column header.

        The Available Driver List

        The Available Driver List is the FIFO list. It is sorted by availability, meaning the least available drivers are on the bottom of the list and the most available on top. Once you’ve dispatched to a driver, their name goes to the bottom of the list and you’ll see the time elapsed since they were last dispatched to. That way you don’t dispatch checks to a driver who is considered “out of the store”. When the driver returns to the store, they will be placed on the top of the list again.

    That’s wraps up the discussion on Dispatching checks, now let’s move on to Undispatching.

    Undispatching

    Undispatching takes the check away from the driver it was assigned to and gives it back to the original employee who placed the order. You might need to do that if you dispatched the wrong check, or maybe the customer called back and canceled the order. The Undispatcher looks like this:

[img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrundispatch.gif[/img:bqfjr099]

    Like it’s brother, the Dispatch Screen, it’s simple to undispatch a check, just:

      1. Select a check by touching it (highlighting it), then touch the TAG button. This puts a check mark next to the check, indicating that it will be dispatched when you touch the DONE button. If you make a mistake and tag the wrong check, simply highlight the check again and touch the TAG button to turn the check mark off.
      2. Select as many checks as you want and when you’re finished, touch the DONE button.  The check will be re-assigned back to the original employee who took the order and it will appear ready to re-dispatch on the dispatch screen.

    See?  Simple, huh? Next up: Returning from a delivery

    Returning checks

    When a driver returns from his delivery he needs to “return” his checks. This action stores the time he got back to the store and enables you to evaluate delivery times.  There’s two ways to store this information, you can return just one check or all checks for a specified employee.

    Functions

    The manager can add employees to the FIFO driver list who are not clocked into the proper job code and can also inactivate a particular driver.  Here’s what the Functions screen looks like:

[img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrfunctions.gif[/img:bqfjr099]

    Here you see a list of clocked in employees on the left and the current FIFO driver list on the right. You can select any employee from the list on the left and add them to the driver list. Simply:

      1. Highlight the desired employee.
      2. Touch the ADD EMPLOYEE button.

    You can also control a driver’s active status by selecting a driver and touching the TOGGLE STATUS button. When a driver is INACTIVE they do not appear on the list of available drivers on the dispatch checks screen.

    That’s it in a nutshell, you should understand the functionality Delivery Manager can provide now.  Want to know more?  Then read on, we’re going to install it and discuss the technical details.

Installation

    Installation consists of two parts. Installing the executable and styling.

    Installing the executable

    Copy the two binary files into your Touchnet folder. The files are: DlvryMgr.EXE and DlvryMgr.RES.

    Styling

    This is where you’ll have to work a bit.  I’ll go over each command line option in detail and leave it to you to implement it as you see fit.  To utilize the basic functionality of Delivery Manager is really quite easy, and I’ll tell you how.  But don’t forget you can expand on the basic functionality through styling to incorporate just about anything your heart desires.

    Let’s start with the command line options and then we’ll bring them all together in a basic way you can implement in your application.

    What are the command line options? They a method of telling Delivery Manager what to do. Here’s a complete list:

    {/dispatch} {/undispatch} {/return} {/returnall} {/closechk} {/closeall} {/inactive} {/listreturned} {/listnonreturned} {/recall} {/functions} {/options} {/init} {/?}

    To utilize one you type the executable name followed by a command line option.  Don’t mix and match them, you can only use one at a time with the exception of the {/init} option.

    For example, to launch the dispatcher portion of Delivery Manager, you’d type “DlvryMgr /dispatch”. Make sense?  Great, now the detailed explanation of each.

        /DISPATCH

        Use to launch the UI to dispatch checks to available drivers. The UI has the following components:

          1. A Checks List
          2. An Active Driver List
          3. A TAG Button
          4. Up to 5 User Definable Buttons
          5. A Done Button

            The Checks List

            The checks list is hardcoded to populate with checks that have Word1 = “IN”. The list is segmented in columns, touch the header of any column to sort the list by that header.

            [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrchkslst.jpg[/img:bqfjr099]

            Active Driver List

            The active driver list is FIFO and is populated by matching clocked in employees to the Delivery Job Code as defined using the {/options} command line.  Its called “Active” because it is possible for an employee, who automatically qualifies for the list by being clocked into the proper job code, to be set to INACTIVE and thereby not included on the list for dispatching to. This can be useful for employees on break. If a driver is OUT, you will see the amount of time elapsed since he/she was dispatched to.

            (You can also add to this list using the {/function} command line, where a user can manually bypass the job code rule to add an employee to the list.  More on that later.)

            [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrdriverlst.jpg[/img:bqfjr099]

            TAG Button

            Use the TAG button to TAG/UNTAG checks.  If a check is TAGGED when the  DONE button is selected, it will be dispatched.

            Dispatched means:

              1. The check’s Server Id will be changed to selected employee ID.
              2. The check’s Word1 will be changed to “OUT”.
              3. The selected Employee will be marked as “OUT” on FIFO list.

            DONE Button

            If any checks are tagged, touching the DONE button will dispatch the tagged checks. (see above definition of “dispatch”)  In addition, certain values will be stored for you to retrieve back in TouchPro so that you will know what happened.  You might want to do additional things besides, just dispatch the check. For instance, you may want a receipt to print for each check.

            The information available to you is stored on the “Z” drive in two files:

              1. Variable.TXT
                  Variable Name Variable # Description

                  Quantity      {1}        the quantity of checks dispatched

                  Number 3      {40}      the selected Employee ID

                  Status        {86}      indicates which button was touched
                                          DONE button = 9
                            User button1 = 1
                              User button2 = 2
                            User button3 = 3
                            User button4 = 4
                            User button5 = 5
              2. !Tag.BUK

                  The check numbers of each dispatched check will be stored in columns 1 – 4. (Remember, you’ll know how many checks are in the bucket from the Quantity variable)

                  NOTE: When dispatching or undispatching the bucket will ONLY contain the check numbers of successfully dispatched/undispatched checks, not ALL tagged checks.  When a User defined button is pressed, it will contain ALL tagged checks instead.

            For example:

            Let’s say you dispatched checks #7789,#7788 and #7790 to employee #123. Here’s what the two files would contain when the Delivery Manager was finished:

            Variable.TXT:

            Variable Name  Variable #  Description

            Quantity      {1}          3

            Number 3      {40}        123

            Status        {86}        9

            !Tag.BUK:
            Column
            Row
            1 2 3 4
            1 7      7      8      9
            2 7 7 8 8
            3 7 7 9 0

            NOTE: these are NOT the actual file formats.

            Both of these files are updated after every transaction Delivery Manager handles. (i.e. Dispatching, Undispatching, etc.) For a complete table of the possible values stored in these files after each transaction refer to the Response Table later in this article.

            USER Definable Buttons

            You may add up to 5 of your own buttons that will appear across the bottom of the dispatch screen.  To add buttons here, you need to launch Delivery Manager with the {/options} command line switch which we’ll talk about in detail in {/options} command line section.

            When one of the User definable buttons is touched, Delivery Manager acts very similar to when the DONE button is touched.  The differences are:

              1. The tagged checks will NOT be dispatched.
              2. The Status variable in Z:Variable.TXT will be set to the number of the button touched.  (i.e. (1 – 5) instead of 9)
              3. The !Tag.BUK file will contain a list of all the TAGGED checks (rather than the successfully dispatched ones)

        /UNDISPATCH

        Use to launch UI to undispatch checks. The UI consists of the following components:

          1. A Checks List
          2. A TAG button
          3. A Done Button
          4. Up to 5 User Definable buttons

            Checks List

            The checks list shows all the checks considered to be “OUT” or “DISPATCHED”.  It is populated by loading a list of previously dispatched checks and verifying that they are still open. The checks list is segmented in columns and you can touch the header of any column to sort the list by that header.

            [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrchkslst2.jpg[/img:bqfjr099]

            TAG Button

            Use the TAG button to TAG/UNTAG checks.  If a check is TAGGED when the  DONE button is selected, it will be undispatched.

            Undispatched-Dispatched means:

              1. Revert Server ID back to original ID if original employee is clocked in.
              2. Revert value of Word1 back to “IN”.
              3. Update FIFO list. If all of an employee’s checks are undispatched,      then the employee will be marked as “IN” on the FIFO list.

            DONE Button

            If any checks are tagged, touching the DONE button will undispatch the tagged checks. (see above definition of “undispatch”)  In addition, certain values will be stored for you to retrieve back in TouchPro so that you will know what happened.  You might want to do additional things besides, just undispatch the check. For instance, you may want a receipt to print for each check.

            After touching the DONE button Delivery Manager will store the relevant information in the two communication files for you to access via TouchPro.  The information follows the same format as the Dispatch response, except for the “Selected Employee” field in Variable.TXT.  This field is not necessary and will always be 0.

        /RETURN

        Use to stamp a return time on a dispatched check. This command line has no UI, it would be included in some kind of Return chain and would be invisible to the user.  To use, you need to pass the check number you wish to stamp the return time for. So your shell will look like this:

        [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrreturnshell.jpg[/img:bqfjr099]
       
        Note the variable options.  You’ll need to have both Store and Get variables options on.  The only variable you’ll need to pass is variable #28, (check number).  This tells Delivery Manager which check to stamp the return time on.

        Upon completion, Delivery Manager will let you know what happened through the two communication files, Variable.TXT and !Tag.BUK. 

        Variable.TXT will have this information:

        Variable Name
        Variable # Description
        Quantity {1} quantity of checks returned
        Number 3 {40} null value
        Status {86} indicates success or failure
        Success = 1
        Failure = 2

        And !Tag.BUK will have the usual list of the check numbers returned in columns 1 – 4.

        /RETURNALL

        Use to stamp a return time on ALL dispatched checks for a specified employee.  Like the Return option, this command line also has no UI.  To use, you’ll pass the employee id for whom you wish to stamp ALL dispatched checks as Returned in Number 1. So your shell will look like this:

        [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrreturnallshell.jpg[/img:bqfjr099]

        Note the variable options.  You’ll need to have both Store and Get variables options on.  The only variable you’ll need to pass is variable #38, (Number 1, the employee id).  This tells Delivery Manager which employee to stamp return time on all their checks.

        Upon completion, Delivery Manager will let you know what happened through the two communication files, Variable.TXT and !Tag.BUK.  This command line switch is different in that it adds another possible situation to the mix.  It is possible to request Delivery Manager to return all checks for an employee, and for Delivery Manager to be unsuccessful because one or more of the specified employee’s checks are in use at another node.  For that reason, Delivery Manager will return the quantity of unsuccessful checks and a list.  The quantity will be returned in Variable Number 2 and the list will be in !Tag.BUK in columns 11 – 13.

        Variable.TXT will have this information:

        Variable Name
        Variable # Description
        Quantity {1} quantity of checks returned
        Number 2 {39} quantity of checks not returned because they were open on another node
        Number 3 {40} null value
        Status {86} indicates success or failure
        Success = 1
        Failure = 2
        Some but not all = 99

        !Tag.BUK will have the usual list of the check numbers returned in columns 1 – 4 as well as a list of not returned checks in columns 11 – 13.

        /CLOSECHK

        Use to remove a check from the dispatched check list and post relevant information into a historical delivery journal.  These journal files given a .DLV extension and will be stored in the Reports directory and  named similar to TouchPro’s other journals, following the YYMMDD format. To use, you’ll pass Delivery Manager the check number you wish to close out. Your shell will look like this:

        [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrclosechk.jpg[/img:bqfjr099]
         
        NOTE: ALWAYS USE PRIOR TO “CLOSE CURRENT CHECK” INSTRUCTION AND IN CONJUNCTION WITH.

        Note the variable options.  You’ll need to have both Store and Get variables options on.  The only variable you’ll need to pass is variable #28, (Check#).  This tells Delivery Manager which check you wish to close out.

        Upon completion, Delivery Manager will let you know what happened through the two communication files, Variable.TXT and !Tag.BUK.

        Variable.TXT will have this information:

        Variable Name
        Variable # Description
        Quantity {1} quantity of checks returned
        Number 3 {40} null value
        Status {86} indicates success or failure
        Success = 1
        Failure = 2

        And !Tag.BUK will have the usual list of the check numbers closed in columns 1 – 4.

        As I mentioned above, when a check is closed, the delivery information is posted to a delivery journal for historical reporting capability.  The YYMMDD.DLV file format is:

        Field Name Data type

        Check #        INTEGER

        Check Amount    LONG

        Employee ID    INTEGER

        Original ID    INTEGER

        Open Time      INTEGER

        Dispatch Time  INTEGER

        Return Time    INTEGER

        Close Time      INTEGER

        Customer Record LONG

        Memo 1          STRING * 40

        Totals:        62 bytes per record

        /CLOSEALL

        Use to remove all checks from the dispatched check list for a specified employee and into a historical YYMMDD.DLV file. This command line works identically to the {/close} option with the exception that you pass it an employee id rather than a check number.  Pass this information in variable #38, (Number 1, set to the employee id)

        It is possible to request Delivery Manager to close all checks for an employee, and for Delivery Manager to be unsuccessful because one or more of the specified employee’s checks are in use at another node.  For that reason, Delivery Manager will return the quantity of unsuccessful checks and a list.  The quantity will be returned in Variable Number 2 and the list will be in !Tag.BUK in columns 11 – 13.

        Variable.TXT will have this information:

        Variable Name
        Variable # Description
        Quantity {1} quantity of checks returned
        Number 2 {39} quantity of checks not closed because they were open on another node
        Number 3 {40} null value
        Status {86} indicates success or failure
        Success = 1
        Failure = 2
        Some but not all = 99

        !Tag.BUK will have the usual list of the check numbers returned in columns 1 – 4 as well as a list of not returned checks in columns 11 – 13.

        /LISTRETURNED

        Use to generate a list of all checks marked returned for a specified employee. To use, you’ll pass Delivery Manager the employee id you wish to generate a list for. Your shell will look like this:

        [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrlistreturnshell.jpg[/img:bqfjr099]

        Note the variable options.  You’ll need to have both Store and Get variables options on.  The only variable you’ll need to pass is variable #38, (Number 1#).  Load it with the employee id of the employee you wish to generate the list of checks for.

        Upon completion, Delivery Manager will let you know what happened through the two communication files, Variable.TXT and !Tag.BUK.

       
        /LISTNONRETURNED

        Use to generate a list of all checks NOT marked returned for a specified employee. This option is used the same way the {/listreturned} option is, just pass Delivery Manager the employee id in variable Number 1. The standard results are returned in the communication files.

        /FUNCTIONS

        Use to launch the UI to perform various functions.

        [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrfunctions.jpg[/img:bqfjr099]

        The UI has the following components:

          1. Clocked In Employee List
          2. Driver List
          3. Add employee to Driver list button
          4. Toggle Driver active status button
          5. Done button
          6. Clocked In Employee List

              You will see a list of all clocked in employees regardless of Job Code used.

              [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrclockedemplist.jpg[/img:bqfjr099]

              Driver List

              You will see a list of ALL drivers (not just ACTIVE ones), their IN/Out status and their Active status.

              [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgrdriverlist.jpg[/img:bqfjr099]

              Add Employee Button

              Touching this button will add the highlighted employee from the Clocked In  Employee list to the Driver list.  You can use this to override the Job Code requirement the Driver list enforces.  For instance you may want to dispatch to an employee who is clocked in under HOST instead of DRIVER.

              Toggle Status button

              Touching this button will toggle the active status of the highlighted Driver.  Inactive drivers do not appear on the Dispatching UI list of drivers.

              Done button

              Exit Functions screen.

              /OPTIONS

              Use to launch options configuration.  Here you’ll define the job code used for the FIFO list, and the text for any User Defined buttons.

              [img:bqfjr099]http://www.possupport.net/dealer/kbase/images/dlvrymgroptions.jpg[/img:bqfjr099]

              To use the User Definable buttons in the Dispatching/UnDispatching screens, simply type some text in the button text field.  The button will now be drawn on those screens.

              The Driver Job Code determines which employees are automatically added to the Driver List upon clock in.

Technical

Check listings are generated by examining the Word1 variable for all stored checks.  Undispatched checks have Word1 = “IN” while dispatched checks have Word1 = “OUT”..

Driver lists are FIFO and are generated by matching the jobcode of clocked in employees to the FIFO Job Code. The FIFO Job Code is maintained in DataRegistry.DAT as option 16.