FlowDesigner -how to move from one instance to another ?

Edwin23
Giga Contributor

I have  a Flow Designer in my Dev instance(Kingston 3a version). How to move this to production instance( as its not capture in updateset, and don't find any export option). Anybody face this situation ? Kindly suggest .

Thanks,

Edwin

1 ACCEPTED SOLUTION

Goran WitchDoc
ServiceNow Employee
ServiceNow Employee

Hi,

That is weird, it should be captured within the update set like this:

find_real_file.png

 

//Gƶran

View solution in original post

4 REPLIES 4

Goran WitchDoc
ServiceNow Employee
ServiceNow Employee

Hi,

That is weird, it should be captured within the update set like this:

find_real_file.png

 

//Gƶran

Also, the Applications have to match, I believe.  If your update set is in global application, but the flow is in a different application, it will not save to the global update set.

Ashvini Kadus1
Kilo Guru

Hi kedwin,

I would suggest you to keep flow designer in your test instance only. If you think, Basically a Flow Designer is the Test function which provides a handy interface for troubleshooting, And you need to perform tests on a test instance i.e Dev Instance, never on a production instance. Because, Actions that create such as a new record, will not roll back after a test run in the Flow Designer.

The item will remain in the instance as an artifact of the test. Also, other record changes and integration calls performed in the Flow Designer are real. So, after troubleshooting your flows within the Flow Designer, promote them to a test instance for testing with feasible data.

 

Regards,

Ashvini Kadus

find_real_file.png
www.DxSherpa.com

 

Kiindly mark helpful/correct if satisfied with the response.

 

 

Edwin23
Giga Contributor

Hi Goran,

 

Yes, as you said its captured in updateset. 

I used flowdesigner for non-global application, so its captured in Application's Default updateset. So i was unable to find that. Using your image, i search and found that..its captured. 

Now i re-capture that in separate updateset and moved to production instance. 

Thanks,

Edwin