Run AIF processor with Break points

Submitted by Nathan Clouse on 09/07/11.

Last modified: 

02/12/17

Tags: 

Class(es): 

The AIF debugging can be quite aggravating especially since document processing can happen in the background leaving you in the dark. The way to fix this is find the AifInboundProcessingService Class and go into the runAsWrapper method.

Find the following lines:

// BP deviation documented
        runas(axaptaUserId,
                classnum(AifInboundProcessingService),
                staticmethodstr(AifInboundProcessingService, processAsUser),
                messageIdContainer);

Comment them out and add the following line afterward:

AifInboundProcessingService::processAsUser(messageIdContainer);

And there you go. Now you will be able to set break points in AxD classes that will actually work so you can gain some insight into what is happening or what is breaking. The end result of the code will look like this:

new RunAsPermission(axaptaUserId).assert();

        // BP deviation documented
        //runas(axaptaUserId,
        //        classnum(AifInboundProcessingService),
        //        staticmethodstr(AifInboundProcessingService, processAsUser),
        //        messageIdContainer);
        AifInboundProcessingService::processAsUser(messageIdContainer);

        CodeAccessPermission::revertAssert();