Custom Forms in Aria Orchestrator Retain Previous Selections

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When using dynamic actions to populate value lists in Aria Orchestrator  forms, if the result set contains only a single value, previous populated data will be listed.

• Cached data from previous selections may persist.

• New selections may not immediately reflect unless the form is refreshed or manually adjusted.

Refer to below example, Once a project is selected, a virtual machine object should appear under the "Select Virtual Machines" tab. However, if you try to change different projects, you should still see the older virtual object and it does not change to a different value.

Environment

VMware Aria Automation 8.18.x

Cause

The is a expected behavior as per design when we have a field with value list populated by Aria Orchestrator action and used as input to another action, the action execution is not set to wait for another action execution to complete.

As result the value is executed with the old data, because it is not set to wait for the new one.

Resolution

Workaround:

Update Aria Orchestrator actions which populate a single-value list which is used by dual list and multi-select to return an additional empty value.

1. Add a default value of type Aria Orchestrator action, that returns null or empty array.
2. This action should have the same form field params as in the value list.
   Example:
   value list __ action has 3 params -> {param1: form field, param2: constant value, param3: form field}, then the default value should have: {param1: form field, param2: form field}