Setting trigger conditions is a key step in the automation creation process. For a complete overview of all the steps, refer to What's in an automation?.
The automation source is what ultimately defines the outcome provisioned by your automation. It's the core component that tells your automation exactly what to provision and how to customize it. When you combine a robust template with accurate data source information, you can provision a comprehensive site with significantly reduced effort and time. Understanding these steps, which are dependent on your specific data source, is key to successful automation.
Provisioning source
The provisioning source defines what your automation provisions and how it's customized. It involves three key steps:
Note: In the context of an automation's provisioning source, the Data Source refers to the connection point where end-user requests are stored. This is where the automation pulls dynamic data for provisioning and customization.
Template Selection
In the Template Selection step, administrators define which templates will be provisioned by the automation. This is also where you specify where products will be installed, choosing between your entire Tenant or a specific Site collection. This step ensures your automation always provisions the correct template in the right location.
Need help with template creation? Check our best practices in template creation in our article on understanding templates
Source Configuration
The Source Configuration section allows you to map fields from your chosen data source to set up crucial site configurations. Here, you can dynamically define elements like the site name and description. For membership, you have the flexibility to map a field from your data source or predefine specific people or groups to be included. This ensures each provisioned site is tailored with essential details automatically.
Data Mapping
The Data Mapping section is where you connect dynamic content from your data sources with your templates. This powerful feature allows tokens within your templates to be automatically replaced with relevant information based on the end-user's request or the data source's content. This ensures a personalized and contextually accurate site provisioning experience without manual intervention.
