This is a critical bug fix release with a couple minor enhancements included because they were ready to go.
Facebook Venue
Prior changes relating to feedItemUrl caused our Facebook venue to do precisely the wrong thing in many cases. This is now fixed so that the venue behaves consistently no matter how the document was created. The venue now always uses the document content as the message to post. Additionally, if the content contains a URL, that URL is “attached” to the post as a link so that Facebook can grab open graph data from it.
Twitter Venue
There was a system software update about a week ago that changed the SSL connection layer for ResultFlow. This completely broke the connection with Twitter as well as some feeds. This is now fixed and Twitter is back in operation.
NOTE: None of the documents that failed to post will be rescheduled – that’ll have to be done manually. We should have specific work-around instructions for you tomorrow.
TextBroker Service
Getting this interface working properly has been more complex than expected. We have now fixed and test the initial submission and revision steps of the workflow and are waiting on completion of work at Text Broker to prove out the rest. This should be completely fixed and ready for your use no later than Monday – we’ll make an announcement as soon as we’re certain all the issues have been resolved.
Document Description Field
This is a minor enhancement: you can now get the document description from inside scripts. The syntax is ${doc.description}.
MTurk TW Start Workflow Dialog
The order of fields on this workflow start dialog was really confusing – it is now much less so.
Leave a Reply