This checklist summarizes the key validation tasks performed during setup and testing of the CivicPlus Asset Management GIS Sync integration. It may also be used by customer GIS coordinators to verify that their feature services and Asset Management configuration are ready for synchronization.
Pre-Integration Verification
Validation Step | Purpose or Expected Result |
|---|---|
Confirm Esri feature services are published and accessible through REST (Representational State Transfer) | Verify that each service URL is reachable. The CivicPlus integration will authenticate using a token even if the feature service itself allows anonymous access. |
Verify the GlobalID field exists and is populated on all synchronized layers | Ensures reliable feature-level linkage across systems. |
Confirm required attributes, such as GlobalID and EditedDate, exist | Enables ExtractChanges and ApplyEdits operations. |
Validate that ChangeTracking or Sync capability is enabled | Confirms the service supports delta retrieval and serverGen tracking. |
Confirm integration user account permissions if using secured services or advanced workflows | Integration user has appropriate access, such as Sync or Edit, as required. |
Validate layer schema against Asset Management mapping | Prevents field-type or name mismatches before initial sync. |
Confirm feature service ownership (Hosted versus Registered) | Determines the correct token URL and change-tracking method. |
Deletion and Bi-Directional Validation (if applicable)
Validation Step | Purpose or Expected Result |
|---|---|
Delete the test record in GIS | The record is removed from Asset Management after the next ExtrachChanges cycle. |
Insert or edit a test record in Asset Management | Change appears in the GIS layer after ApplyEdits. |
Validate editor tracking fields | EditedBy and EditedDate correctly reflect the integration user. |
Confirm serverGen increments correctly | Confirms incremental change tracking is functioning. |
Review log.RecordAudit for expected entries | Confirms two-way event logging integrity. |
Post-Integration Monitoring
Validation Step | Purpose or Expected Result |
|---|---|
Schedule recurring validation review | Ongoing comparison of feature counts and update timestamps. |
Monitor integration logs for errors | Identify failed sync attempts or schema drift early. |
Validate ongoing token renewal | Ensures uninterrupted access to Esri REST (Representational State Transfer) endpoints. |
Review the change-tracking window | Confirms ExtractChanges is polling within the expected date range. |