Winshuttle Composer Glossary of Terms
A single step or task in a workflow.
The And/Join node is used to evaluate Approval node dispositions and move on to the next step in a workflow based on the property setting of the Approval nodes.
The Approval node is a step within a workflow that requires the consent or decision of its assignees to proceed to the next step in the workflow.
A Decision node represents a branching point in a workflow--for example, when an approver must approve or reject a document.
Deployment Profiles allow you to set up different environments for publishing a solution. This makes deploying solutions across different environments easier.
Default profiles include Default, Development, Staging, and Production. You can create as many Deployment Profiles as you require.
An End node is used as a visual reference in a workflow to indicate where it ends. An End node is required to conclude a process or subprocess (loop).
Loop Block node
The Loop Block node allows you to integrate subprocesses within a main workflow.
A node is a single step in a workflow. For example, a node could represent a task assigned to a user, or an action, such as sending a notification or setting of a value. Think of nodes as the 'building blocks' of a workflow.
A Notification node is used to send email notification(s) to individuals participating in a workflow--for example, when an document is approved the author might be sent an email to notify them of approval.
The Originator is the person who initiates a workflow. Every workflow must have an Originator Swim Lane.
The Participant Resolver feature allows you to configure how participants in a workflow are assigned.
The plugin node is used to automate tasks in a workflow, such as:
- Copy a form or document to another location.
- Interface with a Web service.
- Design, add, or integrate your own functionality into a process.
A process—also sometimes called a solution—contains all the items that are necessary for a workflow to function. This can include the workflow itself, documents, forms, and other supporting structures and definitions.
The Process Owner is the person responsible for all processes in a specified group. By default, the Originator (see above) is the Process Owner, but you can assign a different Process Owner as needed. Every workflow must have a Process Owner.
A SharePoint List is a container for data used by workflows. A SharePoint List may contain a list of usernames, materials, documents, etc.
The Start node is used as a visual reference in a workflow to indicate where it begins. A Start node is required to initiate a process.
A Swim Lane is a functional role within a workflow. For example, a Swim Lane could represent a functional manager role, a QA role, or a team role.
This sample workflow has 2 Swim Lanes: One for the process Originator, and one for the approving Manager.
A transition is the movement from one workflow node to another. Click a node, and then drag to draw a transition from the node to another node.
A Node is a single step in a workflow. For example, a node could represent a task assigned to a user, or an action, such as sending a notification or setting of a value. Think of Nodes as the 'building blocks' of a Workflow.
Value Setter node
The Value Setter node allows you to set values in a form field or list column. This functionality can be used to manipulate a workflow route, based on the setting of values in a form field or list column.
A Web service is any form of communication or interoperability (service) between systems through an internal network (intranet) or the World Wide Web (internet).
A workflow is a graphical representation of the flow of information (documents and/or forms) through an enterprise.
Above: A very basic workflow example.
The Xor/Join node is used to evaluate Approval node dispositions and move on to the next step in a workflow based on the property setting of the Approval nodes.