Skip to main content
Skip table of contents

Version 2023.03.2.290

This version was released on 


Bug Fixes

  • Filtering by id field for uCMDB is sent wrong when using operations different than "is" and "is one of".

  • Updates to Remedyforce aren't working when comments are mapped, and no comments are extracted.

  • The payload to set the "Account" field value in Jira, specific to the "Tempo" plugin incorrect when using "projectkey.issuetype" collection.

  • The dropdown component was not populating “:type-template”.

  • Some topology relationships are skipped in the load requests to OA.

  • The CI cannot be set in ServiceNow if there’s a difference in the name’s case sensitivity.

  • Unable to save integration when putting an advanced condition in the respond field map in expanded mode.

  • Unable to display an integration containing a boolean trigger condition with “false” as a value.

  • A “boolean” field set as “false” in the trigger does not upgrade from document version 1.1 to 1.2.

  • A wrong API request is sent to uCMDB when trying to query data.

Platform Features and Improvements

Additional Content

Upgrade Notes

Upgrading to 2023.03.2.290 from 2023.01.191 (or earlier) requires clean-up and redeployment of the ZigiOps service.

  1. Stop the ZigiOps service or process.

  2. Back up the existing ZigiOps installation folder to another location.

  3. Remove the ZigiOps service.

    • Windows:

      • Execute the <ZigiOps>\service\uninstall_service.bat file to uninstall the ZigiOps service.

      • Delete all files from the <ZigiOps>\service\ folder.

    • Linux:

      • Delete the /etc/systemd/system/zigiwave.service file.

      • Delete the <ZigiOps>/ file.

  4. Install the new ZigiOps release in the existing ZigiOps installation folder.

    • Check the OS Service option during the installation, depending on your preferences.

  5. The service is automatically started when the installation is complete.

Upgrading from 2021.10.145 (or earlier) may require resetting the ZigiOps web console certificate truststore credentials by following the steps below; otherwise, ZigiOps would start, but the web console wouldn't be accessible.

  1. Stop the ZigiOps service or process.

  2. Remove the following entries (lines) from <ZigiOps>\conf\ file and save the changes afterward:

    • key-password

    • key-manager-pass

  3. Start the ZigiOps service or process.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.