While following this blog you likely were looking to use the vCO extensibility that is included with the VRA (formerly vCAC) appliance. As it turns out there is an known bug in the 6.1 and 6.1.1 that will likely cause you some heart and head aches. I have had this occur in two environments now and am hopeful I can save you the pain.
The directions in using my post about “utilizing the workflow template” will succeed with no issues. The larger issue is when you try to use that as a wrapper for a more robust workflow. No matter if you are using powershell, AD, SQL, or others it will fail on build (and possibly other states) with this error. “Unable to serialize object of class : ch.dunes.vso.sdk.SDKTypeConvertor_server$1″
This also will occur on external vCO instances and Joerg Lew a colleague of mine has already covered that in his post.
Here is the KB that will walk you through the fix.
I have tested this on my embedded instance and it works flawlessly. Just to help you out here is what I have been running to fix the embedded vCO instance.
#backup the current files
mv o11n-model-5.5.2.jar o11n-model-5.5.2.old
mv o11n-sdkcenter-5.5.2.jar o11n-sdkcenter-5.5.2.old
Then download the zip file and extract all of the files (you will have to do this on another machine). Then upload via SCP into the /usr/lib/vco/app-server/deploy/vco/WEB-INF/lib
#restart the service
service vco-server restart
This should solve any issues with utilizing the workflow template usage.