mg1978
Enthusiast
Enthusiast

Current username coming as "internal" from a webview, with vCO client coming the right name.

Hi All,

I have a few workflows where I use the "Data binding" function in the presentation to bind the "Current username" or "User display name". If I start the workflows from the vCO client is this working, but if I start the workflow from a webview than I get "Internal" as "Current username" or "User display name".

This happen not only on one workflow or one webview, this happen on all webviews and workflows.

0 Kudos
20 Replies
mg1978
Enthusiast
Enthusiast

Hi,

is nobody here who can help me ?

0 Kudos
mg1978
Enthusiast
Enthusiast

Hi All,

I found a link fro 2010

http://communities.vmware.com/thread/267059

with the same problem. Is this perhaps a bug in vCO or have somebody a solution?

0 Kudos
ivand
VMware Employee
VMware Employee

Hello,

Which version of vCO do you use?

I need this to verify if this is an issue and to find a workaround

0 Kudos
mg1978
Enthusiast
Enthusiast

The vCO is running version 4.2.1 build 555 on a W2k8 R2 server and a SQL2005 DB.

0 Kudos
ivand
VMware Employee
VMware Employee

Thanks. I will check and will come back to you

Regards

Ivan

0 Kudos
igaydajiev
VMware Employee
VMware Employee

Looks like a bug.

At the same time #__username ("Current username") is working fine in mine environment. It returns user login name. It is a bit different than __userDisplayName, but  it might be something that can help you.

0 Kudos
mg1978
Enthusiast
Enthusiast

Hi

I try this and get the same error.

2103313.png

How can be addressed to VMWare ?

0 Kudos
ivand
VMware Employee
VMware Employee

I have tried this and in my environment #__username binding is working

What permissions have your user? Is he from administrators group or he has less permissions?

Regards

Ivan

0 Kudos
mg1978
Enthusiast
Enthusiast

I run the workflow and I have adminstrator rights.

Here are the binding.

2103313_1.png

0 Kudos
ivand
VMware Employee
VMware Employee

I am using same binding.

My question is more about do you use a user from vCO admin group or you are using a user which has set admin privileges?

0 Kudos
mg1978
Enthusiast
Enthusiast

Hi,

this is a user from the vCO admin group.

0 Kudos
igaydajiev
VMware Employee
VMware Employee

You can try with Default Value instead of Data Binding as type qualifier.

0 Kudos
ivand
VMware Employee
VMware Employee

Are you using custom WebView?

If yes, can you check your workflow with web operator?

Regards

Ivan

0 Kudos
mg1978
Enthusiast
Enthusiast

Hi,

sorry, will try this on monday.

0 Kudos
mg1978
Enthusiast
Enthusiast

Hi Igaydajiev

can you tell me how I can use the Default Value instead of Data Binding as type qualifier.

0 Kudos
igaydajiev
VMware Employee
VMware Employee

I am using "Defeault value" type qulifier instead of "Data binding" one and I am testing with the "web operator" webview distibuted as plugin for vCO and it is working as expected.

Untitled.png

0 Kudos
mg1978
Enthusiast
Enthusiast

Hi,

I try this with the default value and the wb opertator and still the same. The value is internal

2104565.png

If I use the client than is it working.


0 Kudos
ivand
VMware Employee
VMware Employee

I have tried several scenarios in my environment, I couldn't reproduce this issue (see attached video)

I am attaching and the workflow that I am using.

My environment is VCO applaince with AD 2008.

Can you attached server logs so we can try to find the root cause of this?

Also can you describe exactly what is your configuration and mainly LDAP setup?

And last question: Do you use custom web operator or default one that comes with vCO ?

Regards

Ivan

0 Kudos
BryanL
Contributor
Contributor

I'm running into this same problem and would be interested in a solution or workaround.  Same test case as mg1978.  I'm using the VCO appliance 4.2.1 build 555 and a custom webview based on the included template.  Logging into the webview with an AD user that has view,execute,inspect permissions.  The workflow is working fine aside from the strange value for #__username.

0 Kudos