From 42ef3713c243fffb27e3ed9d9cec46baa841c0e0 Mon Sep 17 00:00:00 2001 From: Steffen Jost Date: Thu, 5 Sep 2024 15:51:49 +0000 Subject: [PATCH] Update AVS User Update Prozedur --- .../AVS-VSM/AVS-User-Update-Prozedur.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/FRADrive-Übersicht/Schnittstellenbeschreibungen/AVS-VSM/AVS-User-Update-Prozedur.md b/FRADrive-Übersicht/Schnittstellenbeschreibungen/AVS-VSM/AVS-User-Update-Prozedur.md index e1de53a..db57476 100644 --- a/FRADrive-Übersicht/Schnittstellenbeschreibungen/AVS-VSM/AVS-User-Update-Prozedur.md +++ b/FRADrive-Übersicht/Schnittstellenbeschreibungen/AVS-VSM/AVS-User-Update-Prozedur.md @@ -97,11 +97,12 @@ 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: - - all company associates are irregularly supervised by the new superior with remark "Vorgesetzer" + - _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) + - if company changed: delete ordinary superiror-only supervision for given user only - 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?