Release 4.2.2

This is a minor update to fix one really significant problem and add one small but very cool feature.

The bug

In version 3, workflows preserved the document name so getUrl in the MTurk answer template would always get the URL that was being abstracted.  In our new workflows this is not true which causes resultflow URLs to be posted to your blog!  This is now fixed.  No updates to your answer templates should be required.

The getXmlUrl function in the MTurk answer template now looks for feedItemUrl and uses that value if it exists so any document that originated from a feed, no matter how many times it was renamed via other workflows, will get a correct “original article” link when it finally hits your blog.

Bit.ly Shortener Integration

A new document property named shortUrl has been added that calls Bit.ly and returns their shortened version of the document’s URL.  This property is available in all templates, but your primary uses will be in Scripts (to compose Twitter output for example) or in MTurk Answer templates if you want to post short URLs to your Venues.

In Scripts, you call it like this:

${doc.shortUrl}

In MTurk answer templates, the document is named differently so it looks like this:

${originaldoc.shortUrl}