Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.0
-
Fix Version/s: 2.3.0 RC
-
Component/s: Workbench - Results panel
-
Labels:None
-
Familiarity:Similar
Description
Paul reports
When running a workflow with a lot of strings, an inner nested workflow does not display the number of string that it was sent.
It does show the number of strings processes on each service, but there is no indication (other than the grey bar) of how many of the total number of stings are yet to be processed.
I've attached a screenshot to illustrate. Going in are 2547 strings, but you wouldn't know that unless you checked by some other means.This is useful for both error checking and for checking on the workflow progress.
Could this be added to future releases?
Solution:
Add to diagram current total number of iterations
Add '+' if upstream processors (uh, which are those) are still running
Testing:
Run workflow with significant number of iterations, ask users for feedback
From the user-requirements meeting on 10th March 2010, they need
Keep iteration number in diagram. If total "out of" is known then show it, otherwise indicate "out of" so far. For example, 101/207+ or 107/303