Sum spent hours on project and tasks #
Customer is big Pharmaceutical company and they are using M-Files as a Project Management solution. They simplified structure have Projects, Tasks and Hour Logging Events, like in Picture 1.
Their Project Managers would like to know at each moment how much time is spent working on a project per each task, as those projects usually takes a bit long. They have configured Calculated properties in two ways:
- Have information on a Project about all hours spent on Tasks
- Have information on a Task about all hours spent
Configuration of Property calculations #
In Picture 2 we can see hierarchy of objects. In M-Files that hierarchy looks like in Picture 3. To configure Extended property calculations, we must be aware of that hierarchy or Parent-Child relationship. In customer cases:
- Project is parent and Task is child
- Task is parent and Hour Logging Event is child
Sum spent hours on a task #
We will create first rule for summing all hour logging events on tasks. Configuration is shown on Picture 5. We would like that summarizing happen when object is changed (Hour logging event). Parent object is Task and property on task object is Total work (h).
Children objects are Hour Logging Events (Picture 6) and they have connection to a Task. That’s why Relationship model is from ChildrenToParent and property that connect them is Task (Picture 7).
Property that we want to sum its Logged Work (h) from Hour logging events. Function that we are using its SUM (Picture 8).
In this case when we add new hour logging event it will be summed and added to related Task object (Picture 9).
Sum spent hours on a project #
The way to sum all spent hours per project (Picture 10) is same as for Tasks expect now Parent is Project and Children are Tasks.
Property that connect Tasks and Project is property Project on a Task object (Picture 11).
The results are seen on Picture 12, how all Total work (h) from Tasks are summarized to Project.
Count opened tasks on project #
Customer that is using M-Files as Project Management is counting opened tasks per project. Every task is going trough workflow and final state is Closed. In every moment Project Manager can see how many opened tickets they have on each project without opening views.
Count opened assignments per person #
Customer wanted to have information of how many opened tasks are per Person. That information was on a Person object. With customer we have tested different gamification and motivational methods and counting opened assignments was one of them that took effect in productivity.
Count opened tickets per customer #
Customer is using M-Files as a ticketing system with help of M-Files Email Processor. They are counting how many opened tickets they have per customer and how many total ticket they have. To gain that quick information
