Hi Community -
I'm working on a feature to automatically check out/publish call flows over API so we can avoid a situation where our most recent common module version isn't being consumed by our production call flow. We use A LOT of common modules and going in and editing/publishing each one my hand is very error prone.
First, I'm using the following API to check out the flow:/api/v2/flows/actions/checkout
When i look at the call flow in the UI, I see that the working copy has the most recent version of the Common Module referenced.
Then, I use the following API to publish the flow:/api/v2/flows/actions/publish
When I look at what was published, the new version of the call flow is still referencing the old version of the Common Module.
However, if i check out the call flow via API, then publish the call flow via the UI, the new version of the Common Module is referenced.
I would assume that publishing via API should be no different from publishing via the UI, but apparently there is.
Any idea what i might be doing wrong here?
Thanks,
#ArchitectureandDesign#Integrations------------------------------
Cory King
IT Lead
Interstate Gas Supply, Inc.
------------------------------