Planning and Lifecycle Management
Your SharePoint sites and applications may change as your business needs and environments change. For example, your SharePoint environment may have new site collections and subsites added, and your applications' workflows, forms, and reports may be updated. Or you may want to reuse application elements like workflows and SmartObjects to interact with different libraries and lists. This topic describes some approaches you can follow to plan for changes or manage the lifecycle of your K2 for SharePoint integration.
- Reusing K2 for SharePoint artifacts
- Adding new site collections and subsites
- Managing K2 for SharePoint application settings
- Removing artifacts and integration
- Assigning Permissions
Adding a new Site Collection after Nintex K2 Integration
After integrating Nintex K2 with a SharePoint environment, you can integrate new site collections with Nintex K2.
Scenario
After a SharePoint environment is integrated with Nintex K2, you create a new site collection using the SharePoint Admin Center. You now need to integrate this new Site Collection with Nintex K2.
Steps
- After creating the new site collection, open the app catalog site.
- Navigate to the K2 for SharePoint app via the following path on the app catalog site: Site Contents > K2 for SharePoint .
- On the App Catalog > K2 for SharePoint page, click on the Manage App Deployments (SharePoint) link.
- Add the newly created site collection URL to the Enter a site collection to deploy to: section and click the Add button.
- Next click the OK button.
- Next click on the K2 for SharePoint app in the app catalog's Site Contents section.
- On the App Catalog > K2 for SharePoint page, click the Manage App Activations link.
- On the App Catalog > K2 for SharePoint > Settings > Manage App Activations page, add the new Site Collections URL to the Specify a site collection URL: section and click the Activate button.
- The Activate Site Collections page opens, and the Activation wizard runs. Once complete, click the Close button.
- The app is activated on the new site collection. Click the Close button.
Adding a new Subsite to a Site Collection after K2 Integration
At activation time, existing subsites in the site collection are activated with K2 for SharePoint. New subsites that are added at a later point, either manually or via a workflow, are also activated with K2 for SharePoint through the remote event receivers. This automatic activation may take a few minutes depending on your SharePoint environment. SharePoint Online instances do NOT include the remote event receiver, and so do not get K2 for SharePoint automatically added to new subsites. For SharePoint Online you must reactivate the site collection using the Manage App Activations page, which finds the new subsites and activates them.
Scenario
When a new subsite is created on a site collection that is already integrated with Nintex K2, you want to enable Nintex K2 integration on the subsite.
Steps
Adding a new subsite to site collection after Nintex K2integration can be done in two ways:
- For information on managing the K2 for SharePoint app at app catalog level see the management topic.
- For information on managing the K2 for SharePoint app on a site collection level see the management topic.
When integrating, or administering a SharePoint Online environment with K2 the following permissions are required:
- Adding, Deploying, Activating and Uninstalling the K2 app on a app catalog level requires Farm administrator permissions.
- Activating and Uninstalling the K2 app on a site collection level requires site collection administrator permissions.
-
You cannot change the SharePoint Site URL or SharePoint Domain name of a product-integrated SharePoint site. Doing so will break the integration with the site. If you have to change a site's web address or domain, you must treat it as a new site or tenant and rebuild your solution, or treat it like a multi-environment move and use Package and Deployment to move your solutions.
Alternatively, consider creating a new site and re-using the existing SmartObjects, forms, and workflows to interact with the new site, but this would require that the structure of the lists and libraries in the new site are the same as in the old site. - Do not create multiple sites with the same title as the title is used to create the category structure in K2 for SharePoint. Using the same title for multiple sites will group all artifacts for those sites together in one category. Ensure you use unique site titles.