VMware Cloud Community
Kagome
Enthusiast
Enthusiast
Jump to solution

vRealize Orchestrator 8.0.1 - general questions

Good Evening,

I'm an old men which started with vCenter Orchestrator 5.5 and developed until today over 250 workflows.

That every update is a pain in the ass is nothing new for me. (5.5 -> 6.x -> 7.x)

In the past, my solution was to put all workflows, actions, configurations, ressources in a package and export it, and import on the new Orchestrator Appliance.

After that spend a few days with password encryption and the sheduled workflows and everything was good.

Today i tried to upgrade from 7.2 to 7.4 because i wanted to try the migration to 8.x..

The 7.4 installation is full of errors in the logfiles so I deploeyed a fresh 8.0.1 Installation..

After testing now a little bit I have a few questions:

- Old Java Client is gone forever?

- What is the latest Version with the old Javaclient? I'm not a fan of Java at all but that client was useable.

- Does anyone of the developers use the Orchestrator with the new HTML Client?

- Will there be in a future update the "tree-view" come back to the new Client for workflow, actions and so on? It is currently  a nightmare in useability to explorer the workflows - especially if you don't remember the name or "tag".

- Will there be a licence change in the future? Currently I use the standalone Orchestrator with vCenter License.

Tags (1)
1 Solution

Accepted Solutions
stevedrummond
Hot Shot
Hot Shot
Jump to solution

Old Java Client is gone forever?

Yes the java client is officially dead.

What is the latest Version with the old Javaclient? I'm not a fan of Java at all but that client was useable.

vRO 7.6 allows for a combination of Java clienta and web client

Does anyone of the developers use the Orchestrator with the new HTML Client?

It's what almost everyone uses, and yes it's incredibly painful

Will there be in a future update the "tree-view" come back to the new Client for workflow, actions and so on? It is currently  a nightmare in useability to explorer the workflows - especially if you don't remember the name or "tag".

The tree view is not coming back

Will there be a licence change in the future? Currently I use the standalone Orchestrator with vCenter License.

There are licensing changes since 7.something (I want to say 7.5?) with the introduction of multi-tenancy in vRO. This requires a vRA Adv or greater licence.

View solution in original post

5 Replies
stevedrummond
Hot Shot
Hot Shot
Jump to solution

Old Java Client is gone forever?

Yes the java client is officially dead.

What is the latest Version with the old Javaclient? I'm not a fan of Java at all but that client was useable.

vRO 7.6 allows for a combination of Java clienta and web client

Does anyone of the developers use the Orchestrator with the new HTML Client?

It's what almost everyone uses, and yes it's incredibly painful

Will there be in a future update the "tree-view" come back to the new Client for workflow, actions and so on? It is currently  a nightmare in useability to explorer the workflows - especially if you don't remember the name or "tag".

The tree view is not coming back

Will there be a licence change in the future? Currently I use the standalone Orchestrator with vCenter License.

There are licensing changes since 7.something (I want to say 7.5?) with the introduction of multi-tenancy in vRO. This requires a vRA Adv or greater licence.

carl1
Expert
Expert
Jump to solution

One word of warning on the old Java client vs. H5 client.  If you edit a workflow using the H5 client, you can no longer edit it using the legacy client.  So, for any given shop, choose wisely. 

Carl L.

0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

The tree view is not coming back

Watch out for 8.1; there will be a little surprise there Smiley Happy

0 Kudos
stevedrummond
Hot Shot
Hot Shot
Jump to solution

So I heard late Friday night! It is definitely also a "little" surprise compared to what else is coming...

0 Kudos
agajjar
Enthusiast
Enthusiast
Jump to solution

  1. Old Java Client:

    • The old Java client has been deprecated, and its use is no longer supported. The latest versions of Orchestrator now leverage a new HTML client.
  2. Latest Version with Old Java Client:

    • As of my last knowledge update in January 2022, UiPath has transitioned away from the old Java client. It's recommended to use the latest version of Orchestrator with the HTML client for an enhanced and more secure experience.
  3. Developers Using HTML Client:

    • Many developers have successfully transitioned to the new HTML client, finding it efficient and user-friendly. The HTML client is continually updated to provide a better user experience.
  4. Tree-View in the New Client:

    • The inclusion of a "tree-view" in the new client is subject to UiPath's development roadmap. Feedback from users, such as yours, is crucial in shaping future updates. While I don't have real-time information on updates post-2022, it's advisable to check UiPath's official release notes for the latest features and improvements.
  5. License Changes:

    • As of my last knowledge update, there were no widespread announcements about significant license changes. However, licensing structures can evolve, so it's recommended to check UiPath's official communication channels or contact their support for the latest information on licensing.
0 Kudos