I recently updated a CDT, which is referenced in a process model subprocess. The

This particular application relies on CDT's by reference because the process contains inner loops: one Review to many Review Stages, one Stage to many Cycles.

It's absolutely necessary to encapsulate the stages and cycles as sub-processes, and it's also necessary that the base process model be updated real time with the changes to the CDT's from each cycle.

When I decided to pass by reference, it seemed like the right decision because of the nature of this particular business process and because the CDT's can be large and I wanted to conserve memory usage.

Fortunately these CDT's are pretty static. I hope I can reverse the changes by reverting the XSD's or I'm going to have a very big problem with production processes.

I wish the warning not to pass CDT's by reference wasn't buried in the documentation. I went to training AND read through the docs when I started developing on the platform, and still somehow missed this.

This particular application relies on CDT's by reference because the process contains inner loops: one Review to many Review Stages, one Stage to many Cycles.

It's absolutely necessary to encapsulate the stages and cycles as sub-processes, and it's also necessary that the base process model be updated real time with the changes to the CDT's from each cycle.

When I decided to pass by reference, it seemed like the right decision because of the nature of this particular business process and because the CDT's can be large and I wanted to conserve memory usage.

Fortunately these CDT's are pretty static. I hope I can reverse the changes by reverting the XSD's or I'm going to have a very big problem with production processes.

I wish the warning not to pass CDT's by reference wasn't buried in the documentation. I went to training AND read through the docs when I started developing on the platform, and still somehow missed this.