Proceedings and interested parties
To sync the proceedings and interested parties from Winzolventz to our database (search index) there are a few steps to be done (assistance from development team is needed):
Stop the
STP winsolvenz.p4 FLOW Connectorservice in the on-premise machineDelete the two files holding information about the last synchronization located in
\ProgramData\STP AG\winsolvenz.FLOW.Connector:Delete the indices in the IM server (this step is made by a member of the IM development team)
Note: this step can be done before the others step
Start the
STP winsolvenz.p4 FLOW Connectorservice
Note:
The way proceedings
and interested parties are synchronized with the cloud vastly differs.
The number of proceedings rarely reaches the 6-digit threshold, even for
large law firms. The manner in which they are persisted is also rather
simple, thus making the process a lot easier and faster. Modified
proceedings will reach the cloud in a few minutes.
On the contrary interested parties are a very complex construct and, for large law firms, they easily number somewhere in the 7-digits range. Thus the synchronization requires the Winsolvenz Server to prepare the data for modified interested parties and only then can the STP winsolvenz.p4 FLOW Connector pick up those prepared data packages and upload them. For this reason it takes significantly longer for updated interested parties to be available.
Containers
To sync the containers (folders and dossiers) from DMS to our database (search index) there are a few steps to be done (assistance from development team is needed):
Stop the
STP LEXolution Connectservice in the on-premise machineDelete the two files holding information about the last synchronization located in
\ProgramData\STP AG\STP.LEXolution.Connect:Delete the indices in the IM server (this step is made by a member of the IM development team)
Note: this step can be done before the others step
Start the
STP LEXolution Connectservice
Related to