In many cases, an employee in an enterprise may belong to both Department A and department B. In department A, an employee may assume one role and another role in department B, this kind of organizational structure violates the basic requirements of the tree, but it actually exists a lot.
Requirements for some matters [section chiefs]
For some cases, [persons from Department A]
Requirements for some matters [Section Head of Department A]
For some matters, [department A's section chief or above]
Therefore, I added the concept of a work domain when handling the case.
When dealing with a matter, anyone asks "to identify", that is, "Who is the matter, in [that department], and [what function] has done [what kind of behavior]"
Algorithm
All |
Department No. = "all" & function no. = "all" & personnel no. = "all" |
Designated person |
Personnel id = person |
Department owner |
Department No. = Department & function no. = "all" & personnel no. = "all" |
Function owner |
Department No. = "all" & function no. = Function & personnel no. = "all" |
Department function owner |
Department No. = Department & function no. = Function & personnel no. = "all" |
Class Structure
Work domain Loading
Simulate the UI