Support Regex or Advanced Output Condition Functions to Overcome 256-Character Limitation

Currently, the Output Condition field in Stream supports functions such as contains() and works as expected. However, the field is limited to 256 characters, restricting the number of conditions that can be configured. We request support for regex-based matching or alternative advanced functions that allow multiple conditions to be combined efficiently within the existing character limit.

The Output Condition field is currently used to determine processing outcomes based on values contained in XML_RESPONSE_MESSAGE. For example:

contains(${this.XML_RESPONSE_MESSAGE}, '>Success<')

or contains(${this.XML_RESPONSE_MESSAGE}, '>Problem<')

or contains(${this.XML_RESPONSE_MESSAGE}, '>Failed<')

While this approach works correctly, the 256-character limitation prevents users from adding additional valid response conditions when business requirements expand.

As integrations evolve, organizations often need to recognize a larger set of response messages as successful, warning, or error conditions. The current limitation forces users to either reduce the number of conditions or implement workarounds outside the platform.

Requested Enhancement:

• Support regular expression (Regex) functions in the Output Condition field.
• Alternatively, provide functions such as matches(), in(), contains(), or similar methods that allow multiple values to be evaluated within a single expression.
• Consider increasing the maximum character limit for the Output Condition field.

Business Benefits:

• Simplifies condition management and maintenance.
• Reduces the need for external workarounds.
• Improves scalability of integrations with varying response messages.
• Enhances user flexibility while maintaining readability and performance.

Example Desired Capability:

'.*(Success|Problem|Failed|Delivery has Error|Additional Statuses).*')