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 check boxes 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 .

  • For custom forms, field properties such as, Match field is not supported in the Constraints.

  • For custom forms, field properties such as, Hide or Unhide field based on another field value is not supported.

  • Minimum and maximum validation is not supported for multi-select and dual list data types in the ServiceNow.

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

  • Catalog items designed using YAML is not supported in the VMware vRealize Automation for ServiceNow ITSM application.

  • Depending upon the number of fields in the catalog form, it may take more time to load the catalog form with available values as loader functionality is not available in the Native UI.

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