The XaaS blueprints (used to be called ASD blueprints) can be used to support many use-cases. Mostly they are used they are used to provision something or to change object states. In many cases they are not used to return any value when completed. They just indicate that the vRO workflows are in progress, failed or completed.
Well, in this blog post I will show how it is possible to return simple data but that can create a cool effect.
Actually there is no problem, I just wanted to show you something that I think is rather cool and can give your XaaS requests a little bit more finesse.
In the next section I will create a XaaS blueprint (easiest blueprint ever) to help my vRealize Automation users at Nubera find the hyperlink to my blog in case they would forget the URL. Rather silly use-case but it is just a proof-of-concept idea.
First we will need to create our vRO workflow. Open your client, create a new workflow, give it a name, drag an empty scriptable task onto the canvas and create three (string) output parameters (no attributes!). That is all we need to have for the vRO part.
In the scriptable task I entered three lines. One line for each output variable and the only thing needed to do is give it string values:
The workflow is now finished. Up to the vRA portal!
Go to the design tab and create a new XaaS blueprint using the newly created workflow and give it a matching name.
Next go to the blueprint form tab and press the upper green plus icon next to the drop down box that has the “Request form” value by default. In the pop-up window select “Submitted request details”. After pressing submit you will get another XaaS canvas. This canvas will be used to show our output.
When scrolling down in the left section of the canvas, you will see that there is a new section called “Outputs”. The values here can be dragged onto the canvas.
At the top I put my text variable, followed by my solutionyst URL and last is my solutionyst logo.
When editing the url parameter (called output in my example), you can give it the link type. This is shown in the image below. The outputLogo parameter has the type “Image URL field”.
Save and close, publish the blueprint, give it the proper entitlements and request it.
When the request is completed, click it and you can see that the URL is clickable (internet access is required of course…) and that the logo is loaded into the form.
It is very easy to make your request forms prettier and also give output when the request has finished.