Utilizing service library run-time variables in vRO workflow

[Lucas-Eriksson]

Hi there!

I have created a service library item in the vCloud Director, defined by a workflow in vRealize Orchestrator. Currently the workflow only prints a simple "Hello world" but I am planning on extending the service library item for my specific use case. There are some values passed from the cloud director to the workflow, such as the username and the organization ID. I would like to utilize these variables in my workflow to not have to look them up myself. I am unsure if this is possible and was hoping that someone in the forum could shine some light on this.

In my workflow I have defined an output as mentioned, which just prints. When inspecting the workflow run the information from cloud director shows up under the "Variables" tab for example as "_vdc_userName". I tried using a variable with the same name in my workflow definition but got a reference error, and the workflow failed.

Do you know if there is a way to use these run-time variables in my workflow definition or do I simply have to retrieve the information on my own?

[VenelinBakalov]

Hi @Lucas-Eriksson , I am not sure if you already managed to find an answer but if another system is sending some form of data to vRO it should be available in the System context.
Here is a sample on how you should be able to get the information based on the variable name you provided:

		const context = System.getContext();
		const username = context.getParameter("_vdc_userName");

I haven't tried this personally for vCD but I've had similar cases with vRA when a Custom Catalog Item or a Day-2 operation is calling a workflow . Here is a sample on how I would get a vRA Machine ID in case I am calling a Day-2 operation on a Machine:

		const context = System.getContext();
		const props = context.getParameter("__metadata_resourceProperties");
		const machineId = props?.resourceId;

[Lucas-Eriksson]

Thank you for getting back to me! I managed to find an ancient blog post which had a print screen of pretty much exactly what you are saying.

So yeah, solution was to retrieve the system context and I ended up writing something like

const _vcd_userName = System.getContext().getParameter('_vcd_userName');