Troubleshooting Automation Service Broker custom forms

If you encounter problems when using custom forms in Automation Service Broker, you can refer to this troubleshooting topic to understand the problem or solve it, if there is a workaround.

These issues affect VMware Aria Automation version 8.16.0.

External actions are not executed correctly

Problem: External actions in your custom forms are not executed correctly, for example, a field might not autopopulate with the default value or a dropdown menu might appear without options.

Cause: External actions used in a custom form field are only executed when all dependency fields with constraints are properly populated with valid values. When a field breaks some of its constraints, such as required, min/max value, or length, and pattern constraints, any directly dependent input field with an external action is evaluated only after the field is within the valid requirements. Transitively dependent fields with an external action are not evaluated unless the field is valid. If a valid field is updated and becomes invalid, then all dependent actions are not run.

Solution: Ensure that all dependency fields with constraints are populated with valid values. For example, ensure that all required dependencies are filled and all constraints on the dependencies are satisfied.

Form requests fail

Problem: You get form errors, for example, Some data cannot be retrieved. If the problem persists, contact your system administrator. Failed request: <action name>.

Cause: Your form might include one or more fields that contain a regex constraint that doesn't comply with Java and JavaScript.

Solution: Ensure that the regex in your fields is both Java and JavaScript compliant.

Unable to import Automation Orchestrator workflows

Problem: When you import an Automation Orchestrator workflow into the Automation Service Broker catalog content sources, you get an error message, for example, Error downloading catalog item ‘/workflow/<workflowId>’ (Error: Content provider error).

Solution: Verify that the workflow does not contain any inputs or fields with the id project, which is a system property.