Release notes

Known limitations and their workarounds

• Multiple dependencies are not added when a job stream is submitted

  If you add multiple dependencies separated by a comma when submitting a job stream, dependencies are not added.

  Workaround

  Add each dependency separately with the follows keyword and use the semi column as a separator. For example:

  Ocli plan submit sbs <jobstream> ; follows=<dep1> ; follows=<dep2> ; follows= <dep3>

• 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.

• REST API: time zone in UTC format only

  When using REST API, if you run a query defining a time zone for the job in plan, the results are displayed in UTC format even if the defined value is different.

• An error occurs when using “FULL” in display, list, and modify commands.

  The “Full” term is a reserved key word in Orchestration CLI. If you use the “FULL” term as an item name or part of an item name in the list, display, or modify commands, it is treated as a keyword, and an error occurs.

• Incorrect value displayed in the job log for the output condition with variable $stdlist

  If an output condition that contains the variable $stdlist is false, an incorrect value error is displayed as status in the job log.

Contacting HCL support

For technical assistance, contact HCL Software Customer Support.