Toad Intelligence Central Integration
- A new high-level code-quality dashboard on Toad Intelligence Central shows combined information from
Team Coding, Code Analysis, and Code Tester, thus enabling teams to view a code quality summary and
trends by project and by database. This information includes traceability (who checked in what, when
and why). Filtering of this data (for example, the worst 5 or 10 objects) is supported.
- Team Coding can now be installed in a central development database on the Toad Intelligence Central
server. This feature enables you to install Team Coding once, to service all development teams, rather
than having to install it on every local team database. This prevents the loss of the Team Coding
configuration when maintenance activities such as refreshes are performed.
- To support Toad Intelligence Central, the database list in DB Health Check has changed. There is no
longer a list of every database in your TNSNames file for you to select databases from. Instead, the list
now shows only the connections that the Health Check will run against. There are buttons to
add/remove connections to the list. Database Health Check actions from 12.8 and older should get
converted automatically to the new format, but if the conversion process cannot find a login record for
one of the databases in the list, it will prompt you one time for that connection.
- Previously published artifacts can now have their content updated without the need to replace the
existing artifact.
Team Coding
- Team Coding now supports the Mercurial version control system. Toad supports standard version control
commands, such as check-in, check-out, add, and revision information to your locally-stored Mercurial
repository. For instructions on setting up Team Coding to work with Mercurial, see the Team Coding
section of the online help.
- You can now use different Code Analysis rulesets/controls with different Team Projects. The Code
Analysis integration dialog is now shown on the Team Project configuration window. One benefit of this
change is that you can apply one ruleset for one project to block check-in on failed validation, and then
apply a different ruleset for another project to allow code check-ins on failed validation.
Schema Browser
- A new RHS tab in the Schema Browser can be displayed to show unit tests associated with a selected
PL/SQL object.
- Two new options were added to the Editor|Behavior page in Toad Options:
Home jumps to the first character. End jumps to the last character. Both are enabled by default.
- The right-click Compare menu has a new menu item for comparing object DDL at a caret to the object
source in the database.
- If your code generates an error after you run it in the Editor, you can click the error to go to relevant
descriptions and solutions shown in the Jump Search feature.
Improved Jump Search
- Jump Search now integrates with the Toad support API to return more useful results from the Knowledge
Base. Previously there was one Knowledge Base link under the Support Portal heading, which opened to a
list of relevant KB articles in a browser. Now, there is a Knowledge Base heading, under which are links to
every relevant Knowledge Base article. Each link shows the title of the article, and the articles open directly
in Toad.
Other new features
- When a new version of Toad is available, a popup message shows the new features in the release. This
helps users know that a new version is available and also helps them to get started more quickly.
- A new Sync with DBMS Redefinition option was added to the Object Type Specific Options tab. This
feature applies to column order differences. When selected and column order differences are present
between the source and target table,Toad rebuilds the target table in the sync script by using dbms_
redefinition. This suppresses all other ALTER TABLE commands for the table, since the redefinition
process will handle those too.
- The database dropdown on the login window now has a popup menu with the following items:
- Show TNSNames entry (displays info in a dialog)
- Send TNSNames entry to Direct tab (sends host, port, service name to the direct tab so you can
connect that way)
- A new button on the Pluggable Database tab in the Database Browser was added to create a TNSNames
entry for the selected database.
- Support was added in the Database Browser to save the current state of a pluggable database, so that it
can be automatically restarted after the container database is restarted.
*******
Additional information relating to the new features in version 12.10 can be found in the Toad for Oracle
Release Notes or in the 'New in this release' of the Help. (includes instructions and screenshots)