SBOM management workflow not starting after SBOM update in tc-12.4

PLM Teamcenter
, , , , , , , ,
1

We’re having issues with SBOM management workflows not automatically starting after SBOM updates in tc-12.4. When software bill of materials are modified - either component additions or license changes - the compliance review workflow should launch automatically, but nothing happens. The workflow-trigger appears to be completely inactive.

Event subscription shows:


Event: SBOMModified
Workflow: SBOM_Compliance_Review
Enabled: TRUE
Last Triggered: NEVER

Manual workflow initiation works perfectly, but the automatic workflow-trigger on sbom-update is broken. This delays-review of compliance changes, which is critical for our export control processes. The event-mapping configuration looks correct, but the workflow-engine isn’t responding to SBOM modification events. Any insights on fixing workflow triggers for SBOM events?

2

Look at your workflow-trigger configuration in the template definition. The trigger needs to be set up with the correct launch criteria for SBOM events. In tc-12.4, there were changes to how workflow launch criteria are evaluated. If your template was created in an earlier version and migrated, the launch criteria syntax might need updating to match the new workflow-engine requirements.

3

I’ve worked with SBOM workflows before. The sbom-update event in tc-12.4 has specific requirements for triggering workflows. Make sure your event-mapping includes the correct object type filter. SBOM objects can have multiple subtypes, and if your workflow trigger is filtering for a specific subtype that doesn’t match what’s being updated, the workflow won’t start. Also check that the event subscription is set to fire on both component additions and license modifications.

4

Don’t overlook the workflow-engine’s event subscription filters. Even if the event is being generated, the workflow might have additional filtering criteria that’s preventing it from starting. Check for any conditional launch criteria in your SBOM_Compliance_Review workflow template. There might be attribute checks or state requirements that need to be met before the workflow-trigger activates.