| the Itential Platform application unexpectantly stops (ENG-2698) | When the Itential Platform application unexpectantly stops working while processing service requests, the workflow tasks would remain in an indefinite running state and not return an error. Implemented error handling transition logic to error the tasks and alert users that a service stopped running. |
| an issue in JSON Golden Configuration (ENG-2882) | Fixed an issue in JSON Golden Configuration which would cause JSON key-checking rule values to always be treated as string. The key-checking value is now saved as the same type as the value in the JSON. |
| importing a pre-built workflow to overwrite (ENG-2932) | When importing a pre-built workflow to overwrite an existing workflow, the imported workflow remains in a draft state with validation errors or warnings until manually saved by the user. Applied a fix to processing workflows from pre-builts to always update the warnings and errors with the latest validation output. |
providing a template without an id (ENG-2965) | When providing a template without an id property to the update legacy template API endpoints, the resulting template is unusable in Itential Platform. Updated the update/create legacy template endpoints to ensure the id property matches the provided name to prevent issues using the template. The update legacy template endpoints will return an error if no id is provided. |
| creating a JSON Form with a (ENG-3034) | When creating a JSON Form with a multi-select dropdown dependency, the dropdown fields would not populate correctly or display any options. Updated the rodeo-ui to ensure that any JSON Form with a dropdown dependency that contains special characters now functions correctly. |
| the migration scripts for Configuration Manager (ENG-3143) | Fixed the migration scripts for Configuration Manager to automatically execute on Itential Platform startup. |
| Some child job loop configurations involving (ENG-3320) | Some child job loop configurations involving JSTs would incorrectly report validation errors in the workflow validation API. Updated the validation method to correctly format JST related child job properties when validating a workflow. |
| creating a callback function in JST (ENG-3888) | When creating a callback function in JST Designer via method card, connecting a constant value input to a non-constant value parameter causes the function to be generated incorrectly. Consequently, the function’s incoming schema is incorrect and is deselected from the method as incompatible. Applied a fix in JST Designer to ensure the function is generated correctly. |
| Transformation functions do not render as (ENG-4705) | Transformation functions do not render as expected in JST Designer if there is a function within the transformation that contains double quotes in its name. Fixed the rendering issues when opening functions in JST Designer. |
| setting an operand source type to (ENG-4715) | When setting an operand source type to null in the evaluation task and then saving the task, it incorrectly displays the type as object instead of null. Updated the source type dropdown to display null if the value is null. |
| If you open a corrupted transformation (ENG-4854) | If you open a corrupted transformation when you already have a transformation open in Automation Studio, and then attempt to delete the transformation, it will delete the document you already had open. Updated the delete transformation dialog to display and delete the correct transformation document. |
| checking the adapter status in the (ENG-4874) | When checking the adapter status in the API after a JSON RPC connectivity issue, the adapter will display as degraded until it is restarted, regardless of current connectivity. Applied a fix in the NSO adapter that was causing the adapter to remain degraded even when connectivity was restored so that the adapter now returns to a connected state without needing a restart. |
| configuring the form elements in a (ENG-4941) | When configuring the form elements in a dynamic form, there is no longer a UI crash when configuring a file upload field and then a dropdown on a JSON Form. |
| running compliance plans through a workflow, (ENG-5832) | When running compliance plans through a workflow, the compliance plan instance would not return properly. Fixed an aggregation issue with Compliance Plans in Configuration Manager that would prevent plan instances executed via workflows from displaying in the “Reports” tab. |
| the URL sanitation that occurs when (ENG-6301) | Improved the URL sanitation that occurs when navigating to assets with special characters in Projects. |
| using the export and import API (ENG-6311) | When using the export and import API in the Service Catalog on Itential Platform version 2023.2, the operation fails due to an issue with the ObjectId reference in the updated MongoDB driver. Corrected the ObjectId reference, ensuring that the export and import API in the Service Catalog functions as expected. |
The runComplianceForDevice task would not run (ENG-6465) | The runComplianceForDevice task would not run compliance for a Golden Config tree if the specified device only existed in the device group. Updated runComplianceForDevice to include devices that are only defined in a device group. |
| upgrading a workflow that has a (ENG-6499) | When upgrading a workflow that has a JST with a reference to a named job variable and a child job that contains a JST with a reference to a job variable that shares the same name, trying to run the workflow in versions 2023.2 and later will cause a validation error on the schema. Fixed the shared-nested JST input job variable name schema validation collision that occurs during workflow upgrade in 2023.2 and later that was causing schema validation errors when attempting to run that upgraded workflow. |
| using the Golden Configuration feature in (ENG-6688) | When using the Golden Configuration feature in Compliance Manager to audit device configurations, line disparities were noted in the compliance report. Fixed an issue in Golden Configuration that would cause incorrect compliance failures when a line contained regular expressions. |
