[FEAT] Bookmarks- Custom Payload Comparison

[codsay]

Feature Request

Problem Overview

Currently, payload comparison is rigidly based on exact JSON string matching, limiting flexibility and adaptability.

Proposed Solution

Introduce a customizable payload comparison mechanism. This would allow users to implement their own logic for determining payload matches, providing greater control over workflow triggers.

Use Cases

• Flexible Payload Matching:

  • Support for pattern matching (e.g., regex) to handle variable payload structures.
  • Ability to define expected payload formats or partial matches.
  • Accommodation of optional payload fields without affecting workflow triggers.

• Enhanced Payload Handling:

  • Efficiently manage large numbers of potential payload variations.
  • Precisely target workflows based on specific payload attributes.
  • Increase system adaptability to evolving payload structures.

Specific Examples:

• A product with numerous document types could benefit from pattern matching (e.g., "Documents.Project.*") or predefined lists of expected project identifiers.
• Optional payload fields could be handled gracefully, triggering workflows based on required data while ignoring optional values.

Impact of Feature

By providing a customizable payload comparison mechanism, we can significantly improve the system's flexibility and efficiency in handling diverse payload scenarios.