Version 2021.11.167

This version was released on 03 Dec 2021

Release Notes

This version includes the below items.

Important

Upgrading from release 2021.07.648 (or earlier) will require resetting the ZigiOps web console credentials by following the steps below; otherwise, ZigiOps wouldn't be able to start.

1. Stop the ZigiOps service or process.

2. Remove the following folders:

   • <ZigiOps>\conf\settings\accounts

   • <ZigiOps>\conf\settings\credentials

   • <ZigiOps>\conf\settings\users

3. Start the ZigiOps service or process.

4. Log in using the default ZigiOps credentials.

5. If needed, you may change your default password.

Upgrading from release 2021.10.145 (or earlier) may require resetting the ZigiOps web console certificate truststore credentials by following the steps below; otherwise, ZigiOps would be able to 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\config.properties file and save the changes afterward:

   • key-password

   • key-manager-pass

3. Start the ZigiOps service or process.

Announcements

• You may now register for a free ZigiOps Cloud Trial directly from our website.

Bug Fixes

• We've fixed an issue with the ZigiOps web console, which is now normally accessible after a restart.

• We've fixed an issue with the unsupported Ivanti query filters added as "null", which is now properly handled.

• We've fixed an issue with the Azure DevOps integration, which now works with projects that contain a dot (.) in their names.

• We've fixed an issue with the Jira "VersionPicker", which is now extracted normally.

• We've fixed an issue with the correlation data, which is now returned successfully on partial load failure.

• We've fixed an issue with the "Respond Field Map", which now works when an action completes with partial ignore or partial load failure.

• We've fixed an issue with the TOPdesk troubleshooting, which now returns the correct error type and response code when the incident creation fails with the "400 Bad Request" response code.

• We've fixed an issue with the Jira "issue" collection, which now can discover cascading custom fields correctly.

• We've fixed an issue with the Troubleshooting page, which is now displaying a correct action run status.

• We've fixed an issue with the Troubleshooting page, which now shows errors when multiple requests are made for the action, and one or the last of them is successful.

• We've fixed an issue with the Troubleshooting page, which now shows a correct error on modification plan failure.

• We've fixed an issue with Field Mappings, which now works fine with values for reference fields that don't support multiple objects if the objects are on different levels (or reference).

• We've fixed an issue with Field Mappings, which now works fine when selecting the second object in field mappings with a mouse click that doesn't overwrite the first object.

Enhancements & Features

• N/A

Additional Content

• N/A