The Baretta

What Nintex Workflow for O365 has an action to create a site automatically in SharePoint, but it's functionality is quite limited.  You can't create groups and you can't add staff to those groups.  This tutorial shows you how to create a Nintex workflow to automate the whole process using SharePoint Web Services. Even better, we are going to create the ability to automate Site Creation across multiple Site Collections. If you're looking for a tutorial on how to do this in Nintex Workflow 2010/2013, I've written an article here:  SharePoint 2010 - Automate Site & Group Creation with Nintex Workflow 2010 Why As most SharePoint administrators are aware, it's ALWAYS a bad idea to give staff the ability to create SharePoint sites.  They will end up creating them for the wrong purposes, will not maintain them, no retention policies will get assigned to them, etc. However, you don't want to restrict your users creative freedom.  You want to govern it...

This article stems from another article explaining how to [[Automate Site & Group Creation with Nintex Workflow O365]] - Coming Soon What Use Powershell to retrieve detailed data about the permission levels on a particular site Why I had previously created a Nintex Workflow to Automate Site & Group creation using nintex workflow on SharePoint 2010 .  I needed to recreate the same workflow in SharePoint Online / Nintex Workflow O365, however the SharePoint 2010 script for retrieving Permission Mask values did not work. How Using Powershell 3.0 or later, and SharePoint Online Powershell Module.  Open up the SharePoint Online Powershell Module and paste the following code (after updating the variables at the top for your site and admin details): # SharePoint Online - Retrieve the Permission Mask Values for a Site using Powershell # Specifies variable $AdminURI = "https://company-admin.sharepoint.com" $RootSiteCollection="https://company.sharepoint.co...

What Nintex Workflow has an action to create a site automatically in SharePoint, but it's functionality is quite limited.  You can't create groups and you can't add staff to those groups.  This tutorial shows you how to create a Nintex workflow to automate the whole process using SharePoint Web Services. Why As most SharePoint administrators are aware, it's ALWAYS a bad idea to give staff the ability to create SharePoint sites.  They will end up creating them for the wrong purposes, will not maintain them, no retention policies will get assigned to them, etc. However, you don't want to restrict your users creative freedom.  You want to govern it in a manageable way. In order to keep track of all your SharePoint sites, we need to ensure that when we allow staff to create sites/content, it is being properly tagged with the right information.  As long as you are logging & tagging sites with extra data, you can easily govern and manage those sites far i...

This article stems from another article explaining how to  Automate Site & Group Creation with Nintex Workflow 2010 What Use Powershell to retrieve detailed data about the permission levels on a particular site Why I was looking for a way to automate Site & Group creation using nintex workflows.  In order to create groups, you need to call a SharePoint Web Service.  That Web Service requires an input value called 'permissionMask (int)'. This powershell script will allow you to find the correct permission Mask related to your particular environment & permission levels. How Jump onto your WFE, open up SharePoint Powershell as admin and paste in the following code (with the site you wish to retrieve data for: ## Get site permissions using SharePoint 2010 web service in powershell $uri=" http://rootsite/subsite /_vti_bin/Permissions.asmx?wsdl"  ## $siteName is a string which contains the site name for which you need to get the permissions [St...

Wow that's a long heading...  Let me explain how this is done, and why this path was chosen out of all the options. THE OPTIONS Still to come... SETTING UP There's quite a few large steps to get this done, so I'll split it into the following sections, ensuring we test along the way to make sure we haven't missed a step: Install & Configure Oracle Client on Web Server Create custom Web Service in Visual Studio Deploy Web Service to IIS Build InfoPath Form Configure InfoPath Services Deploy InfoPath Form to SharePoint Environment Install & Configure Oracle Client on Web Server Ask your Oracle DBA what version of Oracle the database is running on. Navigate here and download the corresponding Client (for this excercise get the 32-bit version if its an option):  http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html Copy to the IIS Server (Web Front End) Extract and install, here's the settings I used for the i...