A vCO Starter asked how to prefill DropDow-Boxes (or other fields) as input in dependency of an other input. Here a simple guide to use an action in Presentation to do this.
Assuming there is a workflow with two input parameters, Input1 [string] for free input, Input2 [string] in dependency of Input1 wich should offer following values:
Define both strings as input parameter. Then go to the presentation tab.
The Mandatory Property forces an input for Parameter Input1. You can not proceed the Workflow without a value for Input1.
Before looking at Input2, create an action:
This action will return an array of string in dependency of the input parameter MySelection described at the beginning.
Now use this action to define the second parameter:
Add a "Predefined list of elements" property.
Use action sign (the puzzle) to bind the action on this property. Click the "string" to select the propriate input parameter or our action. After this the presentation look like this.
Execute the workflow and test the behavior.
Here a little action to mount a NFS export to a Host (assuming all export settings are checked for ESX).
Input parameter
Output parameter
To set DRS automation level is easy with vCO. But how to set the DRS mode (manual, partially automated and fully automated)?
The above example has Cluster [VcClusterComputeResource] and DRSmode [string] as input parameter. Output is Task as VcTask, so you can continue with action vim3WaitTaskEnd.
DRSmode has 3 possible values:
Sometimes you need a function to calculate a result and you don't want to use an action. Here we have an (sense free) example which shows us how a function is build up and used. Also the scope of used variables is demonstrated:
This example will log (in extra lines): 3, 4, 0, 7, 3, 4, 99
This show us the scope of defined variables. The variables a and b are defined in outer and inner (function) scope. The changed values (set to 99) will only affect the inner a and b. Otherwise c - there is no c defined inside the function or passed to it. So the outer c will be used.
After calling Add(a,b) the value of c is set to 99.
Regardless of the scope a function can return a value using the keyword return. There is no type definition. The function will return an object.
Warning - it is not recommended to manipulate outer variables from inside a function. It works, but making your code difficult to debug if any error or misbehavior occurs.
The example above will log this:
The function "desc" returns a boolean to decide to sort or not. It works as comparator for the sorting algorithm inside sort(). I don't know this algorithm, but this is not necessary. Just use ist as sorting comparator. So if returned true the pairs will change place in array - like quicksort or so.
The (partial) log shows this:
And the log shows this:
Be careful with your self created sort function. Use it only on homogen arrays. Because all elements must support the properties you use in your function. On heterogen arrays adapt your function to match all possible elements.
