1. vRealize Automation 7.0
2. vRealize Orchestrator 7.0 that comes with vRA
Blueprint and custom workflow configuration
1. Created a blueprint that provisions a Windows Server VM
2. Created a custom workflow to update the properties of the provisioned VM
When I try to run the "Assign a state change workflow to a blueprint and its virtual machine", I was not able to select the blueprint that I have created in vRA.
Anyone has the same problem and how can we resolve this?
It is recommended to only use the Event Broker for tasks like this moving forward. Those workflows and ties into the old way are going to be deprecated and as such will break much of the work you do in this manner.
I defiantly agree that it is better to use the new method of doing stuff in vRO and vRA.
But, like anything new – this is not very good documented and there is not many examples and blog post out there.
I had the exact same problem 2 weeks ago (post here) and it was very hard to overcome the steep learning curve of vRO when all the examples and guides are for the old "assign a state change…" method.
So, try to use the new extensibility and subscription method of doing stuff but for quick-wins you can still use the "state change workflows" just know that this will soon be deprecated.
Also be sure to follow the links that Mads Fog Albrechtslund post in my original thread.
As suggested by previous entries the EB is the method of choice going forward.
That being said the Assign state change workflows and WFStubs function perfectly in vRA 7.0.
When selecting a blueprint ensure you select one from the Administration > Composite Blueprints folder. If you have issues seeing the blueprints in this folder then double check that the user you used when registering a vRA hosts in the plugin configuration has tenant admin rights.