Hey,
I would like to create a paper as guideline for creation of further integration processes. The
last project has been end up in a chaos without a possibility of enhancement or maintenance.
Therefore I started with a naming convention and a paradigm of designing SWC.
Now I would like to give some hints about how a good bpm design looks like. Does someone
have some information about that.
I have:
- when a bpm is unavoidable (splitting, alerting..)
- when a bpm is not necessary (multi-mapping...)
- which bpm step needs lot resources (recveive/send steps, transformation...)
Do you have some hints for modular designing of bpm? For example to put error
handling in an own bpm (for reuseability) or something else?
How do you design BPMs to keep them small and clear?
thanks
chris