Dear Forum Members,
while going through the new licensing tutorial on the academy, I came across an important concept as shown in figure below.
If I upload 50 attended concurrent licenses and 50 attended named user licenses on the Orchestrator and a designated Named User connects his/her robot to the Orchestrator then in the documentation it states that the concurrent license will be consumed.
However at my company, some use cases require 24/7 robot availability for the named user and some need only on the need-to-use basis. Is there any way to isolate the concurrent and named users for attended robots for this capability? Or is this something planned for the future? I expect the Orchestrator to further subdivide the Attended licenses page into two parts: Named & Concurrent.
The only workaround for the isolation of attended concurrent and attended named users is to manually create a separate tenant? Like for example Tenant_1_Named_Users, Tenant_1_Concurrent_Users? It will make the management of use-cases and automations a big hassle in big organizations with hundreds of use-cases…
Best.