Database Reference
In-Depth Information
nature of JavaScript can be very attractive in the user interface, it can also be circum-
vented easily. Any validations that are executed in JavaScript should also be supported
with appropriate validations during page processing or at the database level.
Note
It's a good practice to assume that every transaction is malicious. It's possible
to implement validations strictly for security purposes, but sometimes it's difficult to
step away from a process enough to identify where weak points may exist. For example,
in a shopping cart application, what would happen to the total if someone ordered -1 of
a product? Would they automatically get a credit? Take extra time in the development
process to look at your application to identify where security weaknesses may exist and
implement features to make it generally more robust and secure.
There are four types of validations: item level, page level, and, for tabular forms,
column level and row level. Item-level validations operate against a single APEX item.
Page-level validations are used when multiple items are involved in validating the con-
dition. Tabular form validations behave similarly but against the columns and rows of
the tabular form. You use an example of each in the Help Desk application.
Item-Level Validation
Validationson a single element can have attributes specific to that element, and behavi-
or can be customized as required by that element. The example you implement here is
a validation that checks its condition only when a specific criterion is true. The require-
ment is to have an end date entered whenever the status is closed. Follow these steps:
1.
Edit
Page 210
of the application.
2.
