General

Can squid by arc46 import data into ServiceNow?

No. ServiceNow provides a complete framework for importing data. There is little we could add to that.

I'm missing a property in a predefined configuration.

Head over to Configurations (Predefined) for an explanation on what we include why or give us a heads-up over at Feature Requests, and we'll see what we can do.

Why are you effectively reproducing the ServiceNow table structure documentation here?

The probable and intended users of squid by arc46 are not ServiceNow users. We are making data held in ServiceNow accessible to peripheral systems that might know little to nothing of ServiceNow and quite frankly aren't really interested in internal ServiceNow structures. The predefined configurations that come with squid by arc46 are an easy pick and chose selection for the developers of peripheral systems that want to integrate ServiceNow data.

Are JSON schemata for the configurations available?

Not yet.

What squid by arc46 returns as JSON is highly dynamic and depends on various factors including the requested configuration, the parameters of the request as well as the state of your ServiceNow instance.

A future release will provide a query flag that will return a JSON schema matching the request instead of data. (Think ?wsdl flag for WebServices.) This already works as a proof-of-concept, but still needs some work for general availability.

If this is important to you, head over to JSON Schema Support and give the feature request a boost.

Log Entry "Missing config 'referenceClass' for referenceName 'referenceName'. Reference will be rendered as SysId."

Unless explicitly configured, squid by arc46 will attempt to render a reference with an implicit configuration based on the class of the reference.

Example:
Reference field ci
Referenced table: cmdb_ci
Implicit targetConfiguration for reference: cmdb_ci

If squid by arc46 does not find a configuration cmdb_ci it will log

"Missing config 'cmdb_ci' for referenceName 'ci'. Reference will be rendered as SysId."

and render the referenced CI as SysId. This is valid and expected behavior.

arc46 intends on providing predefined configs for all ServiceNow default tables, eventually minimizing these log statements. References to customer specific tables will however always log the mentioned entry unless you define the appropriate config yourself.