Unable to select Organizational Unit (OU) via Tree Picker in Service Broker Custom Forms after upgrading to Aria Automation 8.18.1 Update 5

Products

• VCF Automation

Issue/Introduction

The OU tree picker in Aria Automation Service Broker fails to load child items after an upgrade to 8.18.1 Update 5. This issue blocks users from submitting custom forms that rely on OU selection.

Symptoms

• After upgrading VMware Aria Automation to version 8.18.1 Update 5, users are unable to expand the Organizational Unit (OU) Tree Picker within Service Broker custom forms.
• Because the tree picker fails to load the OU data, users are blocked from submitting the affected catalog requests.
• The tree picker continues to function as expected when the workflow is executed directly via VMware Aria Automation Orchestrator.
• When this issue occurs, you may observe warnings similar to the following in the /var/log//services-logs/prelude/tango-vro-gateway-app/file-logs/tango-vro-gateway-app.log:
  
  

  {"name":"ouContainer","type":"AD:OrganizationalUnit","description":"Organizational unit in which to put the newly created user"}
  YYYY-MM-DDTHH:MM:SS.562Z WARN tango-vro-gateway [host='tango-vro-gateway-app-' thread='jdbc-35' user='' org='' trace='' parent='' span=''] c.v.o11n.client.model.WsParameterSdk.getType:64 - Parameter ouContainer has no type.
  Cause

Environment

Aria Automation 8.18.1 Update 5

Cause

This issue occurs due to a recent Spring framework upgrade in Aria Automation 8.18.1 Update 5. Certain symbols are no longer allowed or encoded properly during inventory search. As a result, the system fails to load and render the requested Active Directory inventory data within the Service Broker UI.

Resolution

This issue is targeted to be fixed in Aria Automation 8.18.1 Patch 6 which should be available by beginning of Q4 2026. Subscribe to this article to receive updates on fix status (reference).

Workaround: To unblock users until Patch 6 is applied, you can implement the following workaround by utilizing a vRO action to load the Active Directory objects dynamically:

 

Step 1: Create a vRO Action

1. 1. Log in to Aria Automation Orchestrator.
   2. Create a new action with the following script:
   3. JavaScript
      

      if (host == null ) { return [];} 
      
      return ActiveDirectory.search( 'User' , '', host);

 

1. 1. Configure the Input: Create an input named host of type AD:AdHost.
   2. Configure the Output: Set the return type to Array/AD:User (or AD:User).

Step 2: Update the Custom Form in Service Broker

1. 1. Navigate to the affected Custom Form in Aria Automation Service Broker.
   2. Add a Host field of type Tree Picker and set its reference type to AD:AdHost.
   3. Add a Users field (or equivalent child field) of type Value Picker and set its reference type to AD:User.
   4. Configure the Users field's value list to use the vRO action created in Step 1.
   5. Pass the newly created Host field as the input parameter to this vRO action.

With this workaround the tree picker for the host and then load the children using vRO action and then you will be able to use multiple AD integrations. 

Note: Broadcom Global Support does not provide assistance with workflow customization. Please reach out directly to the individual or team who authored the workflow.

Support Assistance: See Contact Support. Scroll to the bottom of the page and click on your respective region.

Additional Information

Download Broadcom Products and Software