Does workflow ID stay same between lower environments and production?

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi everyone -
When migrating workflows from lower environments to higher PROD environment, I see the workflow ID stayed same for multiple workflows. I assumed this was coincidental at first but looks like a pattern. Anyone can confirm this? Does it always stay the same between environments when promoting to higher? We observed this via config hub.

2

Hi @sushantkulkarni ,

I think you are including id attribute in the workflow JSON when you are migrating. Since it is unique id and it is not referencing any production JSON item, it is setting that id for that workflow. But if you upload the JSON without that id parameter while migrating, you will get a new id in production.

Thanks.

1 Like
3

I have always had to empty out the ID fields when uploading a workflow json file to production, I have not tried via Configuration Hub however, was that what you did in your case?

1 Like
4

Hi @kdfreeman - It does look like that is what caused this. Interesting find! I wasn’t aware that providing an ID gives it preference over generating a random one. Thanks for your insights!

5

@Swegmann Yes, in my case I hadn’t emptied out the IDs, and perhaps that is what caused it to retain the ID.