vRA 7.3 and custom properties from Orchestrator Actions

[michael_stefani]

So I'm in the process of redoing most of what I did in vRA 6.2 in 7.3.  Right now I'm trying to determine if I can use the new blueprint designer or if I still have to use XAAS blueprints.  In 6.2 one of our bigger use cases was having dropdowns that were dynamically populated via an Orchestrator Action based on the user's business group.  I see that now in 7 you can create custom properties that execute an Orchestrator Action (which is cool).  But as best I can tell you either have to type in the input values statically or define them as an additional custom property that a user can select.  In our case I don't want the user to be able to pick it .... I want to pull his business group and give him a list of options.  Are there hidden properties that can be used there to reference the requestor, busgroup, etc like there are in XAAS or no?

[bdamian · Accepted solution]

Just to be sure:

You want to use a custom property in your request form that calls to an action in vRealize Orchestrator and you need to pass the Business Group Name to filter data. Is this right?

Saddly, this is not possible (yet/bug/missing feature) but I have a similar problem that I could solve with a "work-around" proposed by poorem.

Re: getApplicableNetworks retrieves more than Business Group networks

[michael_stefani]

Thanks, that's what I was figuring.  It's a shame all the same custom properties you can use in XAAS are not available to use in the regular designer.  I think I can work around it with the suggestion you mentioned though, so thanks!

Mike