Let me first disclaim that my understanding of the situation I describe herein is a little tentative, so feel free to let me know if I am misunderstanding anything.
In our environment we have vCAC 6.1 and vCO 5.5.2. We also installed the Infoblox plug-in in vCO. This installation customized the WFStubBuildingMachine and WFStubMachineDisposing workflow stubs in vCAC to add calls to the Infoblox vCO workflows for IP address management. That's all dandy until you come along and run the Install vCO customization workflow in vCO, which wipes out the customization to the vCAC workflow stubs previously done by the Infoblox plug-in installation.
How do you deal with conflicts such as this? What if another 3rd party plug-in also wants to customize the same vCAC workflow stubs? It seems like a messy approach for plug-in providers to take. I am under the impression that using the vCAC plug-in in vCO to install vCAC workflow stub customizations is now the preferred means of extending vCAC with vCO workflows. It lets you focus your workflow customization efforts in vCO rather than using the clunkier (IMO) vCAC Design Center. What thoughts does VMware and the community have on this? Thanks.