Projectile Manual

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[3.6_project_portfolio_and_multi-project_management|{{|previous}}]] [[en:handbuch:handbuch|{{|Home}}]] [[3.8_report_generator|{{|next}}]]

====== 3.7 Support of the Processes – The Workflow Engine ======


The Workflow Engine by Projectile is based on OSWorkflow. With the help of the Workflow Engine, project-related main processes and assisting processes are on the side of the system. 

{{:en:handbuch:kapitel_1:bild1kapitel37.gif|}}

__Illustration 25: Abstimmung assisted by the Workflow Engine__

In the system, numerous workflows have already been pre-configurated, which can be adapted to the own requirements by the administrator accordingly. In the workflow files, settings can be made about which user should be notified of certain events or from whom an agreement is required. 

For many companies,  switching from one project status to the next is the central workflow of regulating the project process. After setting up a project, it is possibly cleared for planning and resources from other units of organisation applied for and offers drawn up and cleared. Finally, a project is usually cleared and completed. 

For the workflows, which are not project-related (checking time tracking, checking costs, applying for absence,...), workflows can likewise be configurated by the administrator. At the same time, the number of levels of agreement, recipients, agreement regulations and types of notification can be set up.