David,
Thank you very much for the advice. I'll keep those differences in mind.
I guess my question wasn't very clear. I need to know if there is
functionality in the SECA to detect if a field changed. I'm thinking
there isn't and I'll have to write some code to keep a history of status
changes.
-Adrian
David E Jones wrote:
Are you wondering about when to use an EECA versus when to use an SECA?
In general you should not use EECAs for anything business process
related, but rather for data maintenance tasks like populating
denormalized fields (like OrderHeader.grandTotal), or things like
keeping the status history. However, usually status history maintenance
code goes right into the create and update services, like in the
updateExample service. I'm working on this a little bit relative to the
new entity-auto service engine implementation do handle some of these
standard patterns automatically.
SECAs are the tool for composing business processes and tying separate
processes together. They are obviously used for other things, but their
main purpose is to get a process started automatically based on a
"system event" instead of a "user event". For example, invoice an order
once a shipment is packed.
-David
On Jul 23, 2008, at 6:38 PM, Adrian Crum wrote:
Can I use EECAs or SECAs to monitor an entity and trigger an action if
the contents of a field changed? I need a way to track status changes.
-Adrian
