Rachel:
I believe that business rules should always be separated, even for
non-volatile, bureaucratic stuff like health-care claims. Because then you
have flexibility to quickly adapt your business to external forces such as
new programming tools (think Java, VB.Net) or to new communications
protocols (think HTTP, XML).
In business application software design, the holy grail is to separate
business logic from any other factor - presentation, data access method, or
protocol. Additionally, this functional separation does not entail any time
delays. What's not to like ?
Cheers,
Paul
|-----Original Message-----
|From: Electronic Data Interchange Issues
|[mailto:[EMAIL PROTECTED]]On Behalf Of Rachel Foerster
|Sent: Wednesday, May 23, 2001 11:48 AM
|To: [EMAIL PROTECTED]
|Subject: Re: Dual 997's
|
|
|Paul,
|
|I too used to argue strongly for not applying any business
|rules during the
|transaction process. However, over time I'm come to realize
|that there are
|benefits to doing so. I'm not saying that ALL application
|edits are moved
|into the EDI system, but rather a subset of them. One of the
|reasons used in
|the past for not trying to apply business rules in the EDI
|system was that
|yesterday's EDI systems were inadequate to the task. Today's
|systems are
|not. The sooner one identifies errors and returns acks back to the
|originating system is a better approach. Else, why have
|pre-order processing
|systems that handle dialogue directly with customers prior to passing a
|complete and correct order in to the order management system?
|
|But, I'm not at all advocating that everyone take any one
|approach. Let each
|enterprise determine what makes best business sense for itself and its
|trading partners. I'm all for flexibility and agility and less
|rigidity.
|
|Rachel
|
|
|Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
