2 September 2019 This is a significant feature release. There are 8 features/improvements and 5 notable bug fixes.
There are documentation updates that are yet to completed for some of these software changes, so look for messaging regarding that in the next few days.
That said, this is a “non-breaking” change! You need not change anything in your existing app and usage pattern unless you choose to do so.
- RF-216 – Document Grid View
There are now two different view types in ResultFlow. The “row view” that we have always had, plus a new “grid view.” To change between the two, use the new button at the right-hand side of the document view immediately adjacent to the sort selection. This feature moves us closer to a more rapid curation interface. Note that in both views the image shown is the OG:Image value fetched from the source URL.
- RF-217 – Kanban board option to show images
In keeping with the above, you now have the option to show images in the Kanban columns as well.
- RF-169 – Integrate Temi transcription service
With this update we now have two very different transcription options: Scribie for high fidelity and Temi for high speed. There are advantages and disadvantages to both, and we continue to search for additional transcription options that provide additional cost/performance metrics.
- RF-134 – Merge edit and edit-meta into one single dialog
- RF-202 – Add error_user_title to dialog for Facebook Ad Setup
This applies only to the campaign setup button on the Facebook Ads Credential. There are numerous, and often subtle, errors that can occur in the Facebook funnel setup. With this change we are providing a more detailed level of reporting to clarify errors for both users and support(!) alike. IF you have an error during funnel setup, please copy and paste the error dialog output in your message to support as that helps a lot in getting you on-track.
- RF-205 – Uniform Structure for External Services
We integrate with a growing number of external services. With this release we have standardized how workflows interact with these services. In particular, every external service workflow now includes an order script and an result script. The order script creates the “order” sent to the external service and the result script takes the packet produced by the external service, along with the original document in ResultFlow, and composes the output document. This change makes these services WAY! more flexible and easier to use in custom workflows. Look for documentation updates and usage samples shortly.
- RF-208 – Update Scribie integration
This external service was updated as described above in RF-205 plus there were API/service changes at Scribie that needed to be incorporated as well.
- RF-218 – Adjust Copy/Move targets throughout the app based on source tab type
There are a small number of “standard use cases” for document copy/move based entirely on where the source document resides but the existing copy/move dialog was the same for all source locations. That is now changed. The copy/move destination selection dialog will now show different target folders for Feed folders, Content folders, and Venue folders. This significantly reduces clicks as well as unintended errors.
- RF-196 – Set timeouts for ESB uses of FileUtils.copyURLToFile
This is a low level system change that very occasionally caused recoverable errors.
- RF-198 – Persona import fails for persona with custom persona property
With the introduction of Persona Custom properties, we we’re stymied in our planned rollout of a new Persona because of this issue. That is now fixed and we will move forward with development of a Persona that makes use of custom properties to make (duh) customization of the Persona easier.
- RF-200 – Intermittent errors in new MTurk implementation on RFSB
There have been a number of minor (and a couple significant!) issues following on from major MTurk API update on 1 June of this year. Since we are the single largest use of MTurk across the entire ResultFlow community, we have been very much on top of this and have been doing incremental fixes for problems as they were observed. At this point – and with considerable relief! – I’m calling this API transition done.
- RF-201 – Persona Import/Export fails on some (but not all) Personas
This issue really only impacted about half a dozen veeeery long time customers with older and highly customized Personas that used MTurk. We call that a “corner case.” 🙂 It is now fixed.
- RF-219 – Apply missed MTurk API fixes to RF
This is my fault. Well, I’m in charge of tech, so I guess really it all is 🙁 but in any case…
for the small number of MTurk users, the balance at MTurk was NOT showing because I simply missed an update from one of our developers. That is now incorporated and all is well.