My company, Wortell, migrated to SharePoint 2010 pretty quick after the RTM release. Our CTO, Office 365 MVP Danny Burlage, wanted to introduce a temporary collaboration workspace. This workspace could be used for working on short assignments or brainstorm sessions. We created the site and let the users create sites and left them pretty much alone.
The problem was we had no idea if sites were used or not. There were also sites created for testing SharePoint 2010 functionalities. This was not really what we intended. The site, unfortunately, kind of "died a slow death" and was not used anymore.
I was part of the migration team of our internal portal and still feel responsible for the use of the portal. I sometimes work with Nintex Workflow 2010 and stumbled at documentation about automatic site creation. You can find it here. I read it and thought it would work perfectly for our collaboration space. I wanted to take a different approach and thought about the following scenario:
- The user goes to the collaboration space
- The user fills in a form and applies for a temporary site
- The site gets created by the Nintex Workflow with the appropriate metadata (name and permissions)
- The user gets an e-mail after two months for renewing the temporary site
- When the user decides to renew the site, a new e-mail is send two months later. This repeats until the user decides to delete the site.
The name of the site. This field is also used for the URL of the site.
7:37 PM
Unknown
Posted in: 
5 replies:
Hi Jasper,
Very good article and really useful. I have one question about the notifications. Does the workflow send out a notification to each of the owners, to the requestor of the site, or maybe both? In other words. What happens when for this site Donny's account is being removed, or is being altered into reader? Workflow will send out notification to (new) owner of the site?
Thanks for your reply!
Greets, Edwin
Hi,
Thanks for your reply! You can configure that in the workflow action that assigns the task. I will show that in the next article.
The wait/waiting part always was tricky when doiing IISresets or reboots. Has that been improved in Nintex WF 2010?
Gr. J
To be honest, I don't know.
Doing a IISRESET or server restart won't effect the wait action. As Nintex Workflow uses the native Sharepoint workflow Engine and timer job service. So whilst the the job is in Wait, the SharePoint Timer Service will keep the workflow honest. :)
There was an instance I remember in SP2007 where there was a .NET 2 patch that broke that relationship and any job that had a wait / pause / loop etc broke. I haven't seen this since.
Post a Comment