.png?sv=2022-11-02&spr=https&st=2024-12-22T06%3A40%3A02Z&se=2024-12-22T06%3A50%3A02Z&sr=c&sp=r&sig=CW%2Bh5Fq0KLoFkIRNlz5mqTHgHBsHhTkEprTQe27I2nM%3D){kind=logo}
2023.1.13 Maintenance Release
- 20 Nov 2024
-
DarkLight
-
PDF
2023.1.13 Maintenance Release
- Updated on 20 Nov 2024
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Release Notes
Bug Fixes
This maintenance release of IAP includes fixes for bugs that were reported to Itential Product Support.
| Key ID | Release Note |
|---|---|
| ENG-1797 | When the output of a task reference variable contains non-alphanumeric characters, the Automation Studio UI will parse the output as a template literal and incorrectly display it as a static value. To resolve, the Regex checker was expanded to capture all expected job variable and task variable names. |
| PH-149216 | Templates did not sort correctly within Template Groups in the side navigation panel of Automation Studio, and new templates were missing. |
| PH-151582 | When adding Transformation tasks to the canvas via drag-n-drop in Automation Studio, the “Extract Output” option is automatically selected, but when added using the Assets tab menu, the “Extract Output” option is not auto-selected. Improved the UX by auto-selecting all advanced task options in the UI. |
| PH-152135 | Triggers with saved data would sometimes launch automations with incorrect JSON form data. Secondary Key ID: PH-160246 |
| PH-153653 | When creating workflows in Automation Studio using the Evaluation task and the Enable Query option was deselected (not checked), the task would not save changes made to the Enable Query checkbox. |
| PH-153790 | When creating job variables using Workflow Engine tasks Pop, Push, and Shift in Automation Studio, an invalid job variable reference name error would display upon saving the workflow. |
| PH-156943 | When creating automation triggers in Operations Manager using a JSON Form with Multi-Select Dependency, the Form Data dropdown fields did not render correctly in the UI and users were unable make a second selection. |
| PH-159278 | When multiple adapters are restarted at the same time using the PUT /adapters/:name/restart API call, some adapters did not restart correctly. |
| PH-159517 | Users were allowed to apply duplicate customKeys in Form fields, resulting in a mismatch between Form Elements and the Form Schema. A validation check within JSON Forms now restricts duplicate customKeys in form fields. |
| PH-159588 | When creating a JSON Form, no validation check was applied to verify if the form name already existed. When duplicate forms existed, both names displayed in the left sidenav panel but only one form could be opened, and edits made to one form also occured in the duplicate form. |
| PH-159773 | When importing a Pre-built into Admin Essentials, the import would fail but the Pre-built components (workflow and JST) would still appear in Automation Studio or Operations Manager. |
| PH-159782 | When renaming functions in JSON Transformations, users were unable to update or save functions to the new name. |
| PH-160007 | Transitions would disappear and JST Designer would become unstable when using predefined functions in JST Builder. |
| PH-160171 | Deleting Command and Analytic Templates from the collection view UI in Automation Studio would display a failure notification. A success response now returns to inform users the collection view has successfully updated. |
| PH-160197 | The job variable UX for output schemas was inconsistent with the UX for incoming variables in Automation Studio. UX was improved by properly generating workflow schemas whenever users select the Store Output as Job Variable option on the Output tab in the task dialog. |
| PH-160336 | Apps and adapters would continue to send "alive" health check reports even when the dead process checker was disabled in the systemProps under IAP Profiles, thereby leading to performance issues. |
| PH-160374 | When creating an automation by scheduled or event trigger with assigned Authorization Groups, the workflow failed to run and did not display in Operations Manager. |
| PH-160392 | When importing Pre-builts with an already existing JST, the import did not overwrite the existing JST but duplicated it instead by a "(1)" to the JST name. |
| PH-160475 | When users select the "Select All" option in the Edit Group dialog after creating a new group within Admin Essentials, roles would be selected at random across multiple pages. |
| PH-160501 | When job data linked to a Lifecycle Manager (LCM) resource is archived, the resource can no longer be updated or deleted, thereby causing an error. |
| PH-160535 | When importing workflows in Automation Studio, template variables disappeared and the workflow canvas would not save. |
| PH-160548 | When connecting to adapter-nso, the NETCONF connection would fail due to weak fault tolerance and cause the adapter to crash. |
| PH-160549 | In a system setup with NSO 5.7 or NSO 6.1, adapter-nso would not stay connected or run if a device name did not exist. |
| PH-160576 | When polling the prometheus_metrics API for a running job in Operations Manager, the counters for iap_active_sessions and iap_total_api_calls would reset every 20 minutes regardless of whether a login session had expired or not. |
| PH-160578 | When using NSO version greater than 6.0, NCAM rules configured in Cisco NSO are not properly inherited in IAP, resulting in users having access to different components than intended. |
| PH-160607 | In the new canvas UI, injecting job variables into a larger string value (a feature referred to as template literal strings) in a task property does not work, resulting in the user-entered value being erased by the system. |
| PH-160978 | When editing a Query task in Automation Studio, the user is sometimes unable to change any variable source property between "static" and "task". |
| PH-161014 | Searching transformations on the “Transformations” tab of the collections dialog in Automation Studio gives no results, even if there are matching transformations in the system. |
| PH-161098 | When making different API calls in IAP, the Context Manager maps would increase (grow) over time and cause memory leaks. |
| PH-161138 | When executing getDevice in Configuration Manager without specifying a device name, the task will hang and block any additional IAP calls to Cisco NSO if the NSO instance contains more than 150K devices. |
| PH-161308 | When using JST Designer, attempting to add a function to the transformation results in an unresponsive browser if the number of API routes in available adaptors exceeds 15K. |
| PH-161656 | When making app/adapter calls to the getTasksList API in IAP, the task is unnecessarily looping over data, and thereby causing a slowdown in response time. |
Improvements
This section highlights featured improvements to functionality in this maintenance release.
| Key ID | Release Note |
|---|---|
| PH-160425 | Added the ability for customers to auto discover Automation Gateway so that customers can reliably discover any changes made to a number of Automation Gateways within their environment from within IAP as a workflow canvas task or API call. |
| PH-161087 | Added a new property, compactJobEvents, to the Workflow Engine. When a customer enables this property in IAP it will remove all user-defined job/task variable values, thereby reducing the size of the job event and improving application performance. |
| PH-161594 | Improved IAP event system performance by limiting the events sent only to apps/adapters which have subscribed to a given event. |
Was this article helpful?
