In the first post, I showed you the basics syntax to work with XML and JSON within vRO.
We learn how to create, update and delete values in XML and JSON object, but in real life we some more complex objects such as arrays or we need to convert string to XML or JSON. In this post, I’ll show you some more advanced tricks.
First, let’s see how to work with arrays within XML and JSON objects.
When integrating vRealize Orchestrator with external systems using REST API, knowing how to work with XML and JSON is a must!
During my work on the NSX Firewall as a Service Package and on the F5 LTM Dynamic Types plugin, I noticed that we have a lot of “gotchas” that are not very well documented.
My code samples for both XML and JSON will be based on a custom object that we will call it “Pool”. This “Pool” object as attributes such as name, version, and members of this pool. Continue reading
When you export a plugin configuration using Dynamic Types Plugin Generator, you basically create an open-source package that everyone can reuse or even update.
In the next couple of posts, I’ll show you how to extend the plugin in order to answer you environment needs.
Since vRA 6.x released, XaaS use cases are very common (here some cool demo for create MS Active Directory user as a service).
But presenting workflows to end users required some rethinking and redesign the user form so it will be user friendly with minimum ״free text” that can cause an error during the workflow runtime.