> What is going to happen is event type {a} happens (lets say it's a
> sale). That triggers a default action plan of umpteen things that
> have to follow based on that event, documents that have to be filed,
> people notified, approvals gained etc, then the the default plan has
> to be modified to allow for the specifics of this particular
> transaction.
>
> So the event has to trigger the generation of a whole heirarchy of
> maybe up to 50 things that have to happen, some of which rely on
> previous things being done
>
I have helped build a project management system similar to what you
describe. Each company's products had a "flow" defined like a tree of
actions and decision processes that all got fired off in order as they
completed each portion of work. We started using a nested set model, and as
the complexity grew (and performance dipped) we converted over to an
adjacency list and it worked just fine like that.
~Brad
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:312764
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
