The most recent version of FLOWer (3.5) was released at the end of 2005. Years of working with FLOWer by customers and Pallas Athena engineers has influenced the development of FLOWer 3.5. The FLOWer Suite now consists of a number of complementary components. Below is a brief overview of the components. For more detailed information please select each item from the menu on the left.
The Components of the FLOWer Suite
FLOWer Client/ServerFLOWer 3.5 is a modern client/server application. The server is available on many different platforms. The default client shipped with the product is created in Java and enables you to deploy FLOWer as a complete case handling system in the minimum of time. The client not only gives you the ability to see a summary of each job using the case overview but also allows you to search for jobs and distribute the work in different queues. A unique feature of FLOWer is that you can see the full case summary at any time, even if that particular case is not in your work tray.
FLOWer Configuration Manager
You use FLOWer Configuration Manager to input organisation structures, branches, departments, teams and employees. You then assign the appropriate authorisation levels to each person. This ensures that people only see the work which is relevant to them. Configuration Manager is held separately from the process development, this means a Systems Administrator can change the users and authorisation levels quickly and without affecting the process flow.
FLOWer Studio
FLOWer Studio is an integrated development environment where you define and manage the processes, role structure, forms and integration with other applications. Studio is configured using drag and drop techniques.
FLOWer Teamwork
FLOWer Teamwork supports team leaders during their activities and allows them to carry out part of the FLOWer management independently without the need for support from ICT.