In fact we have used at sometime up to 13 but in reality most covered by use of less than 10. The fact is the deeper you go surprisingly the less "work" objects which become "generic" - if you step up it is inevitably going to take you to function objects which restricts flexibility. So what are these work tasks? Actually very simple too simple for IT to retain complexity and all business driven. In each case they are represented by buttons on a Graphical Designer that when added to a process - make the process of designer?s choice.
A normal task
A form task (web form)
A calculation task
A program task
A pending task
An event task
A report task
An import/export task
A finish task
A sub process task to a process (where libraries of frequently used function processes can be built up for re-use)
Then link tasks true and false with rules capability
Each has a tile to open and insert required information and it works - yes it may sound unbelievable but it true - no "code building" or compiling and driven by business analysts dispensing with the "tyranny" of over the wall to coders....Proven and with surprising results.
Search my name see for yourself in my writings that have been published.
Discussion on:
Message 10 of 1
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
