Hey,
I had this problem. We have Windows and Linux blueprints, and for obvious reasons you can't have them using the same workflows.
I ended up creating OS decision workflows in vCO for each life cycle stage.. They just look at a custom property in the blueprint which will contain either "windows" or "linux". Then based on the value it will launch another vCO workflow that will carry out tasks specific to the OS.
The only thing that is worth noting about these decision workflows is that I ended up launching my configuration workflows asynchronously workflows then checking the state via wfToken.state.
e.g
System.log ("Waiting for aSync workflow to complete");
while (wfToken.state != "completed"){
System.log(wfToken.state)
System.sleep(5000);
if (wfToken.state == "failed"){
throw "Failed"
}
else if (wfToken.state ==""cancelled"){
throw "Cancelled";
}
Works nicely for us and you have the option to expand as much as you want.
