Episode I: Welcome to the Workflow
We couldn't wait any longer to begin this series and unanimously decided that the first episode had a two fold purpose. We certainly wanted to announce the beginning of the series and we felt that we needed to start with a brief introduction to the workflow.
Teaming enables users to send work entries and data through an organizational process called a workflow. These processes are often unique to every organization. We've created some common workflows and posted them to our Teaming Library. Feel free to take a look, but keep coming back for new episodes in this series. We really want this to be a positive learning experience.
How Work Flows
The Teaming workflow process isn't foreign to your current real-life work process. Let's look at real world example:
A new position opens in the Marketing Department. You place an ad and require that all applicants fill out an application as well as submit a current resume. For most businesses, an applicant either e-mails or delivers an application to be reviewed by HR to ensure that the applicant meets the qualifications for the position. HR might consult the department manager/head to ensure a fit. Eventually the applicant is either rejected or accepted, and finally you must contact the applicant with the results of the process.
For most businesses, there are many opportunities for information to be misplaced, mistreated, neglected, or even lost. Teaming manages each of these steps as states of the workflow. Each movement transition between the states is also controlled. Teaming can also notify each person every step of the way as needed.. Lets map out this process:
Figure 1: How Work Flows
Click to View
Teaming workflows automate the natural flow of tasks in real life, so you can move through the process without stopping to search for missing information.
If you want to simulate a process within Teaming, first take some time to draw up a work process like the one in the illustration. You can use whatever graphics you like. Remember that the different steps in a work flow are called states, and that there's a transition between each state. Before you know it, you're on the way to develop custom workflows within Novell Teaming.
We hope that this introduction to workflows has been helpful. Please stop by next week to see how to begin building the workflow in Episode II: The Workflow from Concept to Construction.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.