Dependency between BPM Projects

Question

Hi,
I'm planning the construction of a sales application project. It is composed by eleven topics and I want to know if each topic can be constructed in its own project and each project uses the same custom jsp presentations, webresources, BPM Objects. The reason to implement this is to improve the maintenance in production; because if I quit one project from the engine I don't want to quit the entire project with all the sales process.
Thanks for your help,
Guillermo

Answer 1

Just so you know, you can share JSPs and BPM objects between projects. There's a commonCatalog folder in studio that can be maintained under a common module of code in your repository. Likewise the JSPs can be organized as well in folders that are common to other projects in the repository. When you check in or out code, common objects go into one common module and project specific code go into their own module.
To share BPM objects using the commonCatalog, I just copy the module/folder (e.g. SharedObjects) from the componentCatalog to the commonCatalog. These objects appear to be from the same place from within studio, but they are in separate folders and separate repository modules. This makes it easy to maintain them in your source repository.
Also, if you right-click on the project and go into properties you can have dependencies of projects. One project can be dependent on another. So far, I was only able to share BPM objects. Screen-flows, and processes cannot be shared. JSPs could be shared by using the common folder/branch idea I mentioned before.
If you want to place all projects into one project, that's okay too. When you deploy projects to the server, you can control deployments down to the process level. So for most folks that is the easiest approach.
HTH
Mark