Branching off from another thread to work on the final solution: This was my original post from this message string http://communities.vmware.com/message/1637244#1637244
I went ahead and tried creating a custom decision. I used the following code in the script portion of the decision:
if (vm.state = "poweredOn") {
return true;
} else {
return false;
}
but I get an error when I run the workflow stating that there is no property called "state". vm is of type vc:virtualmachine . Do I have the syntax wrong somewhere? Do I need to somehow set an attribute or output to the value of vm.state in the main input and output parameters? Help a newbie out here to get this sample working.
Paul
Andreas answered with this:
Hi Paul,
1) this is a solved thread - next time pls open an own thread
2) powerState is part of runtimeInfo and not of VM so your code should look like this:
return (VM.runtime.powerState == "poweredOn");
The term in brackets is bool, so you can return it direct.
In Java you use "=" to assign values! With "==" you check for equal or "!=" on not equal.
So the code above returns true on a powered on VM and false for powered off and suspended.
Think that solved your question.
This didn't quite solve my question. That code returns a powerState object.
return (vm.runtime.powerState.name == "poweredOn");
Does the trick though.
So my question is why does the documentation list "state" as a property of vc:virtualmachine? Is that a documentation error or related to the bug referenced in the release notes?
Also where is the best place to see a listing of all the properties and methods for the different object types? Sorry but I am a total novice when it comes to the dev side of things. Is this found in the api documentation set?
Paul
