Hello,
I wanted to ask the question to see what the current / best practices being used are regarding source control for your Documentum projects. In this post I'm using the word "project" loosely as I mean everything from custom java classes to Documentum artifacts, to workflows in ProcessBuilder.
Currently we are developing a project that requires us to build custom TBOs, types, modules, documentum jobs (written in java), form validators (written in java), forms, workflows and other customizations. To facilitate development we are using VSS, composer, process builder and form builder.
For the customizations that are done via composer we are using VSS as our repository. My question is what is the current practice for source / version controlling for things developed in process builder and / or form builder? I know that in order to develop in process builder and form builder I need to be connected to the documentum repository and thus there is already a pseudo source / version control being used, but unless all our developers are using a common development documentum repository, this approach is difficult to maintain (which brings up an entirely seperate question of individual development sandboxes vs. a common development enviroment, but that's a question for an entirely different post). I'm also a little weary about using the development Documentum reposotiry as my source / version control for these items.
The other aspect of this approach that I am not too thrilled about is that there is no longer a single place where I can have all my "source" for a single Documentum project.
Sorry abou the length, but I wanted to ask and find out what others are doing / using to manage all this.
Any insight would be greatly appreciated.
Thanks,
Roger
