Material Event Flows (Epic)

Feature Request: Material Configuration Event Flows

Summary:
Introduce an Events tab within the BOE Pro material configuration that allows users to define automated, flow-like event rules triggered by changes in BOE Pro (e.g., BOM updates) and propagate those changes to external systems and Contractor Edition. This will provide a flexible, Microsoft Flow–style configuration experience for integrating material-related events across connected systems.

Problem Statement:
Today, when material-related changes occur in BOE Pro (such as adding or updating a BOM on a proposal), there is no configurable, automated way to trigger corresponding actions in external systems or Contractor Edition. Any synchronization or downstream updates must be handled manually or through rigid, hard-coded integrations. This leads to inconsistent data across systems, extra manual work for users, and increased risk of errors when BOMs or material configurations change.

Proposed Solution:
Add a dedicated Events tab to the material configuration in BOE Pro. Within this tab:

• Users can select any configured external connection (e.g., ERP, PLM, or other integrated systems) as a target for the event.

• Users define event trigger criteria based on actions in BOE Pro (e.g., “When a BOM is added to a proposal,” “When a BOM is updated,” “When a material is changed”).

• When a trigger condition is met, the system can execute one or more actions against the selected external connection, such as:

  • Creating a new version of the BOM in the external system.

  • Updating existing BOM or material records.

  • Sending a structured payload (e.g., via API) to notify or synchronize the external system.

• The configuration experience should follow a Microsoft Flow–style pattern, where users can:

  • Choose a trigger (BOE Pro or Contractor Edition events).

  • Add conditions/filters (e.g., proposal type, material category, customer, etc.).

  • Chain one or more actions with configurable parameters (e.g., target system, entity type, mapping fields).

  • Support events across:

    • External systems integrated with BOE Pro.

    • Internal BOE Pro events (within the same environment).

    • Contractor Edition, when “Use Contractor Materials” is toggled on, allowing events to propagate material changes between BOE Pro and Contractor Edition.

  • Provide validation and testing tools so users can test an event configuration before enabling it in production (e.g., test run with sample data).

  • Include basic monitoring or logs so users can view recent event executions, successes/failures, and error details if any actions fail.

Benefits:

• • Reduces manual work by automating material- and BOM-related updates across BOE Pro, external systems, and Contractor Edition.

  • Improves data consistency and integrity by ensuring that BOM and material changes in BOE Pro are automatically reflected in connected systems.

  • Increases flexibility by giving users a no-code / low-code, flow-like configuration experience without requiring custom development for each integration scenario.

  • Enhances governance and traceability through event logs and error reporting, making it easier to diagnose integration issues.

  • Supports scalable, repeatable workflows for organizations managing complex material and BOM lifecycles across multiple systems.