This first release of 2013 adds a bunch of requested items and fixes some significant misfeatures plus the completely new feature “activity reporting”.
MTurk Activity Stream
Every 24 hours a summary of HITs submitted, approved and reject is posted to each Persona.
Feed Activity Stream
Every time the system refreshes a Feed folder, an activity record is posted to the Persona where the Feed was created. The record appears on the Persona dashboard and shows both successes and failures for each URL within each Feed folder.
Clone Feed Feature
When creating a Feed folder, you can now “clone” an existing Feed folder. This copies all the URLs from the existing folder but does NOT “start” the Feed. To start your new Feed, either pause, save and unpause, or edit the URL list and save. In both cases this updates the Feed in the system causing it to start loading items.
Social Channels are Now Specific to Personas
The contents of the “Social Channels” tab is now unique to the Persona where it is defined. Define these channels only for the Personas where they are used.
Posting to Facebook Pages and Walls
The social channels now support posting to Facebook pages as well as Facebook walls.
Open Documents in a New Window
In the document list view, clicking the URL of the item opens the contents in a new window instead of replacing the ResultFlow window.
New Router Workflows (4, 5 and 6)
In addition to the Router-2 and Router-3 workflows, there are now versions with 4, 5 and 6 output folders. Use these when you want to split an input document stream into more than just 2 or 3 outputs.
Filter2 Workflow
This new flow is just like the Filter flow but provides two output folders matched by two different sets of patterns.
Clone2 Option to Delete Input Item
The “delete input item” option has been added to the Clone2 workflow.
Expanded Length of Filter Workflow Parameters
There was a 256 character limit on the length of the Filter matching parameter. This has been expanded to 1024.
MTurk Retry on Failure
We saw some cases where the Amazon interface timed-out and left ResultFlow in an ambiguous state. We now retry on error so this will not happen.