Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- Assume the Dashboard view reports 1 failed order from the orders summary.
- However, when following the link to the History view for 1 failed order then no orders are reported.
- This behavior is most probably due to the fact that "failed" orders are counted differently:
- The History view counts orders with a failed end status only. This excludes incomplete orders.
- The Dashboard view seems to count failed and incomplete orders as failed.
Desired Behavior
- Numbers from both views should be consistent.
- Possible solutions include
- that the orders summary in the Dashboard view could show a separate column for "incomplete" orders.
- that the wording in the Dashboard is modified to state "unsuccessful" orders which includes both failed and incomplete orders.
Test Instruction to reproduce the problem
- Prepare a test configuration.
- Setup two job scheduler in Active Cluster mode (Load balancing) & or standalone JobScheduler.
- Prepare test data
- Create a job chain with two job nodes that is configured for file watching.
- Prepare the 2nd job node to always raise an error and to force the order to be suspended.
- Perform the test case
- Login to JOC Cockpit
- Note the number of failed orders from the Dashboard view, widget "Orders Summary".
- Start the job chain by adding a file to the incoming directory.
- Check the JOC Cockpit Dashboard view, widget "Orders Summary" --> "failed status". The number is incremented compared to the number of failed orders noted before.
- Click on "failed status", the GUI will redirect to the "History" view, Note Filter "Failed" for sub-view "Orders" should be set.
- Verify test results
- The number of failed orders from the Dashboard view includes failed & incomplete orders. The History view uses separate filters for failed & incomplete orders. Therefore the numbers from both views are inconsistent.