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, Show or Hide 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.
For the Service Portal and Native UI, the placeholder functionality is not supported.
For the Service Portal and Native UI, the RITM displays extra fields that are not part of the request form.
In the vRealize Automation for ServieNow ITSM application, the dependent fields having minimum and maximum values with the VMware vRealize Automation action is not supported.
For Native UI, password data type does not support the Minimum and Maximum values.
The vRealize Automation Configure Items over the catalog items does not supported in the vRealize Automation for ServieNow ITSM application.
If you have created following fields in the vRealize Automation then while performing the import in the ServiceNow these fields will not be created:
For the User Portal, if any catalog item has a dot in their 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 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 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 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.