Handlers enable business rules/logic to be applied to the flow and based on those rules the transaction flow can take different paths or actions that can be triggered in the flows to ultimately conclude with the ‘Response’ to the Initiating System.
Handlers can be added to any Inbound API Request or Response or any downstream system Response.
- A Handler on an Inbound API Request could for example trigger the routing of the request to another Inbound API on the same GLU.Engine. See here for more: Redirect to other transactions
- A Handler on an Inbound API Response could for example trigger the flow to be re-routed or it could trigger a param matching a certain value or values to trigger it to be over-written etc.
- NOTE: Up to 100 values can be used. Using more than this may require a higher Thread Stack Size – this can be added in Build Manager JVM Arguments: -Xss3m
- A Handler on the Response to an outbound Connector call is the most widely used mechanism for orchestrating your flows. See here for more: Orchestration Response Handlers
Handlers enable business rules/logic to be applied to the flow and based on those rules the transaction flow can take different paths to ultimately conclude with the ‘Response’ to the Initiating System. A Request Handler can allow multiple transactions or actions to be accessed from one API request. Request Handlers can be configured based on Request Parameter Content or for Request Conditions:
