The new Team Coding Dashboard in Toad for Oracle 12

Please enable Javascript to watch this video

http://www.DellSoftware.com/Toad-Oracle
Learn how development teams can more easily work on shared code with the new Team Coding Dashboard in version 12 of Toad for Oracle, the number-one solution for Oracle database development and administration.

Hello, everyone. My name is Anju Gandhi, Product Manager for Toad for Oracle. Today we will review the feature in Toad for Oracle, the Team Coding dashboard. Team coding enables development teams to work on a shared code base without overwriting each other's changes. It also provides a seamless integration with multiple version control systems.
You access the team coding via the Team Coding menu item located in the Utilities menu. First, you click on the Configure Team Coding. And that lets you select the Enable Team Coding, Use the Code Collections. Now, you use code collections to define your projects.
Then you chose the version control system of your choice. Toad for Oracle 12 has support for Team Foundation Server 2012, as well. After relevant selections have been made, if there are any issues during the setup process, there are enhanced status handlers in Toad for Oracle 12 that guides you through the setup process.
And if there are any issues along any of these conditions, there will be a red cross box. And if you double-click on it, it will take you to the problem resolution area. So this provides a very easy, self-guided setup process for team coding.
Once the setup for configuration for team coding is completed, you access the Team Coding dashboard via Utilities, Team Coding, Team Coding dashboard menu item, or the Team Coding dashboard icon located right here. The first tab of the Team Coding dashboard is the Code Collections. Now, this is where you define the code base that you will be working upon. Herein I have defined a schema and all the objects contained within a schema. And I defined this to be my project that I will be working upon.
The second tab will be the central area, the control tabs, where all of the objects that you have defined in your code collections will be visible here. You can right click on any object and perform regular VCS functions such as checking out, comparing the contents, creating new revisions in VCS. The enhancements in the Toad for Oracle 12 is around the ability of group selecting multiple objects and then performing the comparisons or creating new revisions for the group of objects.
You can also come at the highest level at the code collection and right-click and then see the differences in the version control system and the database. So you can select your project and see which all objects are not yet checked into VCS and vice versa-- which objects are in VCS but not in database. And then you can, accordingly, either add those objects to the VCS or import those objects in database.
So this gives users a greater flexibility of performing the version control system actions right from the same interface, Team Coding dashboard. Now, checking out an object is pretty simple. You just add comments.
After the object is checked out, you double-click on it, and it takes you to the editor. You make your relevant changes, compile it, save it. And then you come back into the Team Coding dashboard, and you can check the object in. So this is a pretty easy workflow while staying within Team Coding dashboard.
The VCS browser enables the file level view of all your code-based changes. You can also work on external SQL files that are not part of your team coding objects. And you can check them out. You can check them back in, compare their contents, and see their revision histories as well.
So you're not limited to just working on the database objects. But you can also work on the external files using the VCS browser. And then you can also see the history of changes of your object files as well. So you see how the new Team Coding dashboard user interface and the guided setup process, enhanced status handlers all combine to give you an easier workflow to work in a version control system environment without ever having to leave Toad.