Issues with flow action conversion to Fluent in SDK version 4.1.1

Brady Holliday
Tera Guru

Howdy,

 

I have recently been working on converting existing applications over to fluent and I came across another little bug that I'm curious if anyone else has noticed.

 

When I do a now-sdk transform it appears that flows, subflows, and flow actions are getting converted to fluent, but when migrating them up via the now-sdk, they fail to load into the instance properly (often resulting in the flow/subflow/action not being found).

 

My most recent example of this is I built a simple little flow action that converts an integer into duration that can be used by the wait for duration flow logic. When I moved it up to test it failed to load into the instance and required me to export out the XML of the flow action and import it into the other environment (which can be done via the sdk, it just requires downloading the metadata and finding the proper xml file to keep instead of convert).

 

A simple way to reproduce would be to:

1. Create a brand-new flow action

2. Run 'now-sdk transform' to pull the new action in and transform to fluent

3. Run 'now-sdk build' & 'now-sdk deploy' to a different instance

4. Witness the flow action not being deployed properly

 

Let me know if anybody else has had this issue/if you have found a simple way to work around it.

0 REPLIES 0