Accepted Solutions
Heya B, rather than me writing an article here on how to do what you need, I've taken your code and what I grasp to be what you're trying to do and created a vCO Package file (see attached) of how I would approach this...
Import the package.
Notice that there is a Configuration Element with several attributes and empty values. You need to populate your values here in the configuration element. The workflow attributes will get their values from here.
Now take a look at the workflow - notice the attributes and how they point to the configuration element! Now look into the Scriptable task. The code there is far easier to read and it will be easier in the future to make a change to the East Coast and West Coast resources.
By defining these infrastructure specific resources as elements, you can reference them from many different workflows. And when you make a change for one of the resources that your workflow(s) use, it ONLY should need to be done in the configuration element, not the dozen or so workflows that all need to know what the West Coast Development Resource Pool is 
Hi Burke,
Maybe I do not understand entirely (as I am a VCO newbie). I have used your series & site (great by the way) to assist me to a degree. I can understnad how this would work if I was dealing with one site or cluster but, what happens I am dealing with different sites? Would I just have to create different workflows?
Maybe if i show some of my code, it might give more clarity into mind (probably not 
). This is not all of it but will give you the idea:
//Validate FQDN name structure
if (FQDN.match(new RegExp ("^([a-zA-Z0-9_-]+\.domain\.local)$"))) {
System.log("FQDN: " + FQDN + " is valid");
System.log("Return value: TRUE");
return true;
}
else {
System.log("FQDN: " + FQDN + " is not valid");
System.log("Return value: FALSE")
return false;
}
//Set var host based on location
if (vmDatacentreLocation == "WestCoast") {
var host = VcHostSystem.id(3025);
}
if (vmDatacentreLocation == "EastCoast") {
var host = VcHostSystem.id(3026);
}
//Set var vm based on OS
if (operatingSystem == "Win2K8R2x64STD") {
var vm = vm.id(4001);
}
if (operatingSystem = "CentOS6") {
var vm = vm.id(4002);
}
//Set var pool based on devEnvironment
if (devEnvironment == true & vmDatacentreLocation == "WestCoast") {
var pool = VcResourcePool.id(5001);
}
if (devEnvironment == true & vmDatacentreLocation == "EastCoast") {
var pool = VcResourcePool.id(5002);
}
if (devEnvironment != true & vmDatacentreLocation == "WestCoast") {
var pool = VcResourcePool.id(6001);
}
if (devEnvironment != true & vmDatacentreLocation == "EastCoast") {
var pool = VcResourcePool.id(6002);
}
//Set var datastore based on location and environment
//I do not have the code for this yet
//Launch task to deploy VM from template
actionResult = System.getModule("com.vmware.library.vc.basic").cloneVM(vm,vmFolder,name,powerOn,template,datastore,host,pool);
Thanks
B
Heya B, rather than me writing an article here on how to do what you need, I've taken your code and what I grasp to be what you're trying to do and created a vCO Package file (see attached) of how I would approach this...
Import the package.
Notice that there is a Configuration Element with several attributes and empty values. You need to populate your values here in the configuration element. The workflow attributes will get their values from here.
Now take a look at the workflow - notice the attributes and how they point to the configuration element! Now look into the Scriptable task. The code there is far easier to read and it will be easier in the future to make a change to the East Coast and West Coast resources.
By defining these infrastructure specific resources as elements, you can reference them from many different workflows. And when you make a change for one of the resources that your workflow(s) use, it ONLY should need to be done in the configuration element, not the dozen or so workflows that all need to know what the West Coast Development Resource Pool is
Hi Cdecanini,
If those attributes are already declared as general attributes inside the individual workflow (which runs to completion, no errors), do i have to set/declare them again in the encompassing workflow?
The problem comes in with the getCloneSpec action seems to be missing the general attributes, but they are in the individual workflow cause it works (hard to explain with pics).
Individual workflow: 'pic1' => works
encompassing workflow: 'pic2' => error 
Thanks
B
