Tips for Running Rules
Rules need to be called by an application or a workflow in order to run. Applications generally use the rule result to perform additional functionality—there are a number of ways application functionality can access rules.
- Run rules on a schedule, looking up the data in a database, FTP server, email inbox, or another mechanism
On Batches of Data
- Feed large batches of data into the rule engine using flows. Decisions can manage flat files (e.g., csv, excel), structured files (e.g., json/XML), as well as stored prebuilt data
Via Service Interface
- Any rule can be called using a SOAP or REST (XML or JSON) service interface
- Each rule has an integration page that shows all of the different service interface options and provides sample data structures and/or code for the integration
Via Message Bus
- Rules can be triggered to run as a result of a message across an infrastructure, such as RabbitMQ, MSMQ or IBM MQ Series, which are suitable for high performance or high throughput environments
Example – If a Rule delivers a TRUE, you could automatically send an email, write a value to a database, prompt a user, or automatically kick off other processes and actions.