CathyBr
Enthusiast
Enthusiast

NavigationRequest to "vsphere.vco.workflowItem.monitor"

Hi,

we are trying to implement a connection from our plugin to the vco plugin.  We retrieve a set of Workflows which are necessary to complete an action, and show them in a list.

For each workflow, we would like to create a link, and when the user clicks on it,  we would like to navigate to that specific workflow item in the vco plugin.

So our code Looks like this:

//the workflow has been retreived from the orchestrator rest api, and looks like this:

var workflowID = "vco:WorkflowItem;vco:bd5ab44f-5d07-4776-98f1-a2bfabfc5a36,vco:WorkflowItem,https://<ipaddress>:8281/vco/api/wokflows/11352cf1-b8c4-437c-afe9-76d7209aa5bc/";

var targetViewId = "vsphere.vco.workflowItem.monitor";

WEB_PLATFORM.sendNavigationRequest(targetViewId, workflowID);

When this is called, nothing happens, and in the virgo.log I see the message:

org.springframework.Flex.core.DefaultExceptionLogger  The following exception occurred during request processing by the BlazeDS MessageBroker and will be serialized back to the client:  Flex.messaging.MessageException: No destination with id "objectReferenceService" is registered with any service.

So could you please tell me, if I am doing it wrong or if this is not possible?  When I manually navigate to this item, and look at the URL, it seems that my input would be correct.

thanks

Cathy

3 Replies
laurentsd
VMware Employee
VMware Employee

I assume you are using Web Client 6.0.  Unfortunately there is a bug with the sendNavigationRequest API in Web Client 6.0 that was reported earlier in this forum.  This is fixed in the upcoming 6.0u1 update but we are still trying to find a work-around for 6.0.

To be precise sendNavigationRequest works only in 2 cases in 6.0:

- when not using a target object id

- when using a target object that was visited before in an html view

CathyBr
Enthusiast
Enthusiast

Hi Laurent,

thanks for the answer, at least I don't have to spend any more time trying to figure it out.

Cathy

0 Kudos
nklein1
Contributor
Contributor

Seeing that this post is almost 6 months old, has there been any progress on a work-around for this bug? (Preferably something that's compatible with 5.5.1 and 6.0.1 as well)

0 Kudos