Hi Ron, I think we are getting somehwere closer ... looking at your screenshot you can actually see that your CALLED vCO workflow expects a GUID in "string" format, which should look sth like this: "3F2504E0-4F89-41D3-9A0C-0305E82C3301".

So you now have to look at the place where you CALL the vCO workflow. This is probably inside the vCAC workflow stub "WFMachineProvisioned" via the vCAC Desginer. Or how did you register/setup your vCO workflow? So in the place where you CALL your vCAC workflow you have to make sure that you pass the ID (GUID) of the vCAC machine being provisioned as a string (and not as a native "object" or property thereof).

If in doubt just send another screenshot of the CALL to your vCO Workflow and we have another look.

Regards,

Ronald