Firmenänderung - Automatischer Prozess #122

New Issue

2023-10-12T09:37:54+02:00

wiese commented

2023-10-12 09:37:54 +02:00

(Migrated from gitlab.uniworx.de)

Wenn ein Benutzerdatensatz aktualisiert wird: Durch Anstoßung Postversand, manuelles Anstoßen oder Routine

~~Soll vor der Änderung geprüft werden, welche Ansprechpartner zu ändern sind.Ablauf_AP_Aktualisieren_.pdf~~

Es wurde folgender Ablauf implementiert, der auch im Wiki so dokumentiert ist:

flowchart TD;
  S([Update AVS Person Contact])
  S-->FU0[[★Upsert Firm with \n AVS Firm details]]
  FU0-->FU[/If new company:\n Notify FA/]
  FU-->CF{Firm changed?}  
  CF-->|No|UU
  CF-->|Yes|CA{"`Firm Address **or**
                Email unchanged?`"}  
  CA-->|Yes|SCS
  CA-->|No|CP{New Company Id\n == Primary Company Id}
  CP-->|Yes|NPS

  CP-->|No|CCS
  
  subgraph UserCompany
    SCS[Update User/CompanyId\n default association\n keeping parameters\n]
    SCE[If user was default\n company supervisor:\n Become default company\n supervisor in new company]
    SCS-->SCE
    
    NPS[Delete User/OldCompanyId\n default association]

    CCS[Update User/CompanyId\n default association\n resetting parameters,\n but keeping priority]
    CC1[/If user was default\n company supervisor:\n Notify FA /]
    CCS-->CC1
    
  end

  CC1-->CCE[If old Company Id\n == Primary Company Id\n ★Reset user postal preference]

  subgraph UserSupervision
    UKS[Keep all supervision unchanged;\n but user being company supervisor \nis associated with new  company]
    CC2[Reset company \n associated supervisors\n for this user]
    CC3[/If supervised user has\n no superviser any more:\n Notify FA /]    
    NP1[Delete all supervision\n associated with old company]        
    UU[[Ensure any AVS superior is supervisor to user.\n Inserts superior from LDAP, if possible]]
  end 

  SCE-->UKS-->UU
  NPS-->NP1-->UU
  CCE-->CC2-->CC3-->UU  
  UU-->UUE([★Update other \n user details])

Wenn ein Benutzerdatensatz aktualisiert wird: Durch Anstoßung Postversand, manuelles Anstoßen oder Routine ~~Soll vor der Änderung geprüft werden, welche Ansprechpartner zu ändern sind.[Ablauf_AP_Aktualisieren_.pdf](/uploads/151467d60913dcb823474ba0b36765a3/Ablauf_AP_Aktualisieren_.pdf)~~ Es wurde folgender Ablauf implementiert, der auch im [Wiki so dokumentiert](../../wikis/FRADrive-%C3%9Cbersicht/Schnittstellenbeschreibungen/AVS-VSM/AVS-User-Update-Prozedur) ist: ```mermaid flowchart TD; S([Update AVS Person Contact]) S-->FU0[[★Upsert Firm with \n AVS Firm details]] FU0-->FU[/If new company:\n Notify FA/] FU-->CF{Firm changed?} CF-->|No|UU CF-->|Yes|CA{"`Firm Address **or** Email unchanged?`"} CA-->|Yes|SCS CA-->|No|CP{New Company Id\n == Primary Company Id} CP-->|Yes|NPS CP-->|No|CCS subgraph UserCompany SCS[Update User/CompanyId\n default association\n keeping parameters\n] SCE[If user was default\n company supervisor:\n Become default company\n supervisor in new company] SCS-->SCE NPS[Delete User/OldCompanyId\n default association] CCS[Update User/CompanyId\n default association\n resetting parameters,\n but keeping priority] CC1[/If user was default\n company supervisor:\n Notify FA /] CCS-->CC1 end CC1-->CCE[If old Company Id\n == Primary Company Id\n ★Reset user postal preference] subgraph UserSupervision UKS[Keep all supervision unchanged;\n but user being company supervisor \nis associated with new company] CC2[Reset company \n associated supervisors\n for this user] CC3[/If supervised user has\n no superviser any more:\n Notify FA /] NP1[Delete all supervision\n associated with old company] UU[[Ensure any AVS superior is supervisor to user.\n Inserts superior from LDAP, if possible]] end SCE-->UKS-->UU NPS-->NP1-->UU CCE-->CC2-->CC3-->UU UU-->UUE([★Update other \n user details]) ```

wiese commented

2023-10-12 09:37:54 +02:00

(Migrated from gitlab.uniworx.de)

assigned to @jost

jost commented

2024-03-06 17:25:29 +01:00

(Migrated from gitlab.uniworx.de)

Löschen von Firmen AV Id 0 können tatsächlich gelöscht werden.

jost commented

2024-06-07 14:39:53 +02:00

(Migrated from gitlab.uniworx.de)

changed the description

jost (Migrated from gitlab.uniworx.de) closed this issue

2024-06-07 14:40:34 +02:00

jost commented

2024-06-07 14:43:42 +02:00

(Migrated from gitlab.uniworx.de)

changed the description

This repo is archived. You cannot comment on issues.

No Milestone

No project

No Assignees

1 Participants

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fraport/fradrive-old#122