VMware Cloud Community
dcoulter
Enthusiast
Enthusiast

vCO 4.2.1 webview not auto populating default value for text field

Hello, can anyone confirm whether or not webviews in vCO 4.2.1 (Windows version) allows for setting a default value using an action with upstream fields/inputs as parameters?  It works fine for generating a pre-defined list of elements, but for some reason it doesn't work for a default value (string field, text box).

If I fill in the previous field and refresh the entire page it works - in an earlier version of vCO (vSphere 4.1) if I changed the previous field the text would auto update, no browser refresh required.  This works fine via the thick client by the way.

Possibly a similar issue to this post related to a security change in 4.2?   http://communities.vmware.com/message/1849034

Thanks,

David

0 Kudos
14 Replies
jamesbowling
VMware Employee
VMware Employee

I am having a similar issue but in both Perspectives and Webviews.  My actions that I am using to autogenerate fields are not populating.  Very odd.  I can't seem to find anything as to why this is not happening.  Doesn't seem to put out any errors or warnings.

James B. | Blog: http://www.vSential.com | Twitter: @vSential --- If you found this helpful then please awards helpful or correct points accordingly. Thanks!
0 Kudos
cdecanini_
VMware Employee
VMware Employee

Hi,

This is a pb in vCO 4.2.1. A KB article is being written to provide a fix.

Also future 4.2.X updates and ne next major version of the product will not have this issue.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
jamesbowling
VMware Employee
VMware Employee

Do we have an ETA on the release of the KB? Just wondering because a few of my workflows are not working as designed due to this.

James Bowling

Sent from my iPhone

James B. | Blog: http://www.vSential.com | Twitter: @vSential --- If you found this helpful then please awards helpful or correct points accordingly. Thanks!
0 Kudos
cdecanini_
VMware Employee
VMware Employee

Just noticed it was already published here.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
dcoulter
Enthusiast
Enthusiast

Thanks for the quick response, however, after downloading/installing the new patch and restarting vCO, I still get the same behavior.  I tried multiple browsers with the same result.

Can anyone confirm if the patch works for them?

0 Kudos
jamesbowling
VMware Employee
VMware Employee

Oddly enough that seems to break webviews.  I am now getting a 404 error trying to open a webview or perspectives.

James B. | Blog: http://www.vSential.com | Twitter: @vSential --- If you found this helpful then please awards helpful or correct points accordingly. Thanks!
0 Kudos
jamesbowling
VMware Employee
VMware Employee

Premature...sorry, like a dummy didn't check permissions on it.  And I can verify that this does fix the issue.

James B. | Blog: http://www.vSential.com | Twitter: @vSential --- If you found this helpful then please awards helpful or correct points accordingly. Thanks!
dcoulter
Enthusiast
Enthusiast

Are you running the appliance (Linux) or Windows for vCO?

0 Kudos
Burke-
VMware Employee
VMware Employee

I have a 4.2.1 Windows based server that required the updates... To address all my issues, I did the following:

Added

com.vmware.o11n.webview.htmlescaping.disabled=true

to my vmo.properties file

and applied the files as outlined in these two KBs:

http://kb.vmware.com/kb/2015178

http://kb.vmware.com/kb/2016770

I stopped my config service and server service before making the changes above. After starting them back up, my server seemed good.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you!

Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator
for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
jamesbowling
VMware Employee
VMware Employee

Appliance.

James Bowling

Sent from my iPhone

James B. | Blog: http://www.vSential.com | Twitter: @vSential --- If you found this helpful then please awards helpful or correct points accordingly. Thanks!
0 Kudos
dcoulter
Enthusiast
Enthusiast

Hi James, I applied the changes per Burke suggested (thanks Burke!) for my Windows vCO installation, however now I'm getting the 404 error messages that you were referring to (also denied to log into the thick client).  Do you mind sharing what permissions/etc you modified to get past this?

Thanks,

David

0 Kudos
jamesbowling
VMware Employee
VMware Employee

I am not 100% sure what the permissions would be on the Windows installation but I had to make sure that the file that was replaced was readable by the vco user.  So in my case, it was permissions of 644, owner of vco, and group of vco.

James B. | Blog: http://www.vSential.com | Twitter: @vSential --- If you found this helpful then please awards helpful or correct points accordingly. Thanks!
0 Kudos
dcoulter
Enthusiast
Enthusiast

Very strange - after all patches per Burke applied I can't log in at all (web or thick client), config is intact (all green, no changes), file system security where vCO is installed is wide open.  Looking into the logs now, attaching them in case someone has seen this before...

0 Kudos
dcoulter
Enthusiast
Enthusiast

Wow - not sure what happened there - backing out the patches still didn't help the login issue, and even uninstalling/re-installing vCO - I've somehow managed to corrupt that server to the point I can't log in.  Luckily I had another Windows 2008 R2 VM and was able to install vCO and backup the config from the original machine and restore it to the new one, pointing to the same database.  This time I only installed the patch from kb 2015178 and added the line below to vmo.properties.  Success on login and the webview behavior is also working great, thanks everyone for the help, it's been a long week!

com.vmware.o11n.webview.htmlescaping.disabled=true

                        David Coulter | VCDX #72 | http://www.sovsystems.com | Twitter: @dcoulter_
0 Kudos