Update AVS User Update Prozedur
parent
3ebc2f4ceb
commit
c5d9a20e2e
@ -97,15 +97,16 @@ flowchart TD;
|
||||
- Superiors become irregular supervisors without rerouting, existing supervisions are not changed
|
||||
- Superiors become company users at equal-to-max priority, if not already
|
||||
* For each AVN User update:
|
||||
- if superior change for unchanged company:
|
||||
all company supervisions with remark "Vorgesetzter" are removed
|
||||
- all company associates are irregularly supervised by the new superior with remark "Vorgesetzer"
|
||||
- if superior changed for an unchanged company:
|
||||
all company supervisions with remark "Vorgesetzter" are removed before executing the previous step, also
|
||||
create admin problem that notifies about superior change
|
||||
(special if new superior could not be created)
|
||||
- all company associates are irregularly supervised by the new superior with remark "Vorgesetzer"
|
||||
* Open Questions:
|
||||
- company had superior, but no longer: just remove superior-supervisions, do not report admin problem?
|
||||
- Problem: superior changed, but we first encounter this through a user changing company.
|
||||
Change is not detected at this point, old superiors remain until an old company associate is updated too
|
||||
- from 2025 onwards (when DB is sufficently up-to-date): skip both steps if company and supervisor are unchanged from previous AVS query
|
||||
* Possible problem / Questions:
|
||||
- company had superior, but no longer: ok to just remove superior-supervisions and report admin problem?
|
||||
- Problem: superior changed, but we first encounter this through a user also changing company.
|
||||
Company-wide-change might not be the case, thus old superiors remain until an old company associate is updated too!
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user