SOLVED:
My own stupidity is at fault. The vCO Endpoint field value is populated dynamically, since there's the possibility that you can use different endpoints for each workflow. So no manual entering of the value is needed.
My error was, that I have saved a new designer workflow iteration without the InvokeVcoWorkflow activity and have been editing an older one, which was not executed:|
Recently I was forced to reinstall my vCO appliance and after that my edited vCAC Designer workflow cannot recognize the vCO Endpoint:
This results in the named vCO workflow not triggering when needed. When trying to edit the triggered workflow, instead of the vCO workflow browser I get an error:
The vCO Enpoint itself in vCAC is working perfectly fine, the default Workflow Stubs are triggered without issues. I have used the same vCO Endpoint Name in the Designer as the Endpoint Name in vCAC. Adding a new InvokeVcoWorkflow activity presents the same issue. I may be wrong, but as far as I remember, the value of this box should be filled automatically, since the Designer pulls the vCO Endpoitn name from the Model Manager database?
Thank you in advance for any tips.
EDIT:
I just noticed that the status of the vco service in the vcac vami is blank:
Could this contribute to the issue? Like I said, the vCO endpoint under Infrastructure > Endpoints > Endpoints works fine. also tested the same under Administration > Advanced Services > Endpoints. The Test Connection is successful.