The VI XML format supports a number of Meta Tags to control the data processing and logging. These Meta Tags are defined as XML comments in the VI XML document.

Set VI XML to "not relevant"

This Meta Tag sets an VI XML document as not relevant for processing. This means that the XML is logged but not processed.

For the inbound case this means that the VI XML will not be written to the GIS database.

For the outbound case this means that the message will not be send to the external system.

uti.msg-not-relevant
msg (String)
log (Boolean)
<xsl:comment>uti.msg-not-relevant={"msg":"object is not relevant"}</xsl:comment>
<xsl:comment>uti.msg-not-relevant={"msg":"object is not relevant","log":false}</xsl:comment>

Set VI XML to faulty

This Meta Tag sets the VI XML document to faulty.

uti.error
msg (String)
break (Boolean)
<xsl:comment>uti.error = {"msg":"Error!"}</xsl:comment>
<xsl:comment>uti.error = {"msg":"Error!","break":"true"}</xsl:comment>

Set query expression for DB endpoints

This Meta Tag sets an query expression for DB inbound endpoints:

uti.servicepoint.where
condition (String)
<xsl:comment><xsl:text>uti.servicepoint.where={"condition":"date_completed &gt; '</xsl:text><xsl:value-of select="//ATTRIBUTE[@name='date_completed']/@value"/><xsl:text>'"}</xsl:text></xsl:comment>

Update message protocol information

This group of Meta Tags are used to set the protocol information for processing the VI XMl document.

uti.protocol.username
uti.protocol.source_system
uti.protocol.gis_id
uti.protocol.class_id
uti.protocol.ext_id1
uti.protocol.ext_id2
uti.protocol.ext_id3
uti.protocol.ext_id4
uti.protocol.operation
uti.protocol.obj_type
uti.protocol.notice