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

  • Junk sys_id: In VMware vRealize Automation ITSM Application for ServiceNow, 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.

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

  • If there are multiple catalog items with the same name, then VMware vRealize Automation ITSM Application for ServiceNow 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 stop being shared, the UI of unshared resource becomes distorted. Reload the page to resolve this.

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

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

  • In VMware vRealize Automation ITSM Application for ServiceNow, the RITM displays extra fields that are not part of the request form.

  • The vRealize Automation Configure Items for the catalog items does not supported VMware vRealize Automation ITSM Application for ServiceNow.

  • If you have created following fields in the vRealize Automation then while performing the import in the ServiceNow these fields will not be created:

    • deploymentName

    • description

    • project

  • For the User Portal, if any catalog item has a dot in its version 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 is 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 checkbox 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 displayed in the RITM if the catalog item has multiple versions.