Element validators
Validators in this category are used to validate elements of business objects.
List of element validators
Allowed Value- Validates a particular element against one or more allowable values.
- Used for validating elements, such as GenderType in TCRMPersonBObj
- Parameter mapping<key, value>: <'AllowedValue', allowed value such as 'M'>
Attribute Validator- Validates that an element value equates to a value or code found
in a code table.
- Used for validating elements, such as IssueLocation in TCRMContractBObj
- Parameter mapping<key, value>: <'AttributeValidator', code table name such as 'CdProvStateTp'>
Before Date- Validates whether a particular date element is before its supplied
date parameter. If no parameter is supplied, the system date is considered.
For example, a start date element may have a future date as its value.
- Used for validating elements
- Parameter mapping<key, value>: <’SpecifiedDate’, a desired date String, according the configured date format)
Default Value- Validates that a particular element is set to a specified default
value (for example, a gender type element may be set to a value of
'U', if the incoming value is unassigned).
- Used for validating elements
- Parameter mapping<key, value>: <'DefaultType', a String value representing the data type of this parameter, such as java.lang.String>
- Parameter mapping<key, value>: <'DefaultValue', a value for the type, such as 'U'>
Disallowed Value- Validates if an element contains disallowed values (for example,
the element LastName may not be allowed to have '%' character value
in it).
- Used for validating elements
- Parameter mapping<key, value>: <'DisallowableValue', a disallowable value such as the character '%'>
EntityNameAllowedValues- Validates the EntityName element against one or more allowable
values. It is used to check the allowed EntityNames in case-insensitive
manner.
- Used for validating elements
- Parameter mapping<key, value>: <'EntityNameAllowedValues', an allowed entity name value such as 'CONTACT'>
- For more information, see Configuring Common Search Exclusion.
Fixed Length- Validates if the length of an element is a fixed value (for example,
a date element in a mmdd format must have a fixed length of four).
- Used for validating elements
- Parameter mapping<key, value>: <'FixedLength', such as a length of '5'>
Mandatory- Validates that an element is required in a given object (for example,
for an Address object, it may be mandatory that a zip code is required).
- Used for validating elements
- No set parameters required
Maximum Length- Validates that an element does not exceed a given maximum length
(for example, for a person name object, maximum length of the last
name is 30).
- Used for validating elements
- Parameter mapping<key, value>: <'MaxLength', such as a length of '150'>
Maximum Value- Validates that a numeric element does not exceed a given maximum
value (for example, for an income source object, maximum value of
the annual amount field is 1000000).
- Used for validating numerical elements
- Parameter mapping<key, value>: <'MaxValue', such as a value of '250000'>
Minimum Length- Validates that an element is greater than or equal to a minimum
length value assigned (for example, for a person name object, minimum
length of the last name is 2).
- Used for validating numerical elements
- Parameter mapping<key, value>: <'MinLength', such as a length of '2'>
Minimum Value- Validates that a numeric element is greater than or equal to a
given minimum value (for example, for an income source object, minimum
value of the annual amount field might be 1).
- Used for validating numerical elements
- Parameter mapping<key, value>: <'MinValue', such as a value of '100'>
MinWildcardSearchLen- Validates that the length of non-wildcard characters of the element
is greater than or equal to minimum length value assigned. By default,
the minimum is 1.
- Used for validating elements
- Parameter mapping<key, value>: <'MinWildCardSearchLen', such as a length of '1'>
NumericPositiveVal- Validates that an element has a positive numeric value. For example,
for a credit card number, the value must be numeric and positive.
- Used for validating elements
- No set parameters are required
Task CreationDate- Validates the value of the supplied element to be not null. This
validator is used for Task Creation date since the value is auto-populated
from the system.
- Used for validating elements
- No set parameters required
Task Creator- Validates the value of Task Creator. If the value is not supplied
in the input it will be compared against DWLControl's RequesterName.
- Used for validating elements
- No set parameters required
TaskDueDate- Validates the task close date is before the task due date.
- Used for validating elements
- No set parameters required