Veit Sanner's Blog

With this month I start a post series with Readlists . Each posts contains some links to articles devoted to one topic. besides introducing a new tag "Readlist" there is also a page where all reading lists can be accessed. February 2013 is all about Search in SharePoint 2013 .

This is the second part in the series Integrating Nintex Workflow with Twitter . Please go to part 1 to see the full story. In the first part of this series we have created a content News Page,  a page layout and deployed the feature to a SharePoint Publishing site . The page has an extra field which is used to enter the message sent to Twitter. This part covers the workflow which is used to tweet the availability of a new News Page . In order to get the following to work you need Nintex Workflow 2010 with Nintex Live enabled. (If you want to know how enable Nintex Live take a look at the Installation Manual which can be found on Nintex's Support Pages .) Step 1: Creating the Workflow The workflow for this scenario should be executed everytime a new page with version 1.0 of our content type is approved. Consequently, for updates to the content no tweet is sent. Nintex offers the possibility to hook into the item changed event for list workflows . Therefore go to the l

Overview One common scenario for corporate Internet sites is to sent notifications when a new article is published via social networks to their followers. With the availability of Nintex Live it became possible to twitter a tweet. In one of the later versions a similar activity for Yammer  became available. In this post I will show how you can use the "Twitter a Tweet" activity to notify your Twitter followers about new articles. This is going to be a two part series. In the first part I will create a News Page content type and page layout. In the second part I will show you the workflow which ensures that every time a News Page was approved the notification is sent to Twitter. Step 1: Content Type News Page In order to get started open Visual Studio 2010 and create an empty SharePoint project. Then add a new content type to this project based on Page . Modify the added content type to look like the this: 1: <!-- Parent ContentType: Page (0x010100C