2023.2.14 Maintenance Release

Updated on 05 Feb 2025

Dark

Light
PDF

Article summary

Did you find this summary helpful?

Thank you for your feedback

Release Notes

Bug Fixes

This maintenance release includes fixes for bugs that were reported to Itential Product Support.

Key ID	Release Note
ENG-5861	Fixed an issue with JSON form elements, where any form layering (container/schema combination) is assumed to be a binding configuration (and fails to parse) when at least one actual binding exists.
ENG-7144	When querying form data using the dropdown search bar, multiple pages of results return and you have to scroll through them to find the specific data you need. To resolve this issue, updated the `rodeo-ui` dependendency. The JSON Forms dropdown search now works properly.
ENG-7910	Fixed the setup of the Itential Platform `systemd` unit file for `systemctl restart` and `systemctl stop`, allowing it to clean up its child services and preventing race conditions that resulted in an unclean Redis state. This fix applies to all released versions of Itential Platform.
ENG-8032	When importing JSON Forms and then running the form via the Preview button, the wrong return value was showing. As it turns out, duplicate dropdown labels were causing the returned values to be incorrect. To fix this issue, updated the `rodeo-ui` dependendency. Duplicate labels in a dynamic JSON Form are now supported.
ENG-8258	When a `childJob` Workflow Input Variables Loop Array is set to a `task` variable in Automation Studio, opening another child job task without closing the first window will sometimes cause the source to reset to `static`. Updated the Task Data Workflow Editor to include a unique `taskID` to reset task data when variables change.
ENG-8303	If a workflow is configured with a JST on a `childJob` task, it will attempt to inline the entire JST document into the workflow on export. If the JST is missing at the time of export, Worfklow Builder is unable to handle the export and crashes (stops working properly). To resolve this, added a check to ensure the JST exists before attempting to inline the JST document into the workflow.
ENG-8305	When creating a large number of Golden Configuration tree nodes in Configuration Manager, the pop-over menu for several nodes was hidden in the browser window due to an incorrect menu location. Fixed the menu position to be from "bottom" to "left", so that every node will display their respective pop-over menu correctly.
ENG-8343	When updating an existing Command Template, adding an additional command to the template would cause it to not format correctly which lead the API to timeout when running the command. Applied a fix in `app-mop` that ensures an undefined error does not cause the API to timeout.
ENG-8444	The Automation Gateway adapter was not honoring the base path configuration that allowed it to work with a proxy server that utilizes a non-standard path and the AGManager tasks would error. Updated `adapter-automation_gateway` by setting the `entitypath` to work with the `basepath` configuration. A non-standard base path can now be utilized through a proxy server and AGManager tasks work as expected.
ENG-8493	Fixed a bug in processing Integration Models with `operationId` strings that contained special characters (not a-z, A-Z, or _) that was causing the associated tasks to be considered invalid. Workflows that contain tasks from the Integration Model are now valid and run without error.
ENG-8587	When attempting to save, import, or run a workflow that contained a JST, workflow validation would error with "Cannot read properties of undefined (reading 'type')". This was due to encoding as a result of the JST being pulled directly from the database. To resolve, added logic to pull and decode the JST from the `app-jst` application, thereby allowing workflows with JST to run as expected.

Improvements

This section highlights featured improvements to functionality in this maintenance release.

Key ID	Release Note
ENG-8204	When attempting to access the `getForms`, `getFormById`, `deleteForms` and `updateForm` API endpoints in Itential Platform through tasks, the user was not able to access them. Updated the JSON Form schema to enable all JSON API tasks in Automation Studio. All tasks are now visible and able to run on the canvas.

2023.2.14 Release Versions

Automation Platform Versions

component	version
@itential/adapter-automation_gateway	4.31.4-2023.2.2
@itential/adapter-azure_aaa	1.7.5-2023.2.2
@itential/adapter-email	4.2.20-2023.2.0
@itential/adapter-ldap	2.14.3-2023.2.2
@itential/adapter-local_aaa	4.5.2-2023.2.0
@itential/adapter-nso	7.9.4-2023.2.13
@itential/adapter-radius	2.2.2-2023.2.0
@itential/app-admin_essentials	5.4.10-2023.2.18
@itential/app-ag_manager	1.20.3-2023.2.1
@itential/app-automation_catalog	2.13.7-2023.2.1
@itential/app-automation_studio	4.69.3-2023.2.177
@itential/app-configuration_manager	3.117.5-2023.2.26
@itential/app-form_builder	4.15.3-2023.2.5
@itential/app-json_forms	1.42.3-2023.2.22
@itential/app-jst	1.15.11-2023.2.11
@itential/app-lifecycle_manager	1.38.4-2023.2.15
@itential/app-mop	6.21.1-2023.2.15
@itential/app-nso_manager	2.25.2-2023.2.2
@itential/app-operations_manager	1.215.10-2023.2.51
@itential/app-service_catalog	3.14.1-2023.2.3
@itential/app-service_management	3.0.2-2023.2.3
@itential/app-template_builder	2.9.1-2023.2.8
@itential/app-workflow_builder	5.55.2-2023.2.18
@itential/app-workflow_engine	11.9.6-2023.2.42
@itential/database	2.0.8
@itential/iap-ui	1.14.3-2023.2.7
@itential/itential-utils	3.2.1
@itential/logger	3.1.2
@itential/network	4.1.5
@itential/pronghorn-core	15.8.10-2023.2.59
@itential/search	1.3.3-2023.2.0
@itential/service	3.1.18
@itential/tags	3.2.2-2023.2.0

Was this article helpful?

What's Next

2023.2.13 Maintenance Release

Table of contents

Release Notes
2023.2.14 Release Versions