Like I mentioned, we ship about 300 actions and workflows in the product by default. Personally, when I need examples, this is where I look. There are plenty of workflows that serve as good exa...
See more...
Like I mentioned, we ship about 300 actions and workflows in the product by default. Personally, when I need examples, this is where I look. There are plenty of workflows that serve as good examples. We are aiming at both admins and workflow creators. - For the admins, there are existing workflows in the library that I am sure they find useful right away. More over, we are shipping additional workflows with every update release. For example, in U1, we will likely be releasing workflows that help you find orphaned VMDKs in all your datastores that VC is unaware of. These are workflows that an admin can run out of the box that is very useful right away. - For the workflow creators, vCO has been used to create incrediblly automated data centers that automate everything from storage and network provisioning to pupolating CMDB and reporting on virtual infrastructure. if your goal is to create complex workflows, I would agree that this is a tool where you need to spend some time, make some investment before you can start seeing returns. But the typical VI admin should have no trouble running workflows out of the box. However, creating a workflow, for example, creates a VM and email you the parameters, should be something that is not too difficult to accomplish since both workflows are included in the library and you would only need to create and link a bunch of variables together. Descriptions of each workflow is actually a part of the workflow. If you are interested, I would definitely encourage you to open up the vCO client and look at a workflow or two. Seperately, we are working on a catalogue of workflows that are outside the client so people can look through them without the client. Sia