VMware Cloud Community
KRAEMS
Enthusiast
Enthusiast
Jump to solution

Specifying a root object for an input parameter in the vSphere Web Client

Hello All,

I see that appliance update 7.1.0 released August 24th has fixed the 'Specifying a root object for an input parameter chooser in presentation does not work' issue (http://pubs.vmware.com/Release_Notes/en/orchestrator/vrealize-orchestrator-71-release-notes.html#res...).  Awesome. 

In my experience, I can run a workflow in workflow designer that does this, but, if I run the same workflow from the vSphere Web Client, running through the web client also results in needing to browse the entire inventory tree.  I *think* I remember seeing some discussion on this some time ago ~ but can't remember outcome. 

Can anyone substantiate that this is the case (that specifying a root object is expected to work when running workflows from designer, and expected not to work when running from the web client)?  If this is expected behavior, is there any intent for the web client to also observe the root object specified? 

Appliance version 7.1.0.19044 Build 4276164

Workflow Designer version 7.1.0.4262825

Java version 1.8.0_92

vSphere Web Client version 6.0.0 Build 2997665

Thank you

Reply
0 Kudos
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

Yes, this is the expected behavior. The issue marked as fixed in the release notes is applicable only to vRO Java client (workflow designer) and not to vSphere Web client.

Currently, both clients have completely different code bases, so fixes made to one of them are not applied automatically to the other. vSphere Web client doesn't support all of presentation functionality of vRO Java client (including the root object property), and this is not very likely to change, at least not before code bases of the clients get closer to allow sharing of code/components between them.

View solution in original post

Reply
0 Kudos
1 Reply
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

Yes, this is the expected behavior. The issue marked as fixed in the release notes is applicable only to vRO Java client (workflow designer) and not to vSphere Web client.

Currently, both clients have completely different code bases, so fixes made to one of them are not applied automatically to the other. vSphere Web client doesn't support all of presentation functionality of vRO Java client (including the root object property), and this is not very likely to change, at least not before code bases of the clients get closer to allow sharing of code/components between them.

Reply
0 Kudos