BernhardSie's Posts

In vRO 7.6 client the Tab 'Permissions' is missing, in vRO clients < V7.6 Tab 'Permissions' is present: Any ideas? Thank you!
Thank you for your answer. The user in the vRO client is a member of 'Admin group' "vsphere.local\Administrators" In vRO clients V7.4 und V7.5 same user (and same SSO server) is used, ... See more...
Thank you for your answer. The user in the vRO client is a member of 'Admin group' "vsphere.local\Administrators" In vRO clients V7.4 und V7.5 same user (and same SSO server) is used, but this problem doesn't occur. I changed the line <allowedMask>vf</allowedMask> to <allowedMask>vef</allowedMask> in the corresponding pom.xml file '...\o11nplugin--package\pom.xml', and installed it on vRO V7.6, but the menu entries (like "Rebuild package", "Delete...", "Edit", ...) remain disabled. Thank you for your support.
Some entries (like "Rebuild package", "Delete...", "Edit", ...) are disabled in menu opened by 1. Selecting 'Administer' in the selection box on the top of the VMware vRealize Orchestrator cli... See more...
Some entries (like "Rebuild package", "Delete...", "Edit", ...) are disabled in menu opened by 1. Selecting 'Administer' in the selection box on the top of the VMware vRealize Orchestrator client workspace. 2. Clicking the 'Packages' tab in the upper left corner of the left pane in the VMware vRealize Orchestrator client workspace. 3. Clicking right on the entry of a package (in our case 'com.vmware.library.fujitsuSVS.eLCM') In Versions < V7.6 of vRealize Orchestrator client the entries are enabled, see e.g. vRealize Orchestrator client V7.4 Because of this 'Uninstalling a plug-in from vRealize Orchestrator' described in 'https://kb.vmware.com/s/article/2064575'           :      4. Right-click the package to delete and click 'Delete element with content'           : is not possible. Thank you for any help...
We had the same problem using the new HTML5 webclient. After a time consuming "trial and error" phase (deleting input parameters step by step and so on) the problem was gone when an input paramet... See more...
We had the same problem using the new HTML5 webclient. After a time consuming "trial and error" phase (deleting input parameters step by step and so on) the problem was gone when an input parameter using presentation property "Hide parameter input" was deleted. Corresponding line in the xml file of the workflow: '<p-qual kind="static" name="notVisible" type="boolean" ><![CDATA[true]]></p-qual>' So our idea was to put the value "true" explicitly into the value field of that property and the problem was gone: The line in the xml file of the workflow changed to '<p-qual kind="ognl" name="notVisible" type="boolean" ><![CDATA[true]]></p-qual>' May be it's a bug in the different presentation libraries and/or different presentation constraint language used in new client.
I want to use the HTTP-REST plugin contained in vCenter Orchestrator. I have to invoke a service by REST api, but a value has to be set as cookie in it's api (not as input parameter). Is it pos... See more...
I want to use the HTTP-REST plugin contained in vCenter Orchestrator. I have to invoke a service by REST api, but a value has to be set as cookie in it's api (not as input parameter). Is it possible to use cookies in the HTTP-REST plugin ? If I execute the workflows "Add a REST operation" or "Invoke a REST operation" I can't find any input fields ? I'm using vCenter Orchestrator Version 5.5.2 (and 5.5.1). Thank you for any help! More by chance I found out to set cookie value by method     setHeader(String header, String value) see 'Orchestrator Client'->'Tools'->'API Explorer'->'REST'->'RESTRequest' In my case I have to set a 'SESSIONID' in a cookie and so I added 'setHeader' method to my workflow:             :      var request = myrestOperation.createRequest(inParamtersValues, content);             : ->  request.setHeader("Cookie", "SESSIONID=" + sessionId);             :      var response = request.execute();             :