vRealize Orchestrator Appliance 8.1.0 Patch 3 | 26.10.2020 | 16984307

Check frequently for additions and updates to these release notes.

VMware vRealize Orchestrator 8.1.0 Patch 3 is a minor product patch release that includes specific resolved issues and common improvements made across the vRealize Orchestrator platform. The content of the VMware vRealize Orchestrator 8.1 Release Notes apply to this version as well.

What's in the Release Notes

The release notes cover the following topics:


Upgrade failure after performing steps in KB 87120

Performing the instructions used to address the CVE-2021-44228 and CVE-2021-45046 log4j vulnerabilities described in KB 87120 can cause upgrade failures for vRealize Automation and vRealize Orchestrator 8.6.2 or earlier. For a workaround, see KB 87794.

How to upgrade to Patch 3

You can upgrade your vRealize Orchestrator Appliance to the Patch 3 build by following the official upgrade procedure. See Upgrade a Standalone vRealize Orchestrator 8.0.1 Deployment.

Resolved Issues

  • After migrating to vRealize Orchestrator 8.1, an local changes error appears.

    After migrating to vRealize Orchestrator 8.1, the following error message might appear: 'You updated these paths: Workflow/{workflow_id}/workflow.xml while being deleted/renamed in the remote repository. Undo your local changes regarding them and pull.'.

  • vRealize Orchestrator Administrators cannot create content by using the new scripting languages.

    vRealize Orchestrator Administrators without Workflow Designer permissions cannot create content by using Python, Node.js, or PowerShell.

  • The disabled Token Replay extension is enabled again after a server restart.

    If you disable the Token Replay extension from the Control Center and restart the vRealize Orchestrator server, the disabled extension is enabled again. This problem is now resolved, and the extension remains disabled until you enable it.

  • The vCenter plug-in fails to initialize on restart if there are invalid endpoints.

    The vCenter plug-in fails to initialize on restart if there are invalid endpoints. Because of this problem, the vCenter plug-in can disappear from the vRealize Orchestrator inventory.

  • Workflow runs of the Send notification workflow of the Mail plug-in fail when the password field is not required.

    Workflow runs of the Send notification workflow of the Mail plug-in fail when the password field is not required.

  • The workflow designer provides invalid information about string values.

    If a workflow includes multiple strings with a 'false' value, they might be evaluated with the boolean 'true', and not 'false'.

Known Issues

  • Duplicated workflows created in Orchestrator Legacy Client might display a constant instead of an external action in their value options.

    When editing the input parameters of a workflow that is designed in the Orchestrator Legacy Client, and duplicated in the vRealize Orchestrator Client, the value options might be set as a constant instead of an external action.

    Workaround: Navigate to the Input Form tab and edit the input parameter presentation to include the required external action.

  • Unable to select an action as an external source in input forms because of a return type issue.

    In the vRealize Orchestrator Client Input Form tab, you are unable to select an action that has a return type of either Any or Array/Any for a default value or value option.


    1. Log in to the vRealize Orchestrator Client.
    2. Select your workflow and navigate to the Input Form tab.
    3. Set the action with the return type expected from the widget default value or value option and save the changes.
    4. Select the default value or value option action, save the workflow, and revert the action to previous version or change the return type back to the Any type.

check-circle-line exclamation-circle-line close-line
Scroll to top icon