Filters Connector

Overview

The Equal Filter Component checks whether a given input data exactly matches a specified value. If the condition is met, the message is passed through the equals port; otherwise, it is routed to notEquals.

Usage

This component is used to validate if a text, number, or date is equal to a predefined value, making it useful for strict conditional processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData) and a comparison value (value).

2. Checks for Exact Equality:

   • Performs a strict equality check (sourceData == value).

3. Routes the Message:

   • If sourceData equals value, the message is passed to the equals port.

   • If not, it is passed to the notEquals port.

Output Data Schema

Notes

• Strict Comparison: Ensures exact matches by evaluating equality.

• Supports Various Data Types: Works with text, numbers, and dates.

• Ideal for Conditional Filtering: Useful in workflows requiring strict comparison logic.

This component is essential for workflows that need to validate whether an input is exactly equal to a predefined value before further processing.

Overview

The Contains Filter Component checks whether a given input data contains a specified value. If the condition is met, the message is passed through; otherwise, it is filtered out.

Usage

This component is used to validate if a text, number, or date exists within another dataset, making it useful for conditional processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData) and a search term (value).

2. Checks for Containment:

   • Converts both sourceData and value to lowercase for case-insensitive comparison.

   • Checks if sourceData contains value.

3. Routes the Message:

   • If the value is found, the message is passed to the contains port.

   • If not, it is passed to the notContains port.

Output Data Schema

Notes

• Case-Insensitive Matching: Ensures flexible filtering by ignoring letter case.

• Supports Various Data Types: Works with text, numbers, and dates.

• Ideal for Conditional Filtering: Useful in workflows requiring selective message passing based on content.

This component is essential for workflows that need to validate whether an input contains specific information before further processing.

Overview

The Greater Than Filter Component checks whether a given input data is greater than a specified value. If the condition is met, the message is passed through the greater port; otherwise, it is routed to notGreater.

Usage

This component is used to validate if a text, number, or date is greater than a predefined value, making it useful for conditional processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData) and a comparison value (greaterThan).

2. Checks for Greater Condition:

   • If both values are numbers, compares them numerically.

   • If both values are dates, checks if sourceData is after greaterThan.

   • If exclusive is set to true, strict greater-than comparison is applied.

3. Routes the Message:

   • If sourceData is greater than greaterThan, the message is passed to the greater port.

   • Otherwise, it is passed to the notGreater port.

Output Data Schema

Notes

• Supports Numeric & Date Comparisons: Compares numbers and dates effectively.

• Configurable Strict Comparison: The exclusive property determines whether equality should be considered.

• Ideal for Conditional Filtering: Useful in workflows requiring data validation based on numeric or date values.

This component is essential for workflows that need to filter or route messages based on whether a value exceeds a predefined threshold.

Overview

The Not Equal Filter Component checks whether a given input data is not equal to a specified value. If the condition is met, the message is passed through the notEquals port; otherwise, it is routed to equals.

Usage

This component is used to validate if a text, number, or date is different from a predefined value, making it useful for conditional processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData) and a comparison value (value).

2. Checks for Non-Equality:

   • Performs a comparison (sourceData != value).

3. Routes the Message:

   • If sourceData is not equal to value, the message is passed to the notEquals port.

   • If sourceData is equal to value, it is passed to the equals port.

Output Data Schema

Notes

• Strict Comparison: Ensures only different values pass through.

• Supports Various Data Types: Works with text, numbers, and dates.

• Ideal for Conditional Filtering: Useful in workflows requiring validation that two values are not the same.

This component is essential for workflows that need to filter or route messages based on whether a value differs from a predefined value.

Overview

The Modulo Filter Component checks whether the remainder of a division operation between two numbers is zero. If the remainder is zero, the message is passed through the modulo port.

Usage

This component is used to validate if a number is evenly divisible by another number, making it useful for workflows requiring modular arithmetic checks.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts sourceData (dividend) and value (divisor).

2. Performs Modulo Operation:

   • Computes sourceData % value to find the remainder.

3. Routes the Message:

   • Outputs the remainder to the modulo port.

Output Data Schema

Notes

• Works with Numeric Inputs: Only accepts numbers as input values.

• Used for Modular Checks: Determines whether a number is evenly divisible by another.

• Ideal for Conditional Filtering: Useful in workflows requiring periodic checks (e.g., every Nth event).

This component is essential for workflows that need to determine divisibility or process data based on modular arithmetic conditions.

Overview

The Is Not Empty Filter Component checks whether a given input field contains data. If the field is not empty, the message is passed through the notEmpty port; otherwise, it is routed to empty.

Usage

This component is used to validate whether a text, number, or boolean value is present before proceeding with further processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData) from the input.

2. Checks for Non-Empty Condition:

   • If sourceData is a number or boolean, it is considered not empty.

   • If sourceData is an empty string, array, object, or null, it is considered empty.

3. Routes the Message:

   • If sourceData contains data, the message is sent to the notEmpty port.

   • Otherwise, it is sent to the empty port.

Output Data Schema

Notes

• Supports Various Data Types: Works with text, numbers, booleans, arrays, and objects.

• Automatically Handles Numbers & Booleans: These values are never considered empty.

• Ideal for Conditional Filtering: Useful in workflows that need to check for data presence before proceeding.

This component is essential for workflows that require validation of data presence before further processing.

Overview

The Identity Filter Component allows messages to pass through unchanged. It acts as a transparent relay, forwarding incoming data to the output without modification.

Usage

This component is used in workflows where an incoming message needs to be relayed without transformation, ensuring seamless message propagation.

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts any incoming message at the in port.

2. Forwards Data Unchanged:

   • Passes the received content directly to the out port without any processing or filtering.

3. Maintains Message Integrity:

   • Ensures that message type and encoding remain intact.

Output Data Schema

Notes

• Transparent Message Relay: Forwards messages exactly as received.

• No Filtering or Transformation: Ensures data integrity.

• Ideal for Debugging & Workflow Testing: Helps verify message flow within a pipeline.

This component is essential for workflows where messages need to be relayed unchanged while maintaining their structure and metadata.

Overview

The Range Filter Component checks whether a given input data falls within a specified range. If the condition is met, the message is passed through the inRange port; otherwise, it is routed to notInRange.

Usage

This component is used to validate whether a text, number, or date is within a predefined range, making it useful for conditional processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData), minimum (rangeMin), and maximum (rangeMax) values.

2. Checks for Range Inclusion:

   • If both values are numbers, compares them numerically.

   • If both values are dates, checks if sourceData falls within the given range.

   • If exclusiveMin or exclusiveMax is set to true, strict range checks are applied.

3. Routes the Message:

   • If sourceData falls within the range, it is passed to the inRange port.

   • Otherwise, it is passed to the notInRange port.

Output Data Schema

Notes

• Supports Numeric & Date Comparisons: Compares numbers and dates effectively.

• Configurable Exclusive Boundaries: Allows users to include or exclude boundary values.

• Ideal for Conditional Filtering: Useful in workflows requiring validation of a value within a specific range.

This component is essential for workflows that need to filter or route messages based on whether a value falls within a predefined range.

Overview

The Is Not Empty Filter Component checks whether a given input field contains data. If the field is not empty, the message is passed through the notEmpty port; otherwise, it is routed to empty.

Usage

This component is used to validate whether a text, number, or boolean value is present before proceeding with further processing in workflows.

Properties

Input Ports

Output Ports

Processing Logic

1. Receives Input Data:

   • Accepts a dataset (sourceData) from the input.

2. Checks for Non-Empty Condition:

   • If sourceData is a number or boolean, it is considered not empty.

   • If sourceData is an empty string, array, object, or null, it is considered empty.

3. Routes the Message:

   • If sourceData contains data, the message is sent to the notEmpty port.

   • Otherwise, it is sent to the empty port.

Output Data Schema

Notes

• Supports Various Data Types: Works with text, numbers, booleans, arrays, and objects.

• Automatically Handles Numbers & Booleans: These values are never considered empty.

• Ideal for Conditional Filtering: Useful in workflows that need to check for data presence before proceeding.

This component is essential for workflows that require validation of data presence before further processing.