GIS Feature Synchronization

The GIS Feature Synchronization task synchronizes data between Infor Public Sector and your GIS. This task compares the two databases based on the mappings that you specify, identifies inconsistencies such as orphans and data mismatches, and updates records in either database as needed.

There are two types of synchronization runs, standard and continuation. A standard run is the basic type of run that you schedule in the Batch Manager. A continuation run is used for further processing of records that were processed in a previous run.

For a standard run, the task first creates a sync batch, which is the primary record that is used to track the synchronization process and report the results. The synchronization then proceeds in these stages:

ExportExternal: Using the GIS mappings that you specify, the task first exports records from the GIS database. The exported data is stored in the GISDATA table.
Note: A GIS mapping can optionally be configured to stop processing if the ExportExternal stage returns no data from the GIS.
ExportInternal: The task exports records from the Infor Public Sector database. This data is stored in the IPSDATA table.
Analyze: The data in the GISDATA and IPSDATA tables is compared, and sync audits are created according to the method that is configured for the GIS mapping. The analysis uses the values in the IDENTIFIER column in each table to match records between the two datasets. These identifiers are constructed based on the business keys that you define when you create a GIS mapping. For example, the business keys for an address mapping would include fields such as StreetNumber, StreetName, City, and so on. If all of these values match, then the two records represent the same address.
A GIS mapping can be configured to create sync audits for all records, to create sync audits only for records with errors, or not to create any sync audits.
Each sync audit analyzes a single pair of corresponding records and reports on the mapped fields, the condition, and the status. The condition indicates whether the records are in sync and what the discrepancy is if they aren't. For example, the condition might indicate that the data in one or more fields doesn't match.
If this is a report-only run, Analyze is the last stage.
Import: If this is not a report-only run, the task updates records in one or both databases. The direction in which data is synchronized depends on the GIS mapping. This stage creates a sync integration record for each update.
AdvancedProcessing: During this stage the task runs any after sync formulas that are defined in your GIS mappings.

Depending on the GIS mapping, the task may run the ExportExternal, ExportInternal, Analyze, and Import stages a second time after the initial import is complete. For example, your system may have workflow formulas that alter the records in Infor Public Sector after they're imported from the GIS. This means that the records are no longer in sync, so you can repeat the process to sync the changed fields back to the GIS.

A continuation run starts with an existing sync batch from a previous run. It then creates a new sync batch for just the audits that need to be synchronized. A continuation run doesn't include the ExportExternal, ExportInternal, and Analyze stages, because these were already completed during the standard run.

Setup

This table describes the Configuration Editor settings that affect this task:


Configuration	Comments
Hansen8 configuration	The Record Load Limit attribute on the MAXRECORDS node specifies the number of sync audits that the task will process at a time. This should be set to a maximum of 1000 for Oracle databases, and 2100 for SQL Server databases. Higher values can cause database errors when running the task.
MapDrawerProviders configuration	Configures GIS providers for use in Infor Public Sector. This is used to connect Infor Public Sector to your GIS. See "GIS" in the Infor Public Sector User and Administration Library for more information about providers.

This table describes the Infor Public Sector setup forms that are used to configure this task:


Form	Comments
Create GIS Mapping	Used to map records in the Infor Public Sector database to features in the GIS. There are two types of mappings: GIS mappings, which map records at the component level, and field mappings, which map data at the field level. When you add a GIS Feature Synchronization task in the Batch Manager you must specify one or more GIS mappings.

This table lists the database tables that store setup information for this task:


Table	Comments
GIS.FIELDSOURCEINFO	Stores field-level information about the GIS source.
GIS.SOURCEINFO	Stores information about the GIS source.
GIS.SYNCFIELDMAPPING	Stores field mappings.
GIS.SYNCMAPPING	Stores GIS mappings.

See "GIS" in the Infor Public Sector User and Administration Library for more information.

Invocation

A standard synchronization run can be scheduled or invoked manually through the Batch Manager, and it can also be invoked through the console.

This table describes each parameter for this task:


Form	Console	Description
Workflow Enabled	IsWorkflowEnabled (bool)	Indicates whether you want to run workflow formulas for the Infor Public Sector records processed in the synchronization run.
Report Only Run	IsReportOnlyRun (bool)	Select this option if you only want to generate sync audits. No records will be changed in either database.
GIS Mappings	MappingKeys (int[])	Select each mapping that you want to include in the synchronization.

A continuation run is created when you use Lookup Sync Audit or the Sync Batch InfoViewer to process sync audits.

Data output

This table lists the database tables in which this task adds or updates records:


Table	Comments
GIS.GISDATA	Holds the data exported from the GIS.
GIS.IPSDATA	Holds the data exported from the Infor Public Sector database.
GIS.SYNCAUDIT	Stores synchronization audits.
GIS.SYNCAUDITACTIVITY	Stores information about actions taken on a sync audit, such as creating or updating records.
GIS.SYNCBATCH	Stores synchronization batches.
GIS.SYNCBATCHMAPPINGSTAGE	Stores information about the individual stages within a sync batch.
GIS.SYNCINTEGRATION	Stores sync integration records.

This table lists the Infor Public Sector forms that you can use to review the results of this task:


Form	Comments
Lookup Sync Audit	Used to look up and process sync audits.
Lookup Sync Batch	Used to look up sync batches.
Lookup Sync Integration	Used to look up sync integrations.