Hi kumarsenthild,
Not sure if you worked this out or found your answer somewhere else...
I am assuming you want to get the USERID of who requested the XAAS catalog item.. If this is correct then this is how I have done it..
On your Orchestrator workflow you need to add an Input parameter to capture this. (same for any other inputs you want - in my case an email, crq number and an 'are you sure' checker)
I have an Attribute I have called 'requester', In the Schema I have a "scriptable task" dealing with all the Inputs, but the part of interest to you is this simple line: var requester = requestedby just make sure you set the "IN" local parameter to 'requestedby' and then in the "OUT" tab a local parameter for the attribute 'requester'.
Next have your workflow do what its doing...
On the End of my workflow I have used the built in worflow called "Send Notification" this sends an email.
I have added the Attribute 'requester' as an "IN" parameter to the Send Notification workflow, In the scriptable task of the workflow you can write the content of the email... SO along with other things my content has a line saying{ " This was requested by: "+requester }
Now for the xaas blueprint...
When you pick your workflow when creating a new xaas blueprint, you should have a "requestedby" field, select this and update it like this:
Remember to click Apply
Now your field should look like this:
But we dont want that showing up when users are working with the catalog item... so go back in and make it constantly not visible:
Remember to click Apply
Now when you choose your catalog item you wont see this field but it will be auto populating.
So long as all configured correctly your vRO workflow will run and send the email including the requester,
something like this:: (sorry about the blue.. but have too..)
Hope this helps you, or someone else in the future.
Cheers
Jono.