emite IPaaS allows you to define conditional logic that triggers specific actions if certain criteria are met. By specifying a Source (the data field to check), an Operator (how you compare), a Value (what you compare against), and an Action (what to do if the condition is met), you can dynamically adjust your workflow behaviour - whether that means returning an empty response, aborting the process, or something else.
Rules can be applied when configuring an Action, in the following areas:
Please refer to the following table for a definition of each configuration field, along with some examples:
Configuration Field | Definition | Examples | Additional Guidance |
|---|
Source | The data or field you want to evaluate | "City", "Status", "ResponseCode", customer.address.zip
| Match the source name exactly to how it appears in your data Transform your Source as needed (e.g., to lowercase for case-insensitive checks) Check if you can reference nested objects (e.g., customer.address.city)
|
Operator | A predefined list of comparison or matching operators applied to the Source | Available Operators: EqualTo checks if the Source value is exactly equal to the Value. NotEqualTo checks if the Source value is not equal to the Value. GreaterThan checks if the Source value is greater than the Value (numeric, date, etc.). LessThan checks if the Source value is less than the Value. GreaterThanOrEqualTo checks if the Source value is greater than or equal to the Value. LessThanOrEqualTo checks if the Source value is less than or equal to the Value. Is is often used as a synonym for “EqualTo,” but especially for booleans (“Is true,” “Is false”). IsNot is the inverse of “Is.” Good for negating a boolean or status/flag. EqualToAny checks if the Source value matches any value in a list. Example: Department = "Sales", Operator = EqualToAny, Value = "Sales, Marketing, Support". Rule passes if Department is "Sales", "Marketing", or "Support".
| Choose the operator that best fits the type of comparison you need (e.g., numeric, text, boolean) Consider how to handle null/empty fields. Some operators may fail or skip if the Source is null unless you explicitly define how to handle it.
|
Value | The comparison value (or list of values for EqualToAny) used with the Operator | Premium (string), 404 (numeric), "true" (boolean), etc.
| Ensure proper formatting. Numeric comparisons require numeric Values; date/time comparisons require date/time strings, etc. Check case sensitivity if comparing strings.
|
Actions | A predefined list of actions the system takes if the condition is met | Available Actions: NullResponse: Returns or sets the response to null.
EmptyResponse: Returns or sets the response to "" (empty string).
Abort: Stops the entire process or workflow immediately.
| Use Abort for critical failures (e.g., invalid data). Abort will prevent all subsequent processing. Only use it where stopping the workflow is indeed necessary.
NullResponse and EmptyResponse alter what gets returned, which can affect downstream systems expecting different data.
NullResponse or EmptyResponse can also mask or remove sensitive/unwanted data.
|
Keep an eye on how many rules you create. Combining them or structuring logic carefully can help avoid performance bottlenecks.
