The following issues are known in the VMware vRealize Automation for ServiceNow ITSM application:

  • Junk sys_id: In the VMware vRealize Automation for ServiceNow ITSM application, when a catalog item or project is deleted, if the deleted catalog item or project is part of a defined entitlement, then these deleted records are seen as junk values in the entitlement record.

  • The VMware vRealize Automation for ServiceNow ITSM application displays Boolean type fields as checkboxes in catalog items.

  • If there are multiple catalog items with the same name, then the VMware vRealize Automation for ServiceNow ITSM application 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.

  • When a shared resource is stopped being shared, the UI of the unshared resource becomes distorted. Reload the page to resolve this issue.

  • In VMware vRealize Automation, if a Cloud Template is having a property group or property definition defined in the input, then the same Cloud Template will fail in ServiceNow.

  • For the Service Portal and Native UI, the RITM displays extra fields that are not part of the request form.

  • The vRealize Automation Configure Items for the catalog items does not support the vRealize Automation for ServiceNow ITSM application.

  • If you have created the following fields in vRealize Automation then while performing import in ServiceNow, the following fields are not created:

    • deploymentName

    • description

    • project

  • For the User Portal, if any catalog item has a dot in its versions then the catalog item will not fetch the dependent drop-down values.

  • In the ServiceNow Quebec release, the catalog item requests having a password field are getting failed. This issue occurs as in the custom scoped application, the ITSM application is unable to use getDecryptedValue() for masked variable in catalog item. This is a ServiceNow known issue for Quebec release.

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

  • While fetching the Date Time field from the external sources, an extra T displays for the time in the ServiceNow Native UI.

  • If in the custom form, you have customized the deployment name field using the source data as default value/Read only/External then multiple deployment fields displays on the User Portal.

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