How credential alias are linked in flow designer actions?

[Rohith Sureshk1]

we have ad v2 actions in flow captured in update set, but it references the connection alias , so in upper isntance,(Where the plugin has to be installed from scratch) if we download the adv2 plugin from scratch, will it create new alias with diff sys id. if yes, then the reference will be broken in upper instance? Connection and credential xml wil be imported. but worried about alias as it is used in flow actions. what will happen to midserver script files inside the actions?

Please provide the best practices to follow before deployment. Thanks

[Bhuvan]

@Rohith Sureshk1 

Follow below thread that can help you with best practices for importing Connections & Credentials

https://www.servicenow.com/community/developer-forum/connection-record-not-tracked-in-update-set/m-p...

https://www.servicenow.com/community/queensland-snug/understanding-connection-amp-credential-alias/b...

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[Ankur Bawiskar]

@Rohith Sureshk1 

you need to export and import the Connection and Credential XML to next instance.

Once you use the same records, the sysId remains the same and flow will automatically pick those for your Step.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Rohith Sureshk1]

but the flow actions references the credential alias right? wont it break as upper instance might contain the diff sys id for alias as plugin is new?

[Ankur Bawiskar]

@Rohith Sureshk1 

why will it break as you are exporting and importing the same record and the sysId will remain the same for Credential alias record

If my response helped please mark it correct and close the thread so that it benefits future readers.