Source code control and version control for Notes

Teamstudio CIAO! provides source code and version control at the Notes element level, allowing multiple developers to work concurrently on the same database design without the threat of potential conflicts. Teamstudio CIAO! produces a comprehensive audit trail of the development process, allowing developers to track their design changes.

Download the CIAO! Datasheet

Implementing Teamstudio CIAO! in Your Environment

Whether driven by external regulatory changes, internal audit concerns or a simple desire to work in an efficient and controlled manner, implementing a best practices source code control system in any Notes/Domino development environment is essential. Teamstudio CIAO! software, combined with expert on-site implementation and training will help reduce concerns about inefficient team efforts or compliance failures.

Download the CIAO! Implementation Datasheet

Solutions Brief: Source Code Control for Lotus Notes Applications

Lotus Notes applications have transitioned from back room to mission-critical in many organizations, but software development processes have not changed. This has resulted in out-of-control development cycles, application failures and irate customers. By embracing source code control, IT organizations can bring order out of chaos, contain costs and improve end-user satisfaction.

Download this Solutions Brief on Source Code Control

What Teamstudio Customers are Saying About CIAO!

"Automation Centre loves CIAO! This product has dramatically improved the quality and reliability of our product management process."

For more CIAO! Feedback, Check Out Our Testimonial Page

Teamstudio CIAO! Tool Tip

CIAO! Authority - More than just for Grabs

You probably knew that you could restrict who has the ability to overtake ownership of elements owned by other users through the Teamstudio CIAO! Configuration database, but did you know you could also restrict who has access to add new elements?

The Authority section allows you to specify who has access to perform important functions regarding your database applications.

Check-Out / Check-In: These two features normally go hand in hand, but for the unique cases that only one or the other should be enabled for certain users, these two features are split apart.

Add: With this feature it is possible to restrict who can add new elements to the database.

Delete: With this feature it is possible to restrict who can delete elements from the database.

Grab: The grab feature makes it possible for developers to wrest control of design elements from one another, so restricting access to the grab functionality is often a good idea.

Make Version: Making a version is often delegated to a single or select few. Explicitly restricting access to those people is part of best practices.

Promote: Promoting is also often delegated to a single or select few. Explicitly restricting access to those people is part of best practices.

Used in conjunction with one another, these restrictions can further lock down your database in development to ensure maximum control and reliability.