Customize process logic in Print/Email Orders screen

Hello @charithalakshan49!

Are you adding a new action to the screen? I’m asking because all current actions available on this screen already work in so-called Batch Mode. It means that all selected entities are combined into a list, that will be passed to the action of the processing graph (SOOrderEntry in this case) via the PXAdapter parameter.

Here is the configuration of the SOOrderEntry.printQuote action for example (see the PX.Objects.SO.Workflow.SalesOrder.ScreenConfiguration file):

All actions of this mass process screen are added via Workflow engine. So if you want to add a new action that would work in batch mode (i.e., consumes a whole list of orders at once, not one-by-one separately), you have to register that action in the similar way the SOOrderEntry.printQuote is registered.

So the right form for such a change is the following:

public class SOOrderMassProcessNewActions : PXGraphExtension<SOOrderEntry>
{
    [PXButton, PXUIField(DisplayName = "Do Something Important")]
    protected virtual IEnumerable myNewBatchAction(PXAdapter a)
    {
        // this form makes an action to work in both batch and non-batch mode,
        // so always try to write actions in this way,
        // i.e., avoid Current-based processing, instead gather records from adapter
        var ordersToProcess = a.Get<SOOrder>().ToArray();
        foreach (var order is orders)
        {
           // do something here for each order
        }
    }
    public PXAction<SOOrder> MyNewBatchAction;

    // always try to separate functional changes from WF changes,
    // because those two types of changes have different dependencies
    public class WorkflowChanges : PXGraphExtension<
        PX.Objects.SO.Workflow.SalesOrder.ScreenConfiguration,
        SOOrderEntry>
    {
        // this method is a special entry-point and should always be sealed,
        // because it cannot be overridden further in any reasonable way
        public sealed override void Configure(PXScreenConfiguration config) =>
            Configure(config.GetScreenConfigurationContext<SOOrderEntry, SOOrder>());

        // prefer to store WF configuration in a static scope,
        // in order to avoid accidental access to instance members of graph/extension,
        // they are not initialized yet, so it is not safe to access them.
        protected static void Configure(WorkflowContext<SOOrderEntry, SOOrder> context)
        {
            context.UpdateScreenConfigurationFor(screen => screen
                .WithActions(actions =>
                {
                    // this registers the action in WF engine,
                    // and configures it to be visible on processing screen
                    // and work in batch mode.
                    // You may need to make additional configuration for the action
					actions.Add<SOOrderMassProcessNewActions>(g => g.MyNewBatchAction, c => c
						.MassProcessingScreen<SOOrderProcess>()
						.InBatchMode());
                }));
        }
    }
}

Hope that was helpful.