USoft Rule Language and Domain Constraints

Previous Next

See Also

The following two field prompts in the Domain Constraints definition window of USoft Definer refer to USoft Rule Language. The Old Prompts refer to the prompts that were used for these fields in previous versions of USoft. Other than the prompt name change, domain constraint definition is not otherwise affected when compared with older versions of USoft.

 

New Prompt

Old Prompt

Do Not Allow That

Condition

Make Sure That (in these cases)

Correction

 

 

The following examples illustrate how the fields of the Domain Constraints window may be completed for various simple scenarios. They also give an idea of how the naming of the field prompts refer to USoft Rule Language syntax.

 

Example 1 – Restrictive domain constraint

 

Field

Value

Domain Name:

EMAIL

Do Not Allow That:

instr( domain,'@',1,2 ) != 0

Message

E-mail address may not contain more than 1 @ sign.

Make Sure That (in these cases):

(null)

 

 

Example 2 - Corrective domain constraint, no condition

 

Field

Value

Domain Name:

EU_DATE

Do Not Allow That:

(null)

Message

(null)

Make Sure That (in these cases):

timestamp_to_date( domain )

 

 

Example 3 – Corrective domain constraint, specified condition

 

Field

Value

Domain Name:

EMAIL

Do Not Allow That:

instr(domain,'@') = 0

Message

E-mail address must contain the @ sign.

Make Sure That (in these cases):

domain || '@usoft.com'