Form validation and processing

Confirmation versus constraint

A confirmation will allow the user to continue with the update. A constraint will prevent the action.

Constraint First set Exists

Use this code syntax to check to see if a record set exists for a business class. Upon evaluation, if the system encounters any first records in this business class, it is interpreted as true. If there are no records, it will be false. If true, enforce the constraint.

This can be used to prevent the user action if a record does not exist.

This example prevents the ability to release JE if a related supporting document has not been attached to the JE record.

constraint (first GeneralLedgerJournalDocument set exists)
    "PleaseAttachDocumentationBeforeReleasing"