Configure ticket validation

When a schedule entry is activated, the settings, shown in the following example, specify the fields that need to be validated and provide a regular expression that is applied to each field value. The regular expression typically defines a range that the value must be within. For example, a setting may require that the scheduled flow rate field be a positive, non-zero number.

{

"LMS": {

"BatchXfer": {

"TicketValidation": {

"Rules":

[

{

"name": "sch.schdens",

"fieldtype": "float",

"value": "^(?!^\\s*-?0*[\\.,]?0*\\s*$)(\\s*-?[0-9]*[\\.,]?[0-9]*)\\s*$",

"message": "Scheduled Density must be configured to a non-zero value"

},

{

"name": "sch.schrate",

"fieldtype": "float",

"value": "^(?!^\\s*-?0*[\\.,]?0*\\s*$)(\\s*-?[0-9]*[\\.,]?[0-9]*)\\s*$",

"message": "Scheduled Flow Rate must be configured to a non-zero value"

}

]

}

}

}

}

Where:

• "name" is the field within the schTicket table to be validated. Use periods to separate fields and subfields.

• "value" is a regular expression that indicates the criteria against which the name is compared. If the name is something other than a string, it is first converted to a string representation.

• "fieldtype" is the type of field represented by name. The field type options are as follows:

  • string

  • int

  • float

  • double

  • bool

    Note: The default fieldtype is string.

• "message" indicates the change that needs to be made to make the ticket valid. This message defaults to a generated message using the name and the value. You can modify this attribute.

  Notes: The attributes given in the example in each ticketValidation element ensure that both the fields sch.schdens and sch.schrate contain a non-zero value. If either field does contain a zero, then the error defined in the message attribute is displayed to the Controller.
  The values are converted into strings from floating-point numbers.
  These strings serve as the basis of the regular expressions against which the field is compared. You may add configuration lines to the default configuration file to define the specific additional criteria they would like to submit for validation. 
  The configuration file for AVEVA Pipeline Operations for Liquids is located in %DNAInstallRoot%\RealTime\config\Settings\LMS.RealTime.Json.
  For more information on the creation of regular expressions, refer to the MSDN reference page (https://msdn.microsoft.com/en-us/library/az24scfc(v=vs.110).aspx).