Integration

We have a lot of processes that need to be integrated with an ADF application and we have a discussion about where to put the implementation of the taskflows of these BPM tasks.

BPM allows us to auto generate the taskflows based upon the payload of the process. This does not allow a lot of flexibility to change the taskflow. If we change the taskflow and have to generate again, we lose the changes we made.
The BPM architects say that we will gain a lot of time by autogenerating. The ADF architects (like me) say that it's better to build those taskflows ourself and put them inside the ADF application (or ADF LIbrary jar). This way we have full control over the code.

One of the main reasons why we are not that fund of using the autogeneration is that we have a detailed UX guideline that requires some special attention of the development of an ADF page. When autogenerating the taskflow, we probably have to change quite a lot to make it compliant with the UX standards.

The question is, do we have control over the autogenerated taskflows so we don't have to redevelop everytime we generate a taskflow again?

What are the advantages of generating instead of developing it yourself? Being an ADF developer myself, I tend to say we have to go for the custom implementation because of the UX requirements so we have full control over the code.

Can anybody give some more information about the generation or give his point of view about this problem.

Thanks.