Hi Nicole,

I will check those resources out.

We will not generally be working with different projects. We will usually be working with the same project and making modifications to them like adding a new routine to an existing MAC, adding a button to a Zen page, etc.

We have been testing our process using git with Studio, but now it looks like we are going to use Atelier.

We have a server repository (in Bitbucket) that currently contains XML copies of our MACs and CLSs files. We create a branch from there and pull it down locally to our own personal environment (local Cache instance).

When working with our current task (modifications, new functionalites, etc), we import the needed files into our Cache instance and make our changes. We made hooks to export to XML the files we are working with when we compile.

When done, we commit these changes locally and then push them back to the server (Bitbucket).

What changes now with Atelier besides the files being saved automatically in UDL format when compiling?

Edward, I've been talking about the solution that you proposed to my team members about marking the class or mac as DEPRECATED.

We are looking now in the documentation on how to programmatically  do this. I think we found the Cache class to open a class and mark it as DEPRECATED.

We can't find a way to open  mac file and mark it with a comment like you mentioned.

Would you know how to programmatically do this or should we call WRC?

Thank you for your help.