When using custom forms, Request Info content fields are null when handed over to a vRealize Orchestrator action in validation mode

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Custom forms are being used with a vRealize Orchestrator action as "External Validation" with any field of Request Info as an input parameter
• The following similar entries can be found in the server.log:

2019-07-08 12:47:19.098+0000 [http-nio-127.0.0.1-8280-exec-7] INFO  {} [SCRIPTING_LOG] [script: FQDN.vra.customforms.vra.placement/getReservationPolicyId] (FQDN.vra.customforms.vra.placement/getReservationPolicyId) ProviderBinding = null
2019-07-08 12:47:19.099+0000 [http-nio-127.0.0.1-8280-exec-7] INFO  {} [SCRIPTING_LOG] [script: FQDN.vra.customforms.vra.placement/getReservationPolicyId] (FQDN.vra.customforms.vra.placement/getReservationPolicyId) tenant = null
2019-07-08 12:47:19.102+0000 [http-nio-127.0.0.1-8280-exec-7] INFO  {} [SCRIPTING_LOG] [script: FQDN.vra.customforms.vra.placement/getReservationPolicyId] (FQDN.vra.customforms.vra.placement/getReservationPolicyId) datacenter = AUTO
2019-07-08 12:47:19.102+0000 [http-nio-127.0.0.1-8280-exec-7] INFO  {} [SCRIPTING_LOG] [script: FQDN.vra.customforms.vra.placement/getReservationPolicyId] (FQDN.vra.customforms.vra.placement/getReservationPolicyId) subtenantName = null

Environment

VMware vRealize Automation 7.6.x

Cause

vRealize Orchestrator 7.6 actions do not properly inherit values from “Request Info” fields but do from “Canvas” fields when working in validation mode.  Property values are not added to the validation context prior to executing External Validations.

Resolution

This issue is resolved in vRealize Automation 7.6 Cumulative Update HF2.

Workaround:

1. Create new Canvas fields and bind them to the "Request Info" fields.
2. Change the binding for the action from the “Request Info” fields to the newly created "Canvas" fields.