Reconciles/posts the version of a VertiGIS Networks Job against the SDE.DEFAULT default version. This task processes all the VertiGIS Integrator Cron Jobs that are in the ready to process state.
The Esri mechanism of editing in version implies that before doing a post to the default branch, a reconcile is required. Using the reconcile, the VertiGIS Integrator will read all the differences from the default version posted after the Cron Job has been generated and will update the branch version with the changes from the default version. Using post, the VertiGIS Integrator will write back all the changes from the branch version to the default version.

This Cron Job supports the following additional parameters:
Parameter |
Value |
Required |
|---|---|---|
Duration (min.) |
Time duration of the interval in minutes (VertiGIS Networks Jobs will be processed only within the specified time interval). If this value is empty, all the VertiGIS Networks Jobs in the ready-to-process state will be processed. |
|
Target Service Endpoint |
Name of the feature service endpoint used to send data to the external system. Unless otherwise specified, the operation applies to all feature service endpoints including VertiGIS networks endpoints. |
|
Parameter |
A JSON string containing properties that take precedence over those defined in the global settings page •check_network_validation_before_post: true/false •validate_network_after_post: true/false •abort_if_conflict: true/false •conflict_detection: "byAttribute"/"byObject". obyAttribute: Column level obyObject: Row level •reconcile_retry_count: integer oIf not explicitly specified in this JSON string, the value defined for postserver.reconcile.retry.count in the properties.xml configuration file will be used. odefault is 0 •reconcile_retry_wait_seconds: integer oIf not explicitly specified in this JSON string, the value defined for postserver.reconcile.retry.wait_time in the properties.xml configuration file will be used. •reconcile_conflict_as_protocol_info: true/false oLog reconcile conflicts as informational messages rather than errors in the scheduled task protocol to prevent unnecessary failure flags and ensure smoother automation monitoring. Example: { "reconcile_conflict_as_protocol_info": false, "check_network_validation_before_post": true, "validate_network_after_post": true, "abort_if_conflict": true, "conflict_detection": "byAttribute", "reconcile_retry_count": 1, "reconcile_retry_wait_seconds": 3 } |
|