Release notes V1.1.2

The release notes for HCL Universal Orchestrator contains the following topics:

Known limitations and their workarounds

  • Manual deletion required for existing executable plug-ins
    If you upgrade from HCL Universal Orchestrator V1.1.0 or V1.1.1 to V1.1.2 or later, the existing executable job plug-ins are not deleted automatically. This results in the failure executable jobs.
    Workaround
    You must manually delete the older executable job plug-ins after upgrade.
  • Intermittent data displayed during performance metric monitoring
    If you monitor the performance of HCL Universal Orchestrator in any data visualization platform when the resources are overloaded, the metrics report is not shown continuously, and a time gap of 3-4 minutes is observed.
    Workaround
    Add more CPU resource to the HCL Universal Orchestrator cluster to manage the workload.
  • Error while using reserve keywords as an item name
    The following list contains reserved keywords in Orchestration CLI for model commands.
    • showid
    • full
    • lock
    • unlock
    • offline
    • filter
    • noask
    • force
    • preview
    • errorprompt
    • unlockAfterAction
    • noUpdate
    If you use any of these keywords as an item name or part of an item name with any of the model commands, it is not treated as free text; instead, it is identified as a keyword, and an error occurs.
  • The screen help page is only visible if the browser where the Dynamic Workload Console runs is set to one of the supported languages.
    The screen help in the Dynamic Workload Console is only visible if the browser where the Dynamic Workload Console is running is set to one of the following supported languages:
    • Chinese (Simplified)
    • Chinese (Traditional)
    • English
    • French
    • German
    • Italian
    • Japanese
    • Korean
    • Portuguese
    • Russian
    • Spanish
  • The Show only selected option in the Orchestration Monitor page does not work on specific actions
    The Show only selected option in the Orchestration Monitor page does not work in the following circumstances:
    • when you select Predecessors from Job streams.
    • When you select Predecessors or Show run instances instances from Jobs.
    • When you select Events from Event source.
    • When you select Events from the Job stream table.
  • Launch in context brings you to the wrong page if you are not already logged into the Dynamic Workload Console
    If you are not logged into the Dynamic Workload Console and you launch a URL using the launch in context, the Dynamic Workload Console requests you to enter your credentials and then brings you to the Welcome page instead of the requested one.
    Workaround
    After the log in, launch the URL again.
  • The fence value on workstations needs to be reset when upgrading from HCL Universal Orchestrator v1.1.0 to HCL Universal Orchestrator v1.1.1
    If you are upgrading HCL Universal Orchestrator from version 1.1.0 to version 1.1.1, the fence value on workstation is automatically set to 100.
    Workaround
    Set the fence value on workstations to 0 to let the jobs run as expected.

APARs and defects fixed

Review the list of defects fixed for HCL Universal Orchestrator.
  • Parsing in streaming
    Previously, when you added a job stream definition with a non-existent dependency it was saved as a draft in the database, without any specified dependencies. You were then able to save another job stream by adding this draft job stream as a predecessor. However, this resulted in disruptions when the job stream was run. This problem is fixed now.
    Now you cannot save a job stream definition with a non-existent dependency.

Contacting HCL support

For technical assistance, contact HCL Software Customer Support.

Before you contact the customer support, collect all the details of the problem that you encountered. You can try to collect the following informations:
  • Logs, traces, and messages related to the problem. For more information, see Logs and Data gather.
  • If possible, provide steps to reproduce the problem.
  • The environment and version in which the problem occurs. For example, if the problem occurred in the cloud, the Kubernetes version.