The following issues are known in the VMware Aria Automation Plug-in:

  • The VMware Aria Automation Plug-in displays Boolean type fields as checkboxes in catalog items.

  • If there are multiple catalog items with the same name, then the VMware Aria Automation Plug-in displays the latest created catalog item and earlier created catalog items are removed.

  • While deleting an endpoint make sure that data is in the VMware application scope. If not, an error message displays for the cross scope data deletion post endpoint is deleted and data is removed successfully.

  • The VMware Aria Automation configures Items for the catalog items that do not support VMware Aria Automation Plug-in.

  • The resource name is not visible in the Service Portal for the AWS CFT, ABX actions, deployed Terraform catalog item, and failed vRO Workflow deployments.

  • In the Native UI, if a day-2 action catalog item contains the check box or label fields then ServiceNow displays the cross-scope info messages while loading day-2 catalog items and also on RITM after submitting the day-2 catalog items. This is a ServiceNow-known issue.

  • On the Service Portal, duplicate data type fields are displayed in the RITM if the catalog item has multiple versions.

  • On the Service Portal, for the visibility feature, the Dropdown field list on the catalog item will have an extra empty option.

  • When day-2 actions for multiple deployments are processed simultaneously,  the duplicate variables may be generated in respective day-2 catalog items. This is a ServiceNow-known issue and occurs rarely.

  • In ServiceNow, if you hide all fields under a tab, then the tab will also not be visible even if the visibility condition is matched.

  • The catalog form request with empty fields within property groups will fail after submission because the property groups are mandatory in VMware Aria Automation.

  • In the Data grid, if the input field with type number/integer is empty on the order form, then the catalog request fails after submitting in ServiceNow.

  • In ServiceNow, when you modify the value of any dependent field containing conditional default value and conditional read-only, then the dependent field will reflect the default value instead of the modified value.

  • In ServiceNow, when you perform the price estimate calculations without filling in any mandatory fields in the form, the price estimate can give an error message that can be viewed in the error logs.

  • The “Update” button for price estimate calculations is always active even if any of the field’s inputs are not modified.