Data Validations

It refers to data and UDF validations of the offer requests and order requests. The offer is either validated or invalidated.

If the data is not validated within the request or input and active UDFs fail to adhere to their corresponding length, datatype, rangeValue, or regular expression, the product model gives an error message.

Property Name Details
CheckRelevantOLUDFs

Validation Flag:

com.tibco.af.ope.flags.chkrelevantoludfs

Description:

Validates UDFs attached to the product that are defined as input characteristics of the product. This functionality can be switched on using the configuration.

CheckValidOLUDFs

Validation Flag:

com.tibco.af.ope.flags.chkvalidoludfs

Description:

Validates mandatory characteristics attached to the product model that are found in the corresponding product instance as UDFs in the request. This functionality can be switched on using the configuration.

CheckValidLinkUDFs

Validation Flag:

com.tibco.af.ope.flags.chkvalidlinkudfs

Description:

Validates mandatory linking UDFs that are attached as UDFs to the product in the order request. This functionality can be switched on using the configuration.

ValidateOrderLineUDFsDatatype

Validation Flag:

com.tibco.af.ope.flags.validateudfdatatype

Description:

Validates the UDFs datatype. The datatype can be configured in the product model. The following are valid values: Currency, Digits, Date, Time, and Boolean

ValidateOrderLineUDFRange

Validation Flag:

com.tibco.af.ope.flags.validateudfrange

Description:

Validates that the orderline UDFs are within the range specified in the corresponding product model. This functionality can be switched on using the configuration.

ValidateOrderLineUDFRegex

Validation Flag:

com.tibco.af.ope.flags.validateudfregex

Description:

Validates that the orderline UDFs have the values per the regex. This functionality can be switched on using the configuration.

ValidateProdDate

Validation Flag:

com.tibco.af.ope.flags.validateProdDate

Description:

Validates the products' start and end date. This functionality can be switched on using the configuration.

With the ValidateProdDate flag, the dates required to be set must have the characteristic name as "StartDate/EndDate". The characteristic names are case-sensitive. The dates must be xsd:datetime format and the valuetype as "Input". The following is an example:

<characteristics>
        <name>EndDate</name>
        <description>Characteristic</description>
        <instanceMin>0</instanceMin>
        <instanceMax>0</instanceMax>
        <evaluationPriority></evaluationPriority>
        <actionID></actionID>
        <value>
            <type>Input</type>
            <rangeValue></rangeValue>
            <discreteValue>2011-01-01T00:00:00</discreteValue>
            <mandatoryValue>true</mandatoryValue>
        </value>
...
</characteristics>