Statuses displayed in the WD GUI when a workflow is executing

There are currently 4 statuses that appear on the WD scene when a workflow is executing:

• Ready: the element is ready to process data, but waits for the approve from the scheduler.
• Waiting: the element is waiting for input data or information that the data will not come anymore.
• Running: the element is executing a task.
• Done: the element has finished execution of all tasks.

Scenario:

1. Open the Workflow Designer.
2. Open the "Parallel NGS reads classification" NGS sample.
3. Select "Paired-end" radio button and click "Setup".
4. Add 2 input FASTQ files with paired-end reads, click "Next".
5. Add any step for Trimmomatic (e. "SLIDINGWINDOW" with windows size set to "5"), click "Next".
6. Add CLARK and Kraken databases.
7. On the last page of the wizard click "Run".
   Expected result: the dashboard view is shown.
8. Click "Go to Workflow Designer" button.
   Current result: (see the attached screenshot also)
   • the reader element has status "Ready" even when there are no more input files.
   • the currently executed element has status "Running"
   • all other elements have status "Waiting"
   • status "Done" appears just before the end of the execution

It is required to fix and simplify the behavior as follows:

• "Waiting" and "Ready" meaning is too close to each other and it may be hard to explain the difference to a user. So, it's better to show only three statuses in the WD GUI: "Waiting", "Running", "Done". I.e. display "Waiting" status in all scenarios where currently "Waiting" or "Ready" status is displayed.
• A reader in a workflow should track info about the number of input files/datasets, set status "Done" when there are no more input. All further element also should have status "Done" if they finished the execution for all input data.

Thus, in the scenario above the expected result should be the following:

• the reader will have status "Done" after passing the files to the next element
• the next elements (e.g. FastQC) will also have status "Done" after the execution
• a currently executed element will have status "Running"
• elements after the executed element will have status "Waiting"

In a scenario with several input files/pairs of files/datasets (e.g. the same workflow, but two pairs of FASTQ files), the expected result should be:

• on the first cycle with the first pair of FASTQ files:
  • the reader will have status "Waiting" after passing the files to the next element
  • the next elements (e.g. FastQC) will also have status "Waiting" after the first execution
  • a currently executed element will have status "Running"
  • elements after the executed element will have status "Waiting"
• on the second cycle with the second pair of FASTQ files: the statuses will change similarly to the expected result, described above for the scenario with a single pair of input FASTQ files.