This is an Esri functionality for versions. Because a version can be reconciled and posted, when the reconcile is done, there could be a conflict and you can decide if this conflict should be resolved automatically or not by using the parameters below.
Parameter |
Value |
|---|---|
postserver.reconcile.automatic.mode |
When processing a job, the following operations are performed on the associated version: No action: Reconcile and Post are not executed Reconcile: Reconcile is executed, no Post Reconcile + Post: Reconcile and Post are executed [default: Reconcile+Post] |
postserver.reconcile.conflict.handling |
If a conflict occurs during the Reconcile of a version, here can be defined how the conflict is handled. The following operations are available: •Reconcile Error: when a conflict occurs, the Reconcile process is stopped and an error message is stored in the log table. •Child version wins: if a conflict occurs during the Reconcile process, this conflict will be resolved automatically. Therefore, the changes in the parent version (e.g. SDE.DEFAULT) are overwritten with the child version changes. [default: Reconcile Error] |
postserver.reconcile.conflict.level |
With these options is defined, on which level conflicts of a Reconcile are detected: •Column level: Individual table fields are checked for conflicts. •Row level: Complete table rows are checked for conflicts. [default: Row Level] |
Check network validation before post |
Possible values: true|false true false [default: false] |
Validate network after post |
Possible values: true|false true false [default: false] |