Hi,
I just want to know how I can make it possible to display linefeeds in a workflow presentation with vCO-WebOperator-WebView in the new vCO-Version 4.2.1?
In the old version it was easy, I just used the HTML-Tag <br>, but in the new version it will write it as text as you can see here:
When I use the vCO-Client it will work when \n is used as you can see below, but also not in the WebWiew (see above):
Please can you give me a hint.
Best regards
Rainer
Set this property: com.vmware.o11n.webview.htmlescaping.disabled = true
As described in the vCO 4.2.1 release notes.
Christophe.
This feature was introduced in 4.2.1. But actually it can be switched off using some properties,
You can chek here :
http://communities.vmware.com/thread/333153?start=15&tstart=0
Hi igaydajiev,
sorry, your answer and the link you wrote got me somehow confused.
Which property you mean? "Hide parameter input"? I don't want to hide the description, I want to show it but including linefeeds not with \n or <br> as text.
Maybe I didn't explain exactly.
This is what I want to see (screenshot created with old vCO version):
To display this I used this variable in the Description field of the presentation group:
The variable contains this value:
info = "Here some information:<br>OS=...<br>CPU=...<br>RAM=...";
But in the new vCO-version 4.2.1 the HTML-Tags <br> won't work anymore, nor the javascript newline character \n.
Best regards
Rainer
Set this property: com.vmware.o11n.webview.htmlescaping.disabled = true
As described in the vCO 4.2.1 release notes.
Christophe.
Hi Christophe,
great, that's what I meant , many thanks.
Is there any guide which describes other configuration properies which are available to use? Maybe some others would be helpful, too.
Best regards
Rainer
The supported ones should be documented in the vCO documentation. If one is missing then this is a documentation bug: Something that can be fixed by opening a support request.
Christophe.
Sorry about that.
Actually the usefull information was on the seconnd page, comment #15
This should be the correct link pointing to the message.
http://communities.vmware.com/message/1888606#1888606
...