How to troubleshoot "a problem with the BPM Import organization architecture that prevents the system from logging in"

Encounter Problems ↓

Enter the H3 system landing page.

Click Login to display the error.

After tracing, the display parameter is empty.

Problem Description: The organization import through the Web service way, only imports the common 6 fields such as Objectid and name.
After successful import, the background only displays the department, unable to display the personnel, when the integration engine restarts, then cannot log in, the above problem occurs.

The problem occurs because the Objectid field in the System Department table "Ot_organizationunit" and the user table "Ot_user" must be 36-bit,
The reason for this problem is that the BPM system uses the Objectid of other systems when the corresponding department and the Objectid in the user table.

Reference workaround: If the other system objectid less than 36 bits, the way to add a string is not aligned,
If the two systems still have other interfaces that require this parameter as a unique identifier, you can contract in advance to increase the number of characters you want.

Example: Because the Objectid passed by other systems are numbered endings, the other system calls the BPM interface to stitch the string "X"
The BPM system intercepts "X" when invoking other system callbacks, or it can contract other systems to invoke the BPM interface when the original Objectid
Store to another field in the Department or user table (such as code, etc.).

How to troubleshoot "a problem with the BPM Import organization architecture that prevents the system from logging in"