Hi,
Just a simple one - would it be possible to add a setting to change the default language for new projects (VB/C#)? Similar as we can change default locations etc.
For those more “experimental” of us that do quite a bit of throwaway projects to test some functionality in isolation, it’s easy to muscle-memory click the Create and facepalm after realizing it’s the wrong language, but still need to wait for the whole new process creation to finish.
You can set a policy to set a default language for new projects and various other project settings in ‘Automation Ops’ in the Orchestrator, I believe this should do what you wish.
You can set a default project type and even restrict to only C# or VB I believe.
Ok, that’s one way.
But what I meant is within the Studio itself, from a user level - not everyone is using AutomationOps (it’s not an option on standalone Orchestrator + there are standalone licenses as well that are not connected anywhere + some just… don’t 
).
If I’m understanding it correctly, it would also change it for everyone, and that’s not exactly what I’m after.
Fair point.
Automation ops can be designed to have multiple policies so you can apply them to different user groups at your discretion, but if that still doesn’t work for you I am not aware of a setting for this on the desktop level. Perhaps in the configs somewhere, but its not an option I am aware of being exposed.
That should make it even easier - so the Studio itself does support having a configured default project language, it looks like (and I agree with your conclusion here) that it’s just not exposed.
Hi @andrzej.kniola,
If you want to achieve this only at user level, then user can use the below toggle under Studio Design settings from backstage view to change the default language.
Once changed here, settings would remain enabled unless that user decides to change it again or upgrade studio version.
Alternatively, if you would like this setting to be in place for all users, applying Governance policy would be the best way. There are 2 ways of applying Governance - 1) classic governance policy 2)modern governance policy(automation ops).
Classic governance policy is available to all(on-prem/cloud). It can be simply applied by creating a folder in orchestrator, adding an asset and setting the values in policies config file. and adding the users in that folder on whom you want to apply that policy on. Below is the screenshot of the parameter from policies config json file.
If you are interested in going forward with this classic governance policy, let me know and I can share the steps to enable the same.
Hope this helps.
Regards
Sonali
I cannot believe neither of us found it 
Thank you, that sorts it out 