Invalid routing rules cause error during custom routing
When a request's transaction status is changed, ILLiad will loop through active routing rules and check for a rule matching the request's TransactionStatus and ProcessType, and then apply the rule when appropriate. However, if that routing rule is invalid because it has null fields (e.g., a null value for TransactionStatus, ProcessType, MatchString, NewTransactionStatus, or NewProcessType), an error will be logged and the routing process will fail.
ILLiad should instead check to ensure the routing rule is valid before applying the rule to the request and, if the rule is invalid, provide detailed information in the ILLiad Client log to state why the rule is invalid and cannot be applied to the request, then move on the try the next rule.
Bug# 25294