10-September-2016 This is bug release
Moved update.resultflow.com to 236-mbt.rfblog.net
The original name was never intended to be publicly visible but now it is used to host our training materials so the name is a bit confusing. This site is a ‘blog’, so we’re calling it that.
P280 – Bug in creating Filter workflow with 3 or more filters
The Filter workflow definition dialog did not correctly support 3 or more filters. Now it does.
P281 – Bug in Router workflow dialog
Similar to the Filter workflow UI bug, this one is now fixed as well.
P282 – Error in starting MTurk workflows
When an MTurk workflow was started and there was either an error in the HIT template or the MTurk balance was 0, there was a timing problem that prevented the workflow from entering the error state like it should have. This is now fixed. When your HIT template has syntax errors or you have a zero balance, the MTurk workflow will throw an error task on your dashboard.
If you have MTurk workflows on documents for longer than the HIT lifetime, then you likely have experienced this problem. To fix, simply delete those workflows and restart with the ‘Run Workflows’ button. For example, if your HIT lifetime is 4 days and you have a document running an MTurk workflow and the date on the document is 7 days ago, you should kill that workflow and start a new one.
P284 – Formatting lost in TextBroker results
The UI for TextBroker has two “pickup” functions – one for plain text and one for HTML – but the API supports *only* plain text with newlines used to delimit paragraphs. That obviously is pretty messy to deal with in ResultFlow. We now convert the plain text file to HTML by converting every newline delimited string into an HMTL paragraph. This allows you to process TB results using DOM expressions in scripts just as you would any other HTML document.
P285 – Minor change and improvements to P233
Small change to the task filter/sort feature to make the operation more clear. You can select only on workflow type, not by user assigned name. The way a task is displayed now does not show the workflow type, but instead the details of where the workflow is running.
P286 – Description field displayed for Content folders
This is useful to provide instructions, documentation, or reminders on the folders used in your workflows. We will use this to add documentation for the reference workflows.