question

Some improvements to the On Message code to make @Joerg Vogel's model work more as expected.

- Only remove the first entry of the array if the pull was successful.

- Do not create a back order for the pull (or change the code to handle the back order on the pull result if no value was pulled).

- Place the code in a loop, so it pulls as many entries as possible, to pick up any task sequences that might have been skipped when first pushed to the list, but are now of the right type.

- To prevent any error messages when the array runs out, I add an invalid value (-1) to the array once its empty.

int done = 0;
while(!done) {
    int valuebound = current.label1[1];
    string qrystr = "WHERE bound == "+string.fromNum(valuebound);
    TaskSequence pulledTs = List("TSList1").pull(qrystr, 1, 1, current, 0, LIST_DO_NOT_BACK_ORDER);
    if (pulledTs){
        pulledTs.move(current);
        pulledTs.dispatch();
        current.label1.shift();
        if(current.label1.length == 0) {
            current.label1 = [-1];
        }
    }
    else {
        done = 1;
    }
}

Edit:

Also wanted to add that you can get the same functionality without using a list by storing the task sequences in the tree of the ASRS and looping through them until the right type is found.

All this can happen in the "Use Transport" field of the queue and rack, making the message trigger redundant.

asrs-io-jv-fm.fsm