Versions Compared

Old Version 14

changes.mady.by.user Stonebranch

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note
titleBackward Compatibility Warning

Customers using the LISTADV API for Task Instances should be aware that an error in the JSON formatted response was corrected by defect D-11110 in UC 7.3.0.2. Resolution of this issue may break backward compatibility for customers using this API. For JSON responses, the output tag was changed to outputs. Customers are advised to review their usage of this API when upgrading.

...

Backlog

Title

Description

B-05459

View/Edit Actions associated with an instance directly from an Actions tab on the task instance form

Task Instance records now show the defined Actions from the Task Definition in a new “Actions” Tab.

B-08571

Display exit code in workflow monitor when hovering on task

The Task’s exit code has been added to the Status displayed when you hover over a Task Instance in the Workflow Monitor. In the following example the Task Instance has a Status = SUCCESS with an Exit Code = 0.

B-16872

B-17075

B-17076

B-17077

Workload Simulation

Users may have a new workflow, or a migrated workflow, for which they wish to validate the execution in the Universal Controller without actually having to execute the underlying operation of each task instance.

To facilitate this, a new framework for simulating a workflow, or alternatively, simulating a specific set of tasks within a workflow has been introduced.

In order to designate a task for simulation, you enable the Simulate option from any task form.

If enabled at the workflow-level, all tasks within the workflow will inherit the option and run in simulation mode.

By default, when an instance is running in simulate mode:

  • The instance will complete with a status of Success.

  • The instance will complete with an exit code of 0 (or 200 for the Web Service task).

  • The instances Status, Late Start, Late Finish, and Early Finish events are not published to running task monitor instances.

  • The instances Actions are not executed.

A simulated instance will transition through the same Status changes as a non-simulated instance, and honor virtual resource limits, mutually exclusive constraints, execution limits, etc.

Furthermore, authorization constraints, such as permission to execute on a particular agent, or execute using particular credentials, are also validated in simulation mode.

It may be necessary to customize aspects of an instance running in simulation mode, for example.

  • Change the end status from Success to Failed.

  • Change the exit code.

  • Add a simulation output template.

  • Add simulation variables that would normally be populated when an instance completes, such as ops_trigger_* variables populated by a completed monitor instance.

  • Enable publishing of Status, Late Start, Late Finish, and Early Finish events.

  • Enable execution of Actions by action type.

B-06436

B-16938

B-16939

B-16940

Workflow Instance Gannt Gantt Chart View

Workflow Task Instances can now be viewed as a Timeline. The View Timeline… menu item will be available from the Workflow task instance menu in the Workflow Monitor and View Blocking Ancestors graphs.

B-11390
B-16961

Forecast: Evaluation of variable run/skip criteria.

The Forecast feature will now attempt variable resolution for Run / Skip criteria.

The enhancement will introduce two new possible designations for the assigned Run/Skip Evaluation.

  • Run*

    • The forecasted task is tentatively scheduled to run based on the variable data available at the time of the forecast but is subject to change at run time.

  • Skip*

    • The forecasted task is tentatively scheduled to skip based on the variable data available at the time of the forecast but is subject to change at run time.

Info

If a parent workflow is evaluated as tentatively skip (Skip*) then no further evaluation is performed and its children are marked as tentatively skipped.

If a parent workflow is evaluated as tentatively run (Run*) then its children are further evaluated. You should assume that if the parent is marked tentatively run that this applies to its children. However, additional evaluation is performed to provide visibility as to whether the children, if they have Run/Skip criteria, would be run or skipped (tentatively or not).  

The Not Evaluated designation can still be assigned when an unresolved variable is detected during the evaluation of variable-based run/skip criteria.

Additionally, in the user interface, the Run/Skip Evaluation will now appear with colored styling for improved readability.

This applies to the trigger Forecast List, the workflow Forecast List, and the workflow Forecast Graph.

...