Skip to main content
Skip table of contents

Version 2025.01.1.307

This version was released on 


Announcements

Platform Features and Improvements

  • The “User Details” menu in the navigation bar now displays the user's login name and full name for easier identification.

  • The “Systems” page has been redesigned using MUI for an enhanced user experience and modernized interface.

  • The "system rename" feature has been relocated to the system's context menu.

  • A "system navigation bar" has been added to streamline access to the system's settings.

  • The “Configurator” page now supports the option to set a default value for any conditional mapping which will be sent if the other conditions (if any) aren’t matched.

  • Improved the removing of the last conditional mapping from a field in the “Configurator” page.

Bug Fixes

  • Restarting the ZigiOps services causes rediscovery of the Azure DevOps schema (project.workitemtype) instead of loading it from the local schema file.

  • Failed load documents are not displayed on the Troubleshooting page when a business rule is active on Ivanti's side and expects additional inputs.

  • The ZigiOps "Health Status" displays as "Poor" when a system of type "Web Listener" is configured.

  • A duplicate test connection failure icon is displayed on the "Manage Integrations" page.

  • ZigiOps does not display an error when the test connection returns an HTTP 502 while connecting to a Zabbix system.

  • The platform fails to use a newly obtained ServiceNow OAuth token when working with attachments.

  • The platform sends an invalid 'Content-Type' header when attempting to obtain a security token.

  • Saving an action while on the "Target" tab redirects the user to the "Source" tab.

  • Saving incorrect credentials for ServiceNow with OAuth causes a loop during the security token acquisition process.

  • The "Login" button is not visible on smaller resolution screens.

  • The "Boolean" type fields are not displayed correctly in the side panel of the "Extract" document.

  • A "No query plan" error is displayed for certain sequences of configured “Expressions”.

  • Working with a custom field of type “label” in Jira results in an "nth not supported on this type" error.

  • When querying the "payload" field from a Datadog event, the response does not include the 'payload' field.

  • The "responder/id" field is sent as “String” instead of “Number” for Freshservice.

  • "Boolean" type fields are sent as "String" type fields for Freshservice.

  • "Boolean" type values are sent as "String" values in UQL, causing set manual filters to break for Jira.

  • Manually saving an integration incorrectly stores all hardcoded mapping values as "String" values.

Additional Content

  • N/A


Known Issues

  • N/A

JavaScript errors detected

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

If this problem persists, please contact our support.