This article describes how data is integrated between nSPECT and nCORE.
Configuring 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:
- Set Inspection Report to "Final" Status when nSpect Inspection is Completed - the Inspection Report Document will be set to "Final" status in nCORE automatically
- 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'
- 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:
- Prefilling nSPECT Forms with CME data from nCORE using Data Integration Tags
- Updating nCORE data and performing actions using Data Integration Tags
- Populating the nCORE "Inspection Results" tab using the Data Integration Context
- Creating Violations in nCORE using the Regulation Reference
Inbound to nSpect
Data can be prefilled into nSPECT forms using nCORE data. Data elements are defined in the nSpectImport.CME_INSPECTION_% database views:
- nSpectImport.CME_INSPECTION_MASTER - base view required for Prefill, defines any non-repeating data elements
- nSpectImport.CME_INSPECTION_EVAL_CONTCT - prefills repeating contact sections. Pulls all contacts related to the source evaluation (EVAL) record
- 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)
| nSPECT Data Integration Tag | nCORE Database Field Name | Comments |
|---|---|---|
| SITE_SITE_NAME | SITE.SITE_NAME | Site Name, non-standard tag as SITE_NAME is reserved by nSpect |
| SITE_ADDR | SITE.ADDR_1, SITE.ADDR_2, SITE.CITY, SITE.REF_STATE_CODE, SITE.ZIP_CODE | Concatenated Site Address fields |
| SITE_ADDR_1 | SITE.ADDR_1 | |
| SITE_ADDR_2 | S.ADDR_2 | |
| SITE_CITY | SITE.CITY | |
| SITE_STATE | SITE.REF_STATE_CODE | |
| SITE_ZIP_CODE | SITE.ZIP_CODE | |
| SITE_CNTY | REF_CNTY.DESCR | |
| EVAL_NUM | EVAL.EVAL_NUM | |
| PRMT_NUM | PRMT.PRMT_NUM | Permit information is pulled from corresponding EVAL.PRMT_ID record |
| PRMT_VERSN | PRMT.PRMT_VERSN | |
| REF_PRMT_CATG_DESCR | REF_PRMT_CATG.DESCR | |
| REF_PRMT_STAT_DESCR | REF_PRMT_STAT.DESCR | |
| REF_PRMT_TYPE_DESCR | REF_PRMT_TYPE.DESCR | |
| PRMT_ISSUE_DATE | PRMT.ISSUE_DATE | |
| PRMT_EFCTV_DATE | PRMT.EFCTV_DATE | |
| PRMT_EXPR_DATE | PRMT.EXPR_DATE | |
| PROJ_NAME | SUBM.RESRC_PROJ_NAME | |
| ICONT_CONTCT_NAME | CONTCT.CONTCT_NAME | Pulled from EVAL.ICONT_CONTCT_ID |
| ICONT_CONTCT_FIRST_NAME | CONTCT.FIRST_NAME | |
| ICONT_CONTCT_LAST_NAME | CONTCT.LAST_NAME | |
| ICONT_CONTCT_ORG_NAME | CONTCT.ORG_NAME | |
| ICONT_CONTCT_ADDR | CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE | Concatenated Contact Address fields |
| ICONT_CONTCT_ADDR_1 | CONTCT.ADDR_1 | |
| ICONT_CONTCT_ADDR_2 | CONTCT.ADDR_2 | |
| ICONT_CONTCT_CITY | CONTCT.CITY | |
| ICONT_CONTCT_STATE | CONTCT.REF_STATE_Code | |
| ICONT_CONTCT_PHONE | PHONE.PHONE | |
| PERMT_CONTCT_NAME | CONTCT.CONTCT_NAME | Pulled from PRMT.PERMT_CONTCT_ID |
| PERMT_CONTCT_FIRST_NAME | CONTCT.FIRST_NAME | |
| PERMT_CONTCT_LAST_NAME | CONTCT.LAST_NAME | |
| PERMT_CONTCT_ORG_NAME | CONTCT.ORG_NAME | |
| PERMT_CONTCT_ADDR | CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE | Concatenated Contact Address fields |
| PERMT_CONTCT_ADDR_1 | CONTCT.ADDR_1 | |
| PERMT_CONTCT_ADDR_2 | CONTCT.ADDR_2 | |
| PERMT_CONTCT_CITY | CONTCT.CITY | |
| PERMT_CONTCT_STATE | CONTCT.REF_STATE_CODE | |
| PERMT_CONTCT_PHONE | PHONE.PHONE |
nSpectImport.CME_INSPECTION_EVAL_CONTCT (repeating data)
| nSPECT Data Integration Tag | nCORE Database Field Name | Comments |
|---|---|---|
| EVAL_CONTCT_NAME | CONTCT.CONTCT_NAME | |
| EVAL_CONTCT_FIRST_NAME | CONTCT.FIRST_NAME | |
| EVAL_CONTCT_LAST_NAME | CONTCT.LAST_NAME | |
| EVAL_CONTCT_TITLE | CONTCT.TITLE | |
| EVAL_CONTCT_ORG_NAME | CONTCT.ORG_NAME | |
| EVAL_CONTCT_ADDR | CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE | Concatenated Contact Address fields |
| EVAL_CONTCT_ADDR_1 | CONTCT.ADDR_1 | |
| EVAL_CONTCT_ADDR_2 | CONTCT.ADDR_2 | |
| EVAL_CONTCT_CITY | CONTCT.CITY | |
| EVAL_CONTCT_STATE | CONTCT.REF_STATE_CODE | |
| EVAL_CONTCT_ZIP_CODE | CONTCT.ZIP_CODE | |
| EVAL_CONTCT_PHONE | PHONE.PHONE | |
| EVAL_CONTCT_PHONE_EXT | PHONE.PHONE_EXT | |
| EVAL_CONTCT_AFFIL_CONCAT | REF_AFFIL_TYPE.DESCR | Concatenated Contact Evaluation Affiliation (Role) Types separated by commas |
nSpectImport.CME_INSPECTION_PRMT_FEATR (repeating data)
These tags populate features for the permit specified in the evaluation record.
| nSPECT Data Integration Tag | nCORE Database Field Name | Comments |
|---|---|---|
| FEATR_LOC | FEATR_LOC_GEOG.LAT, FEATR_LOC_GEOG.LONG | Concatenated feature latitude, longitude separated by a comma |
| PRMT_FEATR_DESCR | FEATR.DESCR | |
| PRMT_FEATR_ID_TXT | FEATR.FEATR_ID_TXT | |
| PRMT_FEATR_TYPE | REF_FEATR_TYPE.DESCR |
Outbound to nCORE
Data integration tags can also be used to populate data in nCORE, and perform various actions. See below for configured tags and integration descriptions:
| nSPECT Data Integration Tag | nCORE Field Tag | Description |
|---|---|---|
| START_DATE (valid on nSPECT "Date" control) | EVAL.START_DATE | In conjunction with START_TIME, Will fill in nCORE Evaluation Field "Start Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1". |
| START_TIME (valid on nSPECT "Time" control) | EVAL.START_TIME | In conjunction with START_DATE, Will fill in nCORE Evaluation Field "Start Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1". |
| END_DATE (valid on nSPECT "Date" control) | EVAL.END_DATE | In conjunction with END_TIME, Will fill in nCORE Evaluation Field "End Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1". |
END_TIME (valid on nSPECT "Time" control) | EVAL.END_TIME | In conjunction with END_DATE, Will fill in nCORE Evaluation Field "End Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1". |
| FOLLOWUP_DATE (valid on nSPECT "Date" control) | See Description | Creates a new Evaluation (EVAL) record in nCORE using the date specified in the control and the Evaluation Type (REF_EVAL_TYPE_CODE) specified as the followup inspection type. |
| EVAL_DCSN | EVAL.REF_DCSN_CODE | Matches values from nSPECT control to REF_DCSN.DESCR, and populates Evaluation Decision (EVAL.REF_DCSN_CODE) with the matching value. |
Inspection Results Tab
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.
Violations
Questions marked as Violations in nSPECT can be configured to create violation records in nCORE using the "Reference / Citation" field on the nSPECT screen where form questions are edited. First, Citation Reference Text must be entered in the nSPECT "Reference / Citation" field (field QUESTION_REFERENCE in nSPECT FORM_CONTROL table). Then, the same text must be entered into the appropriate "Violation Types to Categories" record in the nCORE Lookups admin screen in the "nSPECT Data Integration Tag" field:
Once the appropriate record is found, enter the violation reference text in "nSPECT Data Integration Tag" field:
On this page
Sub-Topics
Related Content