SolutionVMware have released patches for all supported versions of Aria Automation to resolve this issue
Aria Automation Version | Patch |
8.11.2 | vrlcm-vra-8.11.2-8.11.2.30135.patch |
8.12.2 | vrlcm-vra-8.12.2-8.12.2.31375.patch |
8.13.1 | vrlcm-vra-8.13.1-8.13.1.32392.patch |
8.14.1 | vrlcm-vra-8.14.1-8.14.1.33507.patch |
8.16 | vrlcm-vra-8.16.0-8.16.0.33716.patch |
Please see
KB 96098 for full details on how to install these patches
Workaround (Only to be used if patching the environment is not feasible)There is no need to explicitly pass the project as action input. When a VMware Aria Automation Orchestrator action execution is started, the project id is implicitly passed in as a context parameter. Instead of having an input for the project in the action, use the context parameter called
_projectId.
Example:
Project Field
The action receives one input called
project.
- Remove that input.
- In the action script, create a variable called project and assign it with the context parameter value:
var project = System.getContext().getParameter("_projectId");
- Save the action.
- In the catalog item custom form designer, re-select the updated action.
- Save the modified custom form.
Request Info Field (e.g. Catalog Item Name)
-
Custom form binds a request field to an action that has Request Info field as an input.
- Switch the field to a constant with the actual value (e.g. Catalog Item name).
Content Source Imports and Updates
- Implement the provided workaround prior to importing the content.
Regex Constraint
- If you encounter form errors and your form includes one or more fields with a regex constraint, ensure that the regex adheres to both JAVA and JavaScript compliance. When this adjustment is made, the issue will be resolved. Example error message: “Some data cannot be retrieved. If the problem persists, contact your system administrator. Failed request: <action name>”