Add a new idea Subscribe
Categories Extensions
Created by Guest
Created on Mar 6, 2025

RELATED IDEAS

ConnectorStateListener

Please, fill in the below fields to enable the processing of your idea.

Who would benefit?

  • Developers implementing ServerExtensions, InboundDataExtensions and others.

  • Teams looking to improve efficiency and responsiveness in processing ConnectorStates.

  • Any inriver users who need real-time ConnectorState processing without delays.

What impact would it make?

  • Reduces dependency on Scheduled Extensions, enabling immediate processing.

  • Enhances performance by allowing ServerExtensions to create ConnectorStates at runtime without having to process data there.

  • Optimizes inbound data processing, allowing quick reactions to incoming data without delays.

How should it work?

  • ConnectorStateListener should be able to filter which ConnectorStates it listens to.

  • Like other Listeners, it would trigger when a ConnectorState is created, updated, or deleted, but with the ability to filter by:

    • ConnectorId

    • Action

  • ConnectorIds could be configured in a CVL or another configuration method.

Why is it needed?

  • Some use cases require immediate action on ConnectorStates without waiting for a scheduled job.

  • Improves flexibility and efficiency in handling ConnectorState-driven processes in inriver.


Additional feedback, background or context:

  • Enables event-driven processing, eliminating reliance on scheduled intervals.

  • Supports ServerExtensions and InboundDataExtensions, allowing them to trigger processes efficiently instead of handling them immediately.

  • Reduces implementation complexity by removing the need for periodic checks.

  • Additional Feature Request: When triggered inside a ServerExtension, the updated fields should be accessible, allowing developers to determine exactly what changed instead of handling the entire entity blindly.

  • Attach files