Bookshelf Home | Contents | Index | Search | PDF |
Siebel Tools Reference > Application Development Projects > Checking In Projects >
Check-In Guidelines
Here are some rules to follow when you check in projects:
- Before doing a check-in, make sure that the projects you are checking in are in a stable state and have been thoroughly tested against your local repository. Check in projects only when all dependent Siebel VB code is complete.
- Check in all dependent projects at the same time to be sure that the configuration on the server remains consistent.
For example, if you create a new PickList object definition in the PickList project and reference that object definition in your Oppty project, check in both projects to the server at the same time.
- Consider the timing of your check-in and its impact on the work of other developers. In some instances, you may need to check in a project before you have fully completed the configurations required in that project because another developer's configurations may depend on a particular feature you have added to your project.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Tools Reference Published: 20 October 2003 |