Nintex Connect

Thought it would be sweet to share with everyone different solutions you've had to different problems.. And how you used Webservices to sort it..

While not MOSS, we have a LOB app that uses hosted WSS 3.0 for some collaboration scenarios. We semi-regularly tear down and build new sites as needs demand. As part of the deployment for new sites, we need to configure custom permission sets, create new groups, and assign the permissions to the groups.

We created workflows to remove most (not Admin) OOB permission sets, create our permission sets, delete most groups, create our groups, and then match up the groups with the new permissions, all using web service calls to the hosted WSS. Was a bit tricky initially, as creating a new permission set requires you to pass a bit mask for the access settings needed.

I love the workflows. So much better than doing it manually. Ugh.

I have on my radar to apply custom permissions to lists in our default template that gets deployed, but haven't gotten to it yet.

We have a client that needs to periodically report on all the security groups for a complex site. We're in the process of writing a WF that:

1. uses the MOSS webservice to return all users in a security group (http://<site>/_vti_bin/UserGroup.asmx -- GetUserCollectionFromGroup)
2. stuff all the user attributes into corresonding collections
3. iterate through these collections to
1. create and populate a list item per user
2. query Active Directory (AD) to gather additional user info (manager's name, dept., etc)

We're almost complete, but have reached a speedbump. In step 3.2 above, if a user has left the company and their AD account is no longer valid, the WF breaks. I think the work-around will involve using the LDAP Query's error handling function to skirt around the bad accounts -- just have to implement it!

On a different note, has anyone explored using web services to report site/subsite metrics? This could be really cool!