Normally, Cúram infrastructure methods are invoked by the application. However, in workflow the call is often made the other way around - i.e. the workflow engine (infrastructure) calls an application method (e.g.g a Work Allocation method). In these cases, it is not possible for an application developer to step from the call to the curam.util.workflow.impl.EnactmentService.startProcess() method into their application (Work Allocation) method. In this case, the developer must set breakpoints within the method they wish to debug and then execute the method that enacts the workflow. The workflow engine will then (asynchronously) invoke the application method, thereby causing the breakpoint to be reached. The debugger will then suspend execution at the specified breakpoint, thereby allowing normal debugging.
Application methods that fall into the above category are: