April 1st I started my new job at e-office.  e-office focusses on Human software, and does this using Microsoft, IBM and Google technology.
Human sofware can be seen as 'messaging', 'collaboration', 'enterprise 2.0', 'unified communications', 'user experience' and 'mobile'.
It does however not stop at the technology, because at e-office we believe that people and organisations are an equal part of the equation.

I've joined the SharePoint team at e-office, and I'm already very excited about the upcoming projects that I have seen.

You can follow e-office on:

twitter: http://twitter.com/#!/e_office_com

facebook http://www.facebook.com/group.php?gid=109382118015

linked-in: http://www.linkedin.com/groups?mostPopular=&gid=145232

Together with 3 colleagues from QNH Business Integration I am currently finishing implementing a already NEN 2082 certified project based on SharePoint 2010.
When SharePoint 2010 hits RTM there will be another audit for this version of SharePoint, because currently the pre release version has been certified.

NEN 2082 is a Dutch standard which is similar the DoD5015 and MoReq standards.

This project was done for the Gemeente Nieuwegein, which is a Dutch local Government.

For this project we have also been nominated for the “Innovation of the year” award:

More information (Dutch)

My colleagues at QNH:

• Jeffrey Tummers - http://blog.thumnet.com
• Alexander Ketelaar – http://sharepoint2010.nl
• Robert Sep

A collegue created a SP2010 workflow in visio, and imported it into SharePoint Designer 2010.
His flow used the following actions: 

• AddListItemPermission
• InheritListItemPermissions
• RemoveListitemPermission
• ReplaceListItemPermissions

SharePoint Designer 2010 throws an error when he validates the workflow (check for errors) or tried to deploy it.

The error (for searchablility):
This workflow action is not supported in this region of the workflow.
It can only be inserted in certain types of blocks.

SharePoint Designer does not show the actions as available.
After a bit of searching we found that these actions can only be added when inserted in an Impersonation Step.
This is logical as the impersonation step runs as the author of the document, in stead of the workflow starter.

Hope this is helpful.