Have you ever wanted to simplify the catalog request form? Maybe your users don’t qualify to know how many CPUs or Memory are needed? Perhaps all you need is to have a custom request form using XaaS!
Well today I’m here to help with a simple workflow that you can customize to make your own request form. As always feel free to check out the video below, and download the package from here.
So what if you could go from this?
Assuming you’ve downloaded and imported the package above here’s what’s included. It’s a simple workflow that makes a decision based on the users OS selection
It uses the print request to pull the JSON from that particular blueprint.
Now the best part about XaaS services is that you can test them without having to go to the web interface. Use the inputs to test and troubleshoot your workflow then those will get surfaced up to vRA when you create the XaaS blueprint.
In this image I’m illustrating the windows and linux blueprints that are defined in the included configuration element.
Run the configure templates workflows to select your linux and windows base blueprints
After selecting those it will update the configuration element and is ready for use
Now you can go into vRA -> Design -> XaaS Blueprint and create a new blueprint
Select the workflow
Provide a name, description, and version
Now you can customize the form as you see fit. Remember though that the current workflow makes decisions and edits the request based on the scriptable tasks.
So for our OS we set it to a drop down menu
Give it the predefined values of Linux and Windows
Set it to be required
Then move on to Size, again set it as a drop down
Take a look at the scriptable task for size to see that we have defined small, medium, large, and xlarge. You can edit these in the scriptable task for your needs!
Set those as predetermined values in the form
Set it as a required field and move to Environment
In my example I used environment by calling out a reservation policy which I have defined Test, Dev, QA, and Prod. In your environment this may not make sense or you may want to change those settings in the scriptable task in vRO but it’s a good example.
Set it to required
Set the predetermined values (case sensitive)
Now we fill in the requested for, this is where I populate it with a field value of who’s requesting it using their email. I then make it invisible to the consumer.
Next we add a few cool sliders with Lease and number of machines
Define min, max, increments
Now publish it and assign it to a catalog service and you’re off to the races with a customized form for your consumers. As always I hope it helps and I can’t wait to hear any feedback!