>
> I'm not completely clear what is meant by "business logic." Do you mean
> custom methods such as adding a method like totalCost that takes two fields
> and returns a total? Do you include the relationship methods as well or is
> that also part of business logic?
Business logic is code that isn't implied by the data, and its the
most custom to a program. Its a term used a lot in the WO marketing
literature.
Simplified Example:
In my bug database, if your user type is set to QA, in my "to do
list" page you see open bugs, and bugs marked fixed. That's because
as a tester, that's what you care about. You see the currently open
bugs so you can add information to them. You see fixed bugs because
its your job to verify them fixed.
If your user type is set to Engineering, you see Open bugs, since
you just want to go through them, fix them, and mark them as fixed.
If your user type is QA manager, you see counts of the bugs of
different catagories, and you see a list of Fixed & Verified bugs so
that you can close them.
That's "business logic" because its logic about how you deal with
the data, not how you access the data. A big selling point of EOF and
WOF, is that ideally, you write just the "business logic". All the
rigamarole of moving data into/out of web pages and databases is done
automatically for you.
In practice you have to write some minimal "data logic" to deal
with stuff like "Fullname = firstname+middlename+lastname+suffix".
And I tend to write a bunch of "page logic", because I can't stand
the typical WO UI where you have an insert button, a save button, and
a delete button on the same page.
Pierce
----------------------------------------------------------------
Pierce T. Wetter III, Director, Twin Forces, Inc.
e-mail: [EMAIL PROTECTED] Phone:520-779-4227
<http://www.twinforces.com/>
U.S. Mail: 1300 South Milton Rd, Suite 206, Flagstaff, AZ 86001
