| Description |
1) Change scale to not set the next ticket number on new tickets until save is hit.
Disable entry of the ticket number unless scale station setting allow manual ticket number
!pastedImage_d38043_0.png! This will eliminate confusion on selection of the ticket type and direction plus truck flow.
NOTE: require the ticket type and direction to be set when adding a ticket.
2) if ticket direction is changed or ticket type after saved, we would have to void the current and create the next ticket number of the other type. So if they change that and hit save, we must pop up a confirmation message. "Saving this ticket will void %ticket% %type% %in/out% and create a new ticket for %newtype% %new in/out%, would you like to continue? yes/no.
Part 1 will make it so less occurrences of 2 will happen since they can change the selection before save.
NOTE: part 2 is ONLY NEEDED when the two types of tickets use different ticket series of numbers. If both types (from and to) use single ticket pool seires, then the number will not need to change so you do not have to do teh void and messages...
!pastedImage_d38043_1.png! however, part 2 must be done if the ticket types use unique numbers since we will have to close out (void) the original types number and then select the next number int he new ticket type number.
Temp number will be in starting numbers
!pastedImage_d38043_2.png! as new entry TempScaleTicket SCT- 1 making preview SCT-1
Use this number, increment it at each new. Scale ticket loads this number for all types. We get final ticket from pool on save, change of tickets (selection list), change of stations, "close of window" any way it can be closed, VOID or Distribute if we still have a TEMP ticket number.
This process is only used when not allowing MANUAL ticket numbers.
|