Content capture fails for custom forms which have been created or modified in Aria Automation version 8.12 and above

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Content capture fails for content type Automation-CustomForm for custom forms which have been created or modified on Aria Automation version 8.12 and above.
• Custom forms created on prior VMware Aria Automation (formerly vRealize Automation) releases that have not yet been edited on version 8.12 can still be captured.
• The /var/log/vrlcm/vmware_vrlcm.log log file contains error message similar to:

  [ ContentAsync-4] c.v.b.u.CommonUtil[httpGetWithRetry] : error while making a get call :: status : 404 NOT_FOUND, Error : {"timestamp":"YYYY-MM-DDTHH:MM:SS.000+0000","path":"/form-service/api/forms/fetchBySourceAndType","status":404,"error":"Not Found","message":"404 NOT_FOUND \"77002-No form definition found for source type 'com.vmw.blueprint' with id '<BlueprintID>'.\"","requestId":"<requestId>","@type":"org.springframework.web.server.ResponseStatusException"}

Environment

VMware Aria Suite Lifecycle 8.12.x
VMware Aria Automation 8.12.x
VMware vRealize Suite Lifecycle Manager 8.10.x

Cause

The issue is caused by API changes introduced in Aria Automation 8.12 forms service to support versioning. These changes are not yet supported in VMware Aria Suite Lifecycle (formerly vRealize Suite Lifecyle Manager) and prevent content capture from succeeding for Automation-CustomForm content types.

Resolution

This issue is resolved in VMware Aria Suite Lifecycle 8.14.

Workaround:
There is currently no workaround available.