Pre Qualification Failed Handler
Like the PIF handler, there is no default implementation of the PQF handler provided with the product.
Be aware that the Pre-qualification failed handler deals with errors raised not only in Feasibility, but also, AOPD. Even if in your architecture you don’t have a Feasibility step, you will always have AOPD, and if AOPD raises exceptions, Orchestrator will publish an event to the PQF handler and wait for a response. If there is no PQF handler implemented, nothing further will happen for that order and it will be “stuck”.
Even if AOPD exceptions are expected to be rare for your application (i.e. you validate the order thoroughly prior to AOPD), consider at the very least, implementing monitoring on the PQF request queue, so that operations will be aware that AOPD has failed for an order, and some action needs to be taken to move the order on.
You may want to consider making the PQF handler “just another” source of Technical Exceptions. In this way, a framework for dealing with automating Technical Exception handling, could be used to also deal with PQF requests. This is the approach that is described in the next section.