Adding new transition step to WMS

Here is the implementation code of one of my customizations that adds two new scans.  Different screen, but same idea.  It looks like your CreateStates.ByAppend isn’t returning anything.  It’s just declaring the new state.  See how mine is using .Append to add the new states:

Note:  I’m also have a section that resets one of the fields (the other is purposely not being cleared)
 

[PXOverride]
public virtual ScanMode<INScanCount> DecorateScanMode(
    ScanMode<INScanCount> original,
    Func<ScanMode<INScanCount>, ScanMode<INScanCount>> base_DecorateScanMode)
{
    var mode = base_DecorateScanMode(original);

    if (mode is INScanCount.CountMode iMode)
    {
        iMode.Intercept.CreateStates.ByAppend(basis =>
        {
            return iMode.States
                 .Append(new TagState())
                 .Append(new AreaState());
        });

        iMode.Intercept.ResetMode.ByAppend(basis =>
        {
            Basis.Clear<TagState>();
            //Basis.Clear<AreaState>();
        });

        iMode.Intercept.CreateTransitions.ByReplace(basis =>
        {
            return basis.StateFlow(flow => flow
                .From<INScanCount.CountMode.RefNbrState>()
                .NextTo<AreaState>()
                .NextTo<INScanCount.LocationState>()
                .NextTo<INScanCount.InventoryItemState>()
                .NextTo<INScanCount.LotSerialState>()
                .NextTo<TagState>()
                );
        });
    }

    return mode;
}

Interesting. Looks a lot like what I did. I added the reset part and found a few extra transitions in the decompiled code. I’ll see if that works.

I wish I could just use Intercept.CreateTransitions.ByAppend instead to add the step more safely but I don’t see any documentation on that either.

I noticed you’ve also added :

.NextTo<PickPackShip.PackMode.ConfirmState>()               

.NextTo<CommandOrShipmentOnlyState>()

I think confirm is implicitly called as the last step, so I don’t think you need to have that in there.  Not sure about that last one though.  I would maybe comment those two out too and see what happens.

So I added new transitions I found in the decompiled code along with that reset part and it appears to work now. I’ll need to run more tests though. I was able to make two separate packages with the custom field filled out, confirm each package and confirm shipment.

packMode
// Replaces the previous implementation with a new one.
.Intercept.CreateTransitions.ByReplace(basis =>
{
    // Creates a list of sequential transitions.
    return basis.StateFlow(flow => flow
        .From<PackMode.ShipmentState>()
        .NextTo<PackMode.BoxState>()
        .NextTo<BoxPackageTransferLabel>() //inserted new state for scanning transfer label
        .NextTo<WMSBase.InventoryItemState>()
        .NextTo<WMSBase.LotSerialState>()
        .NextTo<PackMode.ConfirmState>()
        .NextTo<CommandOrShipmentOnlyState>()
        .NextTo<PackMode.BoxConfirming.StartState>()
        .NextTo<PackMode.BoxConfirming.WeightState>()
        .NextTo<PackMode.BoxConfirming.DimensionsState>()
        .NextTo<PackMode.BoxConfirming.CompleteState>()
        );
});

Not sure why you’re decompiling that code.  It’s in the CodeRepository.

\App_Data\CodeRepository\PX.Objects\SO\WMS\Modes\PackMode.cs

 

You’re right, I just used the go to definition in visual studio on PickPackShip to see this same part as well in decompiled code