Unable to assign an approval policy to a blue print with custom form and properties

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Approval Policy for vSphere Virtual Machine is not triggered on 'Submit' when using Custom Forms.
• Approval Policy is conditional where for example machine's "Storage (GB)" > 20GB.
• Storage (GB) value is not getting submitted on request using Custom Forms.
• Storage (GB) has read-only constraint in Composite Blueprint schema.
• The value cannot be configured in Custom Forms and is not propagated on Submit. 

Resolution

To resolve this issue after 7.5 HF20 or 7.6 HF12 is applied:

1. Re-register catalog types on IaaS machine by running this in command prompt and wait for completion:

"C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterCatalogTypes -v
This rewrites the vSphere Machine schema in vRA.

2. Create a vRO action "calculateStorageGB" for calculating the Storage GB value.

Inputs (In this example, the machine 'disks' field has been used, you can add other inputs and bind them in the form depending on your use-case):

 - diskEntries (Array/Properties)

Return Type: number

SCRIPT:

var acc = 0;

if (diskEntries && diskEntries.length > 0) {
for(var i=0; i < diskEntries.length; i++) {
acc = acc + parseInt(diskEntries[i].get('capacity'));
}
}

return acc;

3. Remove and re-drag the VM in the Blueprint Editor. This will remove the Storage GB read-only constraint from schema in the vRA Database.
4. Edit the Custom Form and drag the Storage GB on the canvas and configure it.
5. Go to Default Value and set to External Source and select the "calculateStorageGB" action.
6. For "diskEntries", the input parameter bind the disk field (or other parameters which you have included).
7. Set ReadOnly to Yes, so the user will not be able to edit the Storage GB.
8. Request the Custom Form:
   •  If Approval Policy is applied, ensure to have more Storage than the limit in Approval Policy.
   • Ensure the Storage GB is submitted and showing correctly in the Deployment Request History.