Customize custom forms and Deployment name options missing in VCF Automation 9.x Custom Forms

Products

• VCF Automation

Issue/Introduction

• In previous versions of Aria Automation (8.18.x and earlier), administrators could use external actions in Custom Forms to automatically set a deployment name while hiding the input field from the end user.
• Post upgrading to VCF Automation 9.x, the options to replicate this behavior in Hard Tenancy environments are missing or unavailable.
• The ability to apply actions to the deployment name field while maintaining field invisibility is not present for Catalog Items.

Environment

VCF Automation 9.x

Cause

This is a behavioral change in the VCF Automation 9.x release. The legacy method for automating and hiding the deployment name field in Hard Tenancy is not currently implemented in the 9.x platform.

Resolution

This is currently a known product limitation in VCF Automation 9.x. 

Engineering and Product Management have confirmed this behavior is expected for the current release. A request to restore this functionality has been shared with the Product Management team for consideration in the future product roadmap.

Workaround:

There is currently no direct workaround to automate the deployment name while keeping the field invisible in a Hard Tenancy environment. 

In Soft Tenancy environments, limited customization is available within the Blueprint section; however, note that this does not currently support full versioning in the same manner as previous Aria Automation releases.