Subscribe to our RSS feed or by email to receive automatic notifications when we ship new features and improvements.
2023.2.3
Platform 2023.2.3 is a maintenance release containing enhancements, bug fixes, and security updates.
Enhancements (2)
| Feature | Description |
|---|---|
| A new jobDelete API endpoint was (ENG-81ENG-895) | A new jobDelete API endpoint was added in the 2023.2.3 Release Version. The jobDelete API can only delete jobs that are completed or cancelled. Updates to the Ops Manager UI reflects utilization of this API endpoint via a new “Delete” button. |
| Project name display is more prominent (ENG-1990) | Project name display is more prominent in the Projects delete confirmation dialog. |
Bug fixes (29)
| Feature | Description |
|---|---|
| creating a JSON form with a (ENG-51) | When creating a JSON form with a Schema Combination set to the “oneOf” format option, the form preview returned an error instead of accepting the option. Fixed by adding a required property to handle the “oneOf’ schema format correctly. |
| Workflows would error at runtime when (ENG-94) | Workflows would error at runtime when the Merge task had a combination of empty and non-empty fields. Reconfigured the task to work properly whether a field is blank or contains a designated value. |
| a bug where the ‘jobStart’ event (ENG-108) | Fixed a bug where the ‘jobStart’ event in a workflow was emitted before sending tasks to the task queue for processing. Modified the order of processing to ensure ‘jobStart’ is not triggered prematurely. |
| creating Lifecycle Manager (LCM) Models with (ENG-203) | When creating Lifecycle Manager (LCM) Models with Actions via API the actions were added without an "_id", which prevented them from working properly. To resolve, modified the domain logic to look for an existing "_id" and create a unique id if one does not exist. |
| a bug in Operations Manager that (ENG-208) | Fixed a bug in Operations Manager that stopped the Auto-Work functionality from running after opening a child job on the workflow canvas. Auto-Work now starts and works as expected on a child job. |
| an issue with spiked CPU demand (ENG-209) | Resolved an issue with spiked CPU demand and data consumption when making job view queries via API in Operations Manager. |
| an issue where navigating from a (ENG-328) | Fixed an issue where navigating from a Compliance Report to a Golden Configuration would break the URL in Config Manager. |
| viewing an existing Golden Configuration (GC) (ENG-330) | When viewing an existing Golden Configuration (GC) tree and then creating a new one, the new GC tree displayed but the previous tree was selected in the left sidebar menu. Created a new UI element for the sidebar menu to automatically focus (select) the newly created GC tree in the sidebar menu. |
| Restricting role permissions to the Search (ENG-333) | Restricting role permissions to the Search Compliance Plan Instances API no longer crashes the Config Manager application. |
| using Regex in Golden Configuration there (ENG-339) | When using Regex in Golden Configuration there is an issue with marking multiple results of the same violation for remediation. Updated the Compliance Report Viewer property use ‘issueId’ as a unique identifier when selecting config lines for remediation. |
| Enhanced GBAC in Admin Essentials by (ENG-863) | Enhanced GBAC in Admin Essentials by adding “read-only” permissions. Users assigned to read-only groups can view workflows within Operations Manager but they are not allowed to execute (run) them. |
| Task Worker is turned off in (ENG-865) | When Task Worker is turned off in an HA setup, the Itential Platform server may still be involved in working the task. To resolve this issue, Itential removed load balancing from the APIs and tasks and made all calls specific to the Itential Platform servers. |
$id from the workflow input schema (ENG-867) | Removed $id from the workflow input schema calculation that originates from transformation task incoming schemas to fix issue where jobs would not start due to duplicate $id in the workflow input schema. |
| the Ramda dependency to the correct (ENG-868) | Updated the Ramda dependency to the correct version to resolve a build error. |
| build errors resulting from dependency conflicts (ENG-912) | Resolved build errors resulting from dependency conflicts. |
| a bug that prevented adapters from (ENG-955) | Fixed a bug that prevented adapters from registering their routes with Itential Platform after coming online. Added trace logging to the adapter startup sequence to identify race conditions and missing adapter models in the global config. |
| Running a transformation no longer displays (ENG-957) | Running a transformation no longer displays an “unsaved changes” error message when no changes are made. |
| a bug by removing an incorrect (ENG-958) | Fixed a bug by removing an incorrect threshold check in JSON Form Builder. Users can now add Form elements to the second field option in the JSON Form schema combination container via drag-and-drop. |
a check for undefined or null (ENG-960) | Implemented a check for undefined or null integer inputs in JST tasks to allow valid “0”integer inputs. |
| JSON forms can no longer have (ENG-1008 ENG-1013) | JSON forms can no longer have the same name. If a name already exists, a duplicate name error message is shown. |
| the error message that displays when (ENG-1030) | Improved the error message that displays when creating a workflow with a duplicate name inside a Project. |
| the sort function in the Collection (ENG-1035ENG-1042) | Fixed the sort function in the Collection dialog view. Workflows and transformations in Automation Studio now sort correctly by created and last updated date. |
| assigning callback functions for methods in (ENG-1137) | When assigning callback functions for methods in JST Designer, the dropdown of existing functions within a transformation would not work. Fixed an incompatibility in the function check for number vs. integer schema. |
| check within saveWorkflow to determine if (ENG-1145) | Added check within saveWorkflow to determine if there is an existing Project template with the same name as the task.variables.incoming.template. If there is, the task.variables.incoming.template is updated to include the namespace._id as a prefix in the name. |
| To determine if a toast should (ENG-1152) | To determine if a toast should be displayed, added an argument to reconcileCallbackSchema to detect if it is being called within the deleteAssign function. |
| the sort function in the Collection (ENG-1279) | Fixed the sort function in the Collection dialog view. Workflows and transformations in Automation Studio now sort correctly by created and last updated date. |
a bug in the getWorkflows task (ENG-2048) | Fixed a bug in the getWorkflows task that occurred when saving workflows with a date string for “created” and “last_updated”. The date strings were changed to date objects, thereby causing the workflow to error. |
| The runAction task now correctly sources (ENG-2451) | The runAction task now correctly sources variables from previous tasks. |
| opening a transition in Automation Studio, (ENG-2505) | When opening a transition in Automation Studio, the transition does not display in the UI. Updated the rendering logic in JST Designer to resolve the display issue. |
