Recommended Winshuttle workflow solution architecture
Winshuttle Workflow supports SharePoint’s distributed architecture where solutions are deployed in the local sites where they are accessed by users. Described below are recommended solution architectures for small and large deployments.
Understanding winshuttle workflow solution architecture
The image below describes a general overview of Winshuttle products and how they interact in an environment.
General architecture recommendations
For small deployments where all processes are used by only one team or department, it is recommend keeping all processes on one single site. This site should be based on the Winshuttle provided site template which by default includes the three Workflow web parts: Form Library, Task List and Process List.
Multiple Sites with strict separation
For larger deployments where Winshuttle Workflow is used to automate processes for a number of different teams or departments and strict separation is required, it is recommended to create separate SharePoint site collections for each grouping. In this model, no content is shared between site collections and security configuration is also strictly separated.
Multiple Sites with aggregation
For larger deployments where Winshuttle Workflow is used to automate processes for a number of different teams or departments and there is a need for an aggregated high-level view of tasks and processes, it is recommended to use one SharePoint site collection with multiple sub sites. Each functional team or department will have a separate sub site, ensuring separation of content.
On the top-level site, the Task List and Process List web parts can be configured to display tasks and processes from all sub sites, providing administrators and super users with an aggregated view of current processes. The top-level site can also be the place to create any supporting lists that are shared between processes in different sub sites. E.g. lists with shared reference data or variables used in business rules.