This article describes how data is integrated between nSPECT and nCORE.

Configuring Evaluation Inspection Types

The nCORE "Evaluation Type" and the nSPECT "Inspection Type" drive the initial data integration between the two systems. Inspections are scheduled in nSPECT via the Evaluation Type provided by nCORE. 

When a new Evaluation Type is added to nCORE, a new Inspection Type will be added to nSpect when the user clicks the checkbox "Enable nSPECT Integration" and saves the record:

Once the "Enable nSPECT Integration" checkbox is clicked, a number of additional settings are displayed, as shown in the image above:

1. Set Inspection Report to "Final" Status when nSpect Inspection is Completed - the Inspection Report Document will be set to "Final" status in nCORE automatically
2. nSPECT Inspection Report File Type - Can be set to "docx" or "pdf". Default file type is set in APP_DEPLOY_SETTING where CODE = 'NSPECT_RPT_EXT'
3. Default Followup Evaluation Type -  If an Inspection Form in nSPECT is configured to schedule a followup evaluation, it will be created with the type specified. If no type is specified, the followup will be created as the same type as the current inspection. See section Outbound Tags for more information on configuring Followup Evaluations.

Configuring Integration Tags in nSPECT

Integration tags are configured on nSPECT questions, and can be used to pass data from nCORE into nSPECT (CME Prefill), and from nSPECT to nCORE to perform various actions. There are four flavors of data transfer:

1. Prefilling nSPECT Forms with CME data from nCORE using Data Integration Tags
2. Updating nCORE data and performing actions using Data Integration Tags
3. Populating the nCORE "Inspection Results" tab using the Data Integration Context
4. Creating Violations in nCORE using the Regulation Reference

Inbound: nCORE Evaluations to nSPECT

Data can be prefilled into nSPECT forms using nCORE data. Data elements are defined in the nSpectImport.CME_INSPECTION_% database views:

1. nSpectImport.CME_INSPECTION_MASTER - base view required for Prefill, defines any non-repeating data elements
2. nSpectImport.CME_INSPECTION_EVAL_CONTCT - prefills repeating contact sections. Pulls all contacts related to the source evaluation (EVAL) record
3. nSpectImport.CME_INSPECTION_PRMT_FEATR - prefills repeating feature sections using features referenced on the source permit. Useful for sampling inspections

Additional repeating or custom views can be developed on client request.

See below for tag definitions for each of the above views:

nSpectImport.CME_INSPECTION_MASTER (non-repeating data)

nSpectImport.CME_INSPECTION_EVAL_CONTCT (repeating data)

nSpectImport.CME_INSPECTION_PRMT_CONTCT (repeating data)

Pulls any contacts related to parent Permit record and populates data into a repeating nSPECT section

nSpectImport.CME_INSPECTION_PRMT_FEATR (repeating data)

These tags populate features for the permit specified in the evaluation record.

Outbound: nSPECT Inspections to nCORE Evaluations

Data integration tags can also be used to populate data in nCORE, and perform various actions. See below for configured tags and integration descriptions:

nCORE Evaluation Results from nSPECT 

Entering "AREA" into the "Data Integration Context" field in an nSPECT inspection question causes the question and response to display in the nCORE evaluation record's Inspection Results tab.

Syncing nSPECT Violations to nCORE

Questions marked as Violations in nSPECT can be configured to create violation records in nCORE, but must be configured to do so.

1. In nSPECT, edit the form question that should result in a violation
2. In the Reference / Citation field, enter a unique value for the violation reference. This value will be used in the next section to map to an nCORE Violation Type/Category
3. Ensure that the radio button is selected that indicates the user is allowed to mark the inspection as a violation
4. Click Save at the top of the screen to ensure the changes are saved.
5. Navigate to the nCORE Admin → Lookups → Violation Types to Categories screen
   
6. Either create a new Violation Type to Category Association or edit an existing Violation Type to Category Association that the violation will map to.
7. In the nSPECT Data Integration Tag field, enter the same value as entered in step 2 above.
   
8. Click Save to save the changes.

Note that after saving, beneath the nSPECT Data Integration Tag field, a message will indicate whether the mapping is successful or not by display either one of the following messages:

• "No nSPECT questions use this integration tag", or
• "Integration tag exists in nSPECT"

Technical Aspects if nSPECT to nCORE integration

Steps performed for integration:

1. On a regular interval, nCORE invokes the Integration - Process Completed nSpect Inspections scheduled task. WSL invokes an nSPECT web service to fetch any completed inspections. If found, the data is staged to EVAL_NSPECT_SUB and EVAL_NSPECT_SUB_DTL staging tables.
2. Stored procedure SP_IMPORT_NSPECT_DATA is then invoked to move data from the staging tables back to nCORE, including creation of violations.
3. On a separate schedule, nCORE invokes the Integration - Import nSPECT Submission Files scheduled task. This process copies any new inspection report PDFs from nSPECT into nCORE. Documents are staged in NSPECT_EVAL_FILE_PRCSS. Once the task copies the documents to nCORE, procedure SP_ADD_NSPECT_REQST_FILE performs finalization tasks, such as removing the record from the staging table and setting document statuses to "Final".