26 May 2018 This update is the first major release in over a year and includes three significant changes. First, we've complete overhauled the internal development process to make the app easier to develop and test. Second, we've reimplemented the Content On Delivery (COD) service as a custom workflow type, rather than the standalone Persona previously used, thereby making it far easier to use, more reliable, and easier for us to support. Finally, there are extensive new advanced MTurk features that have been in-work for more than a year.
- RF-6 Refactor MTurk code for use in scripts
Members of the ResultFlow Development Council asked for additional MTurk capabilities beyond what was possible in the predefined MTurk workflows (T, T2, and TW). This change creates scriptable APIs to manipulate MTurk workflow results in ResultFlow and directly access the MTurk service API. One of the key use cases this change supports is automated management of Turker Qualification groups. Full documentation of this feature set is forthcoming.
- RF-62 Implement COD service as a workflow
The first implementation of the COD service was created late last year with no specialized support in ResultFlow. This was necessary because of the work-in-progress on the new development environment. With that work complete, COD has been reimplemented as a "first class" workflow like MTurk and TextBroker. This makes COD far easier to integrate into our standard workflows and thereby far easier for users as well!
Remaining work includes (a) documenting the workflow; (b) updating the reference workflows; and (c) providing an upgrade/transition plan for existing users of the COD service.
IMPORTANT NOTE: The existing COD service, based on the COD Persona, will continue to work! This new implementation does NOT break the old one allowing us to get everyone transitioned in an organized manner.
- RF-38 Reformat and cleanup workflow rule dialogs
There was little consistency in the order of fields on the dialogs when defining a new workflow. This has been fixed to a large extent. It is likely that additional improvements can/will be made.
- RF-67 Change Scheduler default item count to 1
This is a pretty minor change, but one that does trip up new users when creating Schedulers. Since the most common use case is to move a single item, the default value has been changed to 1. There is no impact on existing Schedulers, you will only see this when creating new ones.