Issue assigning an approval policy to a blue print with a custom form and properties
search cancel

Issue assigning an approval policy to a blue print with a custom form and properties


Article ID: 326572


Updated On:


VMware Aria Suite


  • 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.


To resolve this issue:
  1. Apply 7.5 HF20 or 7.6 HF12.
  2. Re-register catalog types on IaaS machine 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.
  1. Create a vRO action "calculateStorageGB" for calculating the Storage GB value.
VMware recommends using the machine 'disks' field. You can add other inputs and bind them in the form depending on your use-case) - diskEntries (Array/Properties).
Return Type: number

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;
  1. 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.
  2. Edit the Custom Form and drag the Storage GB on the canvas and configure it.
  3. Go to Default Value and set to External Source and select the "calculateStorageGB" action.
  4. For "diskEntries" input parameter bind the disks field (or other parameters which you have included).
  5. Set ReadOnly to Yes, so the user wont be able to edit the Storage GB.
  6. Request Custom Form
  • If Approval Policy is applied make sure to have more Storage than the limit in Approval Policy
  •  Make sure the Storage GB is submitted and showing correctly in the Deployment Request History