You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The formula element allows the declaration of multiple workflow elements; however, there is no easy means to determine (looking strictly at the workflow definitions) the execution order without comparing (and inferring) such from the workflow timestamps.
Describe the feature
Discuss if a new field/fields is/are necessary to indicate a "root" or starting workflow (or task) to assist tooling/humans in analyzing the MBOM.
Possible solutions
Add a field to declare a "root" workflow (by its bom-ref); however it MAY (TBD) be possible to have parallel workflows all be considered root (conceptually initiated by the same "trigger" (event).
Drawbacks/issues...
These fields would need to optional as the underlying platform's tool used for generating an MBOM may not have full context/view of all workflows...
What if declared "root" does not match "timestamps"?
Alternatives
TBD
Additional context
None
The text was updated successfully, but these errors were encountered:
mrutkows
changed the title
[DISCUSS]: Need means to declare "root" workflow for a formula
[DISCUSS]: Need means to declare "root" workflow(s) for a formula
Jan 8, 2025
The
formula
element allows the declaration of multipleworkflow
elements; however, there is no easy means to determine (looking strictly at the workflow definitions) the execution order without comparing (and inferring) such from the workflow timestamps.Describe the feature
Discuss if a new field/fields is/are necessary to indicate a "root" or starting workflow (or task) to assist tooling/humans in analyzing the MBOM.
Possible solutions
Add a field to declare a "root" workflow (by its
bom-ref
); however it MAY (TBD) be possible to have parallel workflows all be considered root (conceptually initiated by the same "trigger" (event).Drawbacks/issues...
These fields would need to optional as the underlying platform's tool used for generating an MBOM may not have full context/view of all workflows...
Alternatives
TBD
Additional context
None
The text was updated successfully, but these errors were encountered: