1. Implementing Product Management
  2. Use Business Events for Workflows

Use Business Events for Workflows

You can subscribe to workflow status change business events for workflows.

The Workflow Status Update Event is raised whenever an eligible workflow transitions from one status to another. This includes promotions, demotions, repeated status transitions, cancellations, and failures.

Use this event to enable downstream applications to respond as the workflow progresses rather than polling for status changes or monitoring only selected workflow milestones.

The event includes both the previous and current workflow status, allowing integrations to identify exactly how the workflow has progressed. The initial event payload contains the following key identifiers:
  • Change ID
  • Change Notice
  • Organization ID
  • Base Change Type Code
  • Change Type Value (internal name)
  • Old Status Type
  • New Status Type
  • Old Status Internal Name
  • New Status Internal Name

The event payload is intentionally lightweight. Use the identifiers in the payload to retrieve additional workflow details through the appropriate enrichment call. Use the Base Change Type Code to identify which enrichment REST call to use.

This event supports engineering change orders, commercial change orders, change orders without revision control, change requests, deviation change requests, problem reports, and corrective actions.

Important Considerations

  • Business events configured before update 26D remain available and are fully supported. The Workflow Status Update Event extends the event framework to provide broader lifecycle coverage without affecting existing integrations.
  • New item requests use their own business events.
  • You can call your preferred enrichment call to retrieve additional workflow details based on your integration requirements.
  • Use the Base Change Type Code to identify which enrichment REST call to use to retrieve more details.