Barcode Scan States: Confirmation State

The confirmation state is a special scan state that validates and confirms all the data accumulated by input states and completes the barcode processing cycle by applying changes based on this data to a certain document. There are two types of confirmation strategies: explicit and implicit. An explicit confirmation strategy shows the prompt to confirm an action. An implicit confirmation strategy automatically executes the confirmation process.

Required Properties

For a confirmation state, you must implement the Prompt required property. You use the property to specify the prompt that is shown to a user to confirm an action. In the Prompt property, you can use the Basis.Localize() method if you need to insert message parameters. If you do not need to use parameters in the message, you return the message itself. The system localizes it automatically.

Implementation of the Confirmation Process

The PerformConfirmation() method is an entry point for the confirmation process. The FlowStatus object is the result of the PerformConfirmation() method. This object indicates how the system should complete the confirmation. The FlowStatus class has multiple factory methods that facilitate proper object creation. For details about these methods, see ConfirmationState<TScanBasis> Class.

A confirmation process can contain complex logic, which should be split into multiple methods that can be overridden separately. While scan components should not introduce and use virtual methods, this does not mean that all the confirmation logic should be implemented in a single method. To implement this complex logic, you can use the ScanExtension components. The ScanExtension component is a PXGraphExtension that can be created and used in the scope of the barcode scan class and of all types of its components. Any scan component can delegate its responsibility to a particular ScanExtension component. Because the ScanExtension component is a PXGraphExtension, it can be customized as other graph extensions are customized; that is, it can be split into multiple virtual methods that can be overridden.

The component that delegates a part of its logic to a ScanExtension is called a complex component. You can learn how to customize complex scan components in Extension of Scan Components: General Information.

Change of the Confirmation Strategy

public class INScanCount : WMSBase
{
    ...
  
    public
        PXSetupOptional<INScanSetup,
        Where<INScanSetup.branchID.IsEqual<AccessInfo.branchID.FromCurrent>>>
        Setup;
 
    public override bool ExplicitConfirmation => 
        Setup.Current.ExplicitLineConfirmation == true;
  
    ...
}