Integrations & Setup
Factry Historian
External measurement validation
if measurements need to conform to a certain internally used format, a validation server can be used to enforce this configuring a validation endpoint external validation settings can found under configuration > external validation here you can enable or disable external validation configure the severity level configure one or more validation endpoints implementing a validation server a validation server is a web server that implements at least one endpoint conforming to the validation endpoint protocol it should accept a post request with a payload containing a list of measurements an example \[ { "uuid" "dad3f495 22b1 11ec 864a 81d3f45e479b", "name" "tank1 temperature", "description" "", "datatype" "boolean", "database" "historian", "collector" "opc ua staging", "tags" {}, "status" "active", "settings" { "nodeid" "ns=1;s=boolean 22", "collectiontype" "polled", "collectionoffset" 0, "collectioninterval" 5000 } }, { "uuid" "c54b4e3c 6f02 11ec 864a 81d3f45e479b", "name" "site1 tank2 temperature", "description" "", "datatype" "number", "database" "historian", "collector" "modbus", "tags" {}, "status" "active", "settings" { "regtype" "input register", "byteorder" "default", "collectiontype" "monitored", "modbusdatatype" "int32", "collectionoffset" 0, "collectioninterval" 2000, "address" 1 } } ] it should respond to this request with a json list containing a response for each of the received measurements in the following format \[ { "uuid" "dad3f495 22b1 11ec 864a 81d3f45e479b", "valid" false, "error" "should include site prefix" }, { "uuid" "c54b4e3c 6f02 11ec 864a 81d3f45e479b", "valid" true, "error" null } ] the endpoint can perform any internal business logic required to ensure the validation settings are correct this can for example be used to enforce a specific measurement name format

