Due to my company policies, our passwords are expired every month.
I do change my passwords every month for all my “execute query” activities.
If i use 20 activity, i should change my password 20 times.
as far as i guess, there should be a way (like using variables) and after my password expire, i should change only one time and it should affects it all.
Create an asset in Orchestrator with the Credential Type and store all your credentials there. Use the Get Credentials activity in Studio to retrieve those credentials and apply them in the Execute Query activities.
When you change your system password, update it in the Orchestrator asset, and the new credentials will be used in all Execute Query activities during subsequent runs.
Assets is the best practice here and you don’t need any redeployment after every password change it will automatically fetch latest asset value you store on Orchestrator.
Hie @Krmi instead of saving your password in variable you can save it to Orchestrator Under Asset so you do not to update it on your code everytime . just changed it to Asset and it will update in your process as well.
my companies it dep. told me that i can not use it with studiox i dont have studio… for simple tasks :) but i got the solution anyway, its good for me so far.