Define approving/approval procedures for each type of absence
J
Jan Holländer
projo offers extensive options for defining the approver for absences.
Here we use the function “if defines fixed teams, otherwise project teams” with the addition “use fallback approvers”.
We're doing pretty well with that.
However, we think it makes sense to always send certain types of absences to a specific person. These could include, for example, illness or even period of education as examples.
It would be great if projo could set this as an additional setting for each absence.
3 states could then be defined here:
• Use basic settings
• Override default setting and define A specific approver
• Use basic settings and name ONE specific approver as the second necessary approver
I understand that the function can be quite complex, as it may be different/depending on the selected default setting. It could therefore be useful that it could be useful to “give up” the basic setting and define the type of approval process absence-type-specific as a characteristic in the settings of the respective absence.
Or you choose in the basic settings whether you want to activate individual approval procedures for each absence.
It would therefore remain unchanged for everyone who is satisfied with the current process.
VG! Jan
S
Simon Winkler
Hi Jan,
With dynamic project teams, a large number of projects and from time to time an inconsistency in the settings (= instead of sending to the standard fallback representative, projo does not send a notification from time to time) that it turns one or two rounds until the right person presses the button. The idea is therefore very good :-)
W
Wenzel, Ronny
Yes, we also have the problem.
With the help of an Outlook rule, we are currently building a workaround with regard to the sick report, so that the generated e-mail, which is sent to the defined manager, is automatically forwarded to our central sick e-mail.
I know from Personio that there are role groups that can be individually integrated when building a workflow.
In my opinion, it shouldn't be too complicated to make workflows more flexible via person IDs, their associated email and role (group) assignment.