JohnDanter2
VIP Member
Hi folks
If you are making Orchestations for external folk to call and test, how are you guys going about ensuring the specific accounts (and E1 linked Roles) they are using to connecting INTO E1 from outside have access to the UDO Orchestrations you are creating.
We are currently going through a large development whereby I am making new ORCHs almost weekly and the .NET team here are constantly having to ask CNC for UDO access to see and the run the new ORCHS in Postman or in .NET etc.
There must be a better way to do this. Is there not a *ALL view access option for ORCHs and SREQs etc?
Thanks
John
If you are making Orchestations for external folk to call and test, how are you guys going about ensuring the specific accounts (and E1 linked Roles) they are using to connecting INTO E1 from outside have access to the UDO Orchestrations you are creating.
We are currently going through a large development whereby I am making new ORCHs almost weekly and the .NET team here are constantly having to ask CNC for UDO access to see and the run the new ORCHS in Postman or in .NET etc.
There must be a better way to do this. Is there not a *ALL view access option for ORCHs and SREQs etc?
Thanks
John
Last edited: