We have a need to work on adding functionality to our existing vCO 5.5 workflows that integrate with vCAC 6.0 machine states. This is accomplished, in addition to adding the vCO Endpoints in vCAC, by adding the following custom properties with a appropriate values to all Blueprints:
ExternalWFStubs.BuildingMachine ExternalWFStubs.MachineDisposing ExternalWFStubs.MachineProvisioned
We have a need to do some workflow development. The problem is that we have only the one production vCAC + vCO infrastructure, no dev-test environment and no time to build one (don't ask). What I would like to know is: if we were to add some non-production instances of vCO for dev/test/QA would this work? The problem I see is either:
1) If we take a backup of the entire set of workflows & related vCO bits (*.package) and restore them to these non-production vCO instances the workflow IDs will be the same as production, but then how do we ensure that production requests go to the production vCO instances and the non-production requests go to the non-production vCO instances.
2) Take a backup of the entire set of workflows & related vCO bits and restore them to to these non-production vCO instances. Is it then possible to change the workflow IDs? (No, I haven't tried.) This way we can simply create a new set of custom properties + build profiles + blueprints for dev/test/QA. If it is possible to change the workflow ID, then I'm assuming that this can be done when we promote from non-production into production to match the existing workflow IDs.
Thanks in advance