This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:handbuch:kapitel_3:3.09_workflow-modul [2009/12/03 16:56] admin |
en:handbuch:kapitel_3:3.09_workflow-modul [2019/10/25 14:11] (current) |
||
---|---|---|---|
Line 3: | Line 3: | ||
====== 3.09 Workflow-Module ====== | ====== 3.09 Workflow-Module ====== | ||
- | The workflow engine enables illustrating work processes within Projectile. Unlike a business process that describes a sequence of activities with the objective of service performance, a workflow is a predefined sequence of computer-aided flow of activities. The workflow engine in Projectile supports a business process, provided with necessary data and processes, according to the specifications stored in the system. The goal here is not a documentation for an organization or its employees, but rather the ability to automate the process. | + | The workflow engine enables illustrating work processes within Projectile. Unlike a business process that describes a sequence of activities with the objective of service performance, a workflow is a predefined sequence of computer-aided flow of activities. The workflow engine in Projectile supports a business process, provided with necessary data and processes, according to the specifications stored in the system. The goal here is not a documentation for an organization or its employees, but rather the ability to automate the process. |
Projectile's workflow engine is based on OSWorkflow from OpenSymphony and is part of the standard version. | Projectile's workflow engine is based on OSWorkflow from OpenSymphony and is part of the standard version. | ||
Line 11: | Line 11: | ||
In TimeTracker various workflows for the handling time periods (period-end closing, vacation application, ...) can be stored. The following example shows the implementation of a holiday application. After performing the action in the Time Tracker ... | In TimeTracker various workflows for the handling time periods (period-end closing, vacation application, ...) can be stored. The following example shows the implementation of a holiday application. After performing the action in the Time Tracker ... | ||
- | {{:handbuch:kapitel_3:tutorial:234.gif?direct}} | + | {{:en:handbuch:kapitel_5:apply_for_holiday.gif|}} |
... a dialog for absence application is opened. Here the user can apply for absences (overtime compensation, recreation and special vacation) and cancel absences applied for or cancel approved absences. | ... a dialog for absence application is opened. Here the user can apply for absences (overtime compensation, recreation and special vacation) and cancel absences applied for or cancel approved absences. | ||
- | {{:handbuch:kapitel_3:tutorial:235.gif?direct}} | + | {{:en:handbuch:kapitel_5:apply_application.gif|}} |
In the following example the employee has applied for vacation. | In the following example the employee has applied for vacation. | ||
- | {{:handbuch:kapitel_3:tutorial:236.gif?direct}} | + | {{:en:handbuch:kapitel_5:apply.gif|}} |
After confirming the application ... | After confirming the application ... | ||
- | {{:handbuch:kapitel_3:tutorial:237.gif?direct}} | + | {{:en:handbuch:kapitel_5:please_confirm.gif|}} |
... the applied for vacation is then visualized ... | ... the applied for vacation is then visualized ... | ||
- | {{:handbuch:kapitel_3:tutorial:238.gif?direct}} | + | {{:en:handbuch:kapitel_5:appliedfor1.gif|}} |
and the supervisor (manager, personnel manager, project manager or unit manager) receives an internal message. In the example, the unit manager of the applicant ... | and the supervisor (manager, personnel manager, project manager or unit manager) receives an internal message. In the example, the unit manager of the applicant ... | ||
- | {{:handbuch:kapitel_3:tutorial:239.gif?direct}} | + | {{:en:handbuch:kapitel_5:login_george.gif|}} |
... is informed and receives a vote. | ... is informed and receives a vote. | ||
- | {{:handbuch:kapitel_3:tutorial:240.gif?direct}} | + | {{:en:handbuch:kapitel_3:absences_mail1.jpg|}} |
The employee is then informed of the vote through an internal message. | The employee is then informed of the vote through an internal message. | ||
+ | {{:en:handbuch:kapitel_3:absences_mail2.jpg|}} | ||
- | {{:handbuch:kapitel_3:tutorial:241.gif?direct}} | + | In the workflow engine the holiday can either be ... |
- | In the workflow engine a the holiday can either be ... | + | {{:en:handbuch:kapitel_3:ballots1_chapt3.jpg|}} |
- | + | ||
- | In der Workflow-Engine kann im Menüpunkt Abstimmung ... | + | |
- | + | ||
- | {{:handbuch:kapitel_3:tutorial:242.gif}} | + | |
accepted or denied in the menu item "Ballot". | accepted or denied in the menu item "Ballot". | ||
- | {{:handbuch:kapitel_3:tutorial:243.gif?direct}} | + | {{:en:handbuch:kapitel_3:vote1.gif|}} |
The applicant obtains a message of the vote from the system. | The applicant obtains a message of the vote from the system. | ||
- | {{:handbuch:kapitel_3:tutorial:245.gif?direct}} | + | {{:en:handbuch:kapitel_3:absences_mail3.jpg|}} |
Depending on the voting results, the holiday is graphically displayed as vacation or as vacation rejected in the absence application of the Time Tracker. | Depending on the voting results, the holiday is graphically displayed as vacation or as vacation rejected in the absence application of the Time Tracker. | ||
- | {{:handbuch:kapitel_3:tutorial:246.gif?direct}} | + | {{:en:handbuch:kapitel_5:application2.gif|}} |