Note: These articles are intended to showcase examples of Orchestry's Custom Feature option. From a product support standpoint, we do not assist in creating or debugging Custom Features.
Getting Started
Before creating a custom feature, definitely check out our more introductory articles on:
Feature Proposal
Have you wondered if you can provision some custom security options to your SharePoint site via Orchestry? Currently we do not provision broken inheritance models from the source SharePoint site to the destination, however, you can use PnP provisioning and create an Orchestry Feature to customize the SP Site Permissions instead.
Here are two examples, one using a hardcoded (Static) Permission Group Name, and another with a name like {groupsitetitle} Designers.
Testing the Feature
Sometimes it can be much easier to do away with the entire PnP package I did away with the entire PnP Package file. I don't believe it's required for what we are trying to do. Instead, I simply used the extracted XML file under <extract>/Files.
Likely you will want to update the XML to simplify it as much as possible and re-save it, here's an example:
Next, upload only the XML into the Orchestry Template Files. Here are the two of ours:
One useful trick to test your XML file, before you deploy it as a feature, is to use the green 'beaker' icon to launch as a test against an existing site in the environment. This is a much faster way to test the file is working.
Next, connect each of these to a feature to be able to attach them to a Template:
Here is an example of a request with the feature added:
This is the resulting Team Site with the custom Group (and members) created:
