SUPPORT
  TECHNICAL SUPPORT  |  RELEASE HISTORY  |  RESEND PASSWORD  |  REQUEST KEY 

Release History:

^

ClearDB Documenter 4.7 (Release 1)

Oct 26, 2016

NEW FEATURES

  • NEW: New features and look&feel of the Database Object Tree step:
    • Exclusion of rarely used, “heavy” object types as well as Oracle system and sample schemas by means of an Exclusion Profile, allowing to significantly reduce Docu generation time.
    • “Refresh” and “AutoRefresh” of the tree items:
      • “Refresh (x1)” - one-time refreshing of the content of the Database Object Tree with the actual content of the DB.
      • “AutoRefresh” - automatic refreshing of the content of the Database Object Tree with the actual content from the DB as the first step during document generation.
    • Automatically delayed process of retrieving information and Database Object Tree population.
    • Processing History providing a better understanding/estimation of
      • how much time is needed to load e.g. 25000 objects.
      • how much time is needed to generate a Docu including those objects.
    • No Docu Tree pane.

IMPROVEMENTS

  • Core
    • A new collecting query without sorting a result set in a subquery was applied to improve collecting of Unified Audit Policy.
  • Docu
    • Database Properties, Database Objects, DB Security Audit and other pages that have multiple groups, now show content of only one selected group for ease of navigating. “Show Full Content” allows viewing content of all groups. Implemented for all types of output documents.
    • Manual sorting is now available in tables with schemas, schema and non-schema objects, object types, and observations.
    • Improved alignment of column headers and data in tables of ClearDB Documenter output documents.
    • Errors in the Observations section are now sorted by the line number and their position.
    • “Compilation unit analysis terminated” is no longer shown for errors that do not contain error code and end with “statement ignored”/ “item ignored”/ “compilation ignored”.
    • Sections (pages) that are part of a Docu but have no relevant information found in the Database during Docu generation now show the following message: “No <NodeName> available”. The hint for the corresponding nodes/links is as follows: “The DB contained no information for this section”.
    • Links to sections that were excluded from Docu generation now have the following hint: “The section was excluded from generation of this Docu”.
    • The “top” link was replaced by a floating arrow on all pages of ClearDB Documenter output documents, where relevant.
    • In an actualized Docu, the “Comparison Report - Source 1 <-> Source 2” node was renamed to “Comparison Report - Source <-> Actualized”.
    • New default color settings (customizable).
    • “CRUD1” was renamed to “CRUD1 type Matrix” in the Docu Tree and content.
    • Schema names are now shown in bold in the node names of the Observations section.
    • Improved hints of DB & PL/SQL Observations and DB Security Audit nodes.
  • Database Object Tree
    • Object loading process can now be initiated manually and automatically:
      • Manually - select items to be included in a Docu in the tree and click the “Load Objects Now” button.
      • Automatically - select items to be included in a Docu in the tree and move to the following step. The selected objects will be loaded as the first step of Docu generation.
    • New color legend:
      • black - item not checked and not loaded
      • blue (italic) - item checked but not loaded
      • blue - item loaded; will be included in the output document (shown after a manual load only)
      • red - objects in a Job/Template not available in the DB
    • New visual representation of counting of items in the tree:
      • Figures - on the right from nodes - show the number of selected items vs. total number.
      • Thousands are shown as 10k, 200k; the precise number is in the hint.
      • Figures for Schema nodes are shown in braces.
    • The total number of available objects is now shown immediately after the tree is populated, without the need to expand folders.
    • Object selection is now shown in percentage terms on the progress bar below the tree.
    • The “Load&Next” button was renamed to “Next”. Clicking this button no longer initiates the object loading process because it is now automatically run as the first step of Docu generation.
    • A new panel “DB Loading Tree - Object Loading Progress” below the object tree shows totals for processed schemas and retrieved objects in percentage terms, and status of selection/loading processes. Time of selection/loading is shown on the panel’s title bar.
    • New options “Show all tree items” and “Show checked items only” are now available on the “DB Object Tree - Object Loading Progress” panel, allowing filtering the tree by checked items. When a template is applied, these options are renamed to “Show DB and template items” and “Show template items only” correspondingly.
    • A new panel “DB Object Tree - Refresh Controls” below the object tree gives access to the “Refresh” and “AutoRefresh” features. “Validate” is no longer in use.
    • With “Show checked items only” enabled, the number of checked items is shown in blue, and the total number - in gray.
    • On clicking “Expand All” on the pop-up menu, the process of expanding nodes and loading the tree structure is now shown in percentage terms on the progress bars below the tree. You can break the process if needed.
    • Empty schemas are no longer shown in the Database Object Tree.
    • History of processing time for the Database Object Tree and document generation is now available via the “Processing History” button on the main buttons toolbar.
    • The “Exclude empty object type folders and schemas” option was renamed to “Exclude empty object type folders”.
    • Significantly sped up Database Object Tree population with the “Exclude empty object type folders” option enabled.
    • The “Exclude empty object type folders” option is now enabled by default. It was moved from Preferences to the “DB Object Tree - General Exclusions” panel.
    • If there are an excessive number of objects selected to be included in a document, a message is shown on the Database Object Tree step, warning the user that a document with over 100k objects in the Docu Tree might not open.
    • The “Load to Docu Tree” button was moved to the main buttons toolbar and renamed to “Load Objects Now”.
    • On the “Load Objects Now” drop-down menu, the “Load from File” command was renamed to “Load from Recent Files”.
    • New commands on the Database Object Tree pop-up menu:
      • “Refresh x1”, “Set to AutoRefresh”, “Remove AutoRefresh” and corresponding submenu commands such as “Folder ‘<SelectedFolderName>’”, “All”, “All Highlighted”, etc.
  • Docu Comparison Report
    • Significantly sped up process of report generation.
    • Improved look&feel and layout of the report:
      • New coloring of table rows (customizable).
      • Color legend shown above the table.
      • Ability to filter content by Non-equal properties (NEQ), inserted lines (INS), deleted lines (DEL).
    • Source 1 and Source 2 (Docu and Docu/DB) are no longer included in Docu Comparison Report generation by default.
    • Navigation is now available for source codes of the compared Docus: a scroll bar and navigation arrows.
    • The Report Tree can now be filtered by non-equal, inserted, and deleted values by enabling “Show diffs only” on the tree toolbar. The option is disabled by default. Filtering by parser and database statuses is no longer available for the Report Tree.
    • If there are no differences in “Database Properties”, this node is now hidden from the Report Tree when “Show diffs only” is enabled.
    • Nodes to which “Show diffs only” is applied are marked as [not filtered].
    • It is now possible to exclude an object creation date/ object and data object ID from the report by enabling corresponding options at “Compare | Docu Content Options | Comparison Options | Database Objects | Exclude from Comparison”.
    • The “Next” button is now disabled when same documents are selected for Source 1 and Source 2.
    • Links to the corresponding pages with DB and Parser status issues are now available in the Included Database Objects tables on all relevant pages.
    • Auto file names for a Docu Comparison Report and Docu Summary Report are now generated according to the following patterns: “docuCOMPARISON-Report_<timestamp>” and “docuSUMMARY-Report_<timestamp>” correspondingly.
    • The names of the main nodes in the trees of a Docu Comparison Report and Docu were changed:
      • “Database and Objects” to “DB & Objects”.
      • “DB&PL/SQL Observations” to “DB & PL/SQL Observations”.
      • Nodes of the compared Source Docus are now shown in regular formatting.
    • The “DB & Objects” and “DB Security Audit” nodes are now expanded in the Report Tree by default.
    • Improved coloring of the main nodes in the Report Tree.
  • Code Analyzer
    • Ability to display source code with or without formatting:
      • Code formatting can be enabled either globally or for a single object type (if applicable). “Code Formatting” and “Source Code” options were added to “Docu Content Options | Database and Objects | Object Options | Global Options/Schema Object Types”.
      • With “Code Formatting” and “Source Code” enabled (included), formatted code is shown on the main object properties page and “Code Audit” pages of a Docu.
    • Improved performance of Code Audit.
    • Max numbers are now shown correctly on the Structure View page.
  • Diagrams (Flowcharts/Call Trees)
    • An object call can now be located in the Source Code and Docu Object Tree by clicking the corresponding command on the pop-up menu of this object call.
    • Sped up Call Tree diagrams generation due to duplication exclusion.
    • The octagon with Flowchart/Call Tree limits was reduced in size, and its message was changed to: “<NumberOfBlocks>” blocks were removed: the number of Flowchart/Call Tree blocks exceeded the allowed maximum.” Paths to the location of options where diagram limits can be changed are shown in the hints.
  • Code Analyzer Options
    • Improved layout of the window with options for adding/editing/testing a naming rule pattern.
    • On the “Call Tree” page, enabling/disabling the “Data flow” option now affects the state of the “Show data flow labels” option.
  • Database Security Audit
    • The number of checks supported by the Database Security Audit feature was extended by 30 new checks, which makes 630 checks on the whole.
  • Docu Content Options
    • Changed default state of options on the Look&Feel tab: “Exclude nullable value nodes from the Docu Tree” is now enabled by default, and “Display object attributes as subnodes” is now disabled by default.
    • On enabling “Display object attributes as subnodes” on the Look&Feel tab, a message is shown warning the user that an output document may not open in case there are excessive number of nodes in the tree.
    • On the Security Audit tab of the Compare feature, “Use password from Source 1” is now enabled by default.
    • A “Clear” button was added to the Security Audit and Protect Docu tabs for ease of clearing password fields.
    • The Look&Feel tab was changed into a subtab of the General tab.
    • A “Display password” option was added to the Security Audit tab.
    • Improved layout of options on the Comparison Options tab.
  • Generation Status and Log
    • When there is not enough free space on a disk, a warning message is shown during document generation. A similar message can also be shown before the generation is started.
    • Time of preloading auto refreshed objects and loading objects that were checked but not loaded on the Database Object Tree step is now shown as a separate record in a generation log.
    • Time spent on processes that were run during document generation is now rounded to the hundredth of a second.
    • Call Tree diagram and CRUD2 type matrix generation might take much time. The following message was added to a generation log of an output document: “Attention: Depending on the size, structure, and other factors of a database, Call Tree/CRUD2 type matrix generation may take 30 min or even longer. Do not break the process!”
    • Database Security Audit Report generation might take much time. The following message was added to the generation log of an output document: “Attention: Depending on the size, structure, and other factors of a database, the audit may run 20 min or even longer. Do not break the process!”
  • Job Manager
    • An error message about a non-registered database instance (DBI) no longer appears when a job is run in trial mode for a Docu that includes only system and sample Oracle schemas.
    • The “Database Oracle Connection” step can now be accessed via the “Connection” button in the Job Manager mode.
  • Template Manager
    • Applying a template for a job is no longer possible. The Docu Template panel is unavailable in the job mode.
    • In the Template Manager, the filters were renamed to “Docu - Type 1 New -> Scratch”, “Docu - Type 2 New -> Existing”, “Docu - Type 3 Actualize”, “Docu - Type 4 Extract”, “Docu Comparison Report”.
    • “Template Object Tree - <timestamp>” is now shown on the toolbar above the Object Tree on the Database Object Tree step when a template is applied.
    • A modified template is now shown in italics in the “Loaded template” field and in the list of recently used templates.
  • Docu Manager
    • A process of adding heavy output documents to the Docu Manager is now shown in percentage terms on the progress bar. The same was implemented for docuVIEWER.
    • Free space on a disk is now counted before a document is compressed, and a warning message is shown if there is not enough space.
    • A new option “Autoclose this form after compression” was added to the Compress Selected Docu window.
  • docuVIEWER
    • Sped up opening of heavy output documents.
    • On loading a heavy output document, its title, size, type of diagrams, number of observations and Security Audit issues included are now shown in a tab while content is loaded. Also, loading is indicated with a progress icon.
  • Tray Notifications
    • Notification about Annual Maintenance & Support (AMS) renewal 30, 14, and 7 days prior to the end date of the current AMS period. Enabled by default at “Options | Preferences | Notifications”.
    • Notification about special service for users with recently purchased product license without AMS: 60 days of priority technical support and software updates/ new version upgrades at no additional cost.
    • Notification about Annual Maintenance & Support (AMS) termination.
    • Options that enable/disable notifications are located at “Options | Preferences | Notifications”:
      • “Notify about AMS renewal" for a perpetual license with AMS.
      • “Notify about License expiration” for project, trial, and extended trial licenses.
      • “Notify about purchasing AMS” for a perpetual license without AMS.
  • DB Connection Window
    • Security Audit is now automatically disabled on LDAP connection. The user is warned against using this connection by a message.
  • Generation Options
    • The “Break generation on error” option is now disabled by default.
  • GUI
    • Instant help with password requirements is now shown in all places where the user is required to enter a password.
    • Improved layout and look&feel of Instant Help and other message dialog boxes all over the application.
    • Improved layout and look&feel of the Security Audit tab.
  • OSD
    • Improved layout of the New Message window.
    • The user is now required to confirm attaching recommended files to an OSD message by entering “I AGREE” before the message can be sent.
  • Installer/Updater
    • It is now possible to delete files that remained after uninstalling ClearDB Documenter, if any, using the uninstallation wizard.
  • Preferences
    • The “Warn about not used template on Generation Status and Log page” option was renamed to “Prompt to save Document settings as a template after document generation” on the Prompts and Warnings page.
    • The “Display a total number of objects in folder” option was removed from the Database Object Tree page because database objects are now always counted in the tree.
    • On the General page, the “Open HTML with Browser” option was renamed to “Open Documents with Browser”.
  • Extract DDL
    • Improved style of formatting “Alter…Add” statements.
  • System Requirements
    • Windows Vista is no longer supported.
  • Online Help
    • Detailed description of the new features and look&feel of the Database Object Tree step.

BUGS FIXED

  • Core
    • A message about not enough DBA user privileges is now shown before the user can initiate Docu generation, and not during the generation process.
  • Docu
    • Multiple links to the same schema were removed from the “Included Database Objects” table on the DB & PL/SQL Observations page on a schema level.
    • Sched. Destination and Sched. Groups are no longer duplicated in a Docu when included as part of both schema and non-schema objects.
    • All types of diagrams in the SVG format are now opened correctly in Internet Explorer 11.
    • All properties from the system view are now shown for objects included in a Docu.
    • The “no_package” prefix was removed from the name of a standalone procedure/function.
    • Wrapped stored objects are now shown with the “Skipped” Parser status.
    • The page with observations now opens on clicking a wrapped object value in the table of totals on the Docu Overview page.
    • Empty tables of totals are now excluded from a Docu when it is generated with “Database properties only (only objects included)” enabled.
    • Clicking the “Return” button of the browser now opens the previous page on the same position where you left it.
    • Empty nodes are no longer shown in the Docu Tree when a filter is applied.
    • Links to objects are now available in the Object Privileges table.
    • Offline data files are no longer shown as available.
    • Node highlighting is now removed during an object loading process.
    • Links to non-schema objects now work correctly in the Dependencies section.
  • Docu Comparison Report
    • Invalid and disabled objects are now shown with the “invalid” and “disabled” icons in the Report Tree and tables of totals.
    • An unnecessary DB connection check is no longer performed when two Docus are compared.
    • Deleted Docus are no longer shown in the list of source Docus to be compared.
    • A Docu Comparison Report can no longer be selected in the list of source Docus of the following features:
      • Type 2 Docu Creation Mode
      • Type 3 Docu Creation Mode
      • Type 4 Docu Creation Mode
      • Compare
    • The table with totals on the “Objects in Source 1 and Source 2 - no differences” page is no longer empty for Datafiles.
  • Docu Summary Report
    • The “Not supported Docu type(s)” message is shown when a Docu Comparison Report is selected to be included in a Docu Summary Report (beta).
    • An access violation error no longer occurs when a long title is entered for a generated comparison report.
  • Code Review Rules
    • Instead of the “Exception is not handled in the BEGIN/END block”, it is now the “Exception is not handled inside the unit” code review rule that raises an error for triggers with missing exception handler block.
    • An EXIT statement is now used in the FOR loop, so a Code Review alert is no longer triggered for the EXIT statement in the Basic loop.
  • Code Analyzer
    • The “Procedure calls itself recursively” code review rule no longer raises an error for subprogram calls in which the caller subprogram name is the same as the called subprogram name. An additional analysis is now carried out for such subprogram calls: 1) parameters in a call are compatible with those of the current subprogram; 2) there is no other overloaded subprogram with the compatible parameter set. The call is now considered recursive only if both checks are positive.
    • Oracle conditional compilation directives are ignored when they do not break the statements.
    • Unicode character support in the Code Audit features.
  • Code Analyzer Options
    • If all rules of a naming rule pattern are deleted, the check box of this pattern is no longer selected.
    • A deleted naming rule pattern is no longer restored after the Code Analyzer Options window is reopened.
    • “Formatter Options | Case | Keywords | Default Case”: the “No change” option for key words formatting was removed, and “Uppercase” is now set by default.
  • Code Metrics
    • Superfluous columns are no longer added to the Code Metrics table.
  • Database Object Tree
    • An Oracle error no longer occurs when Profiles are loaded and the user has non-DBA privileges.
    • A currently loaded node in the tree no longer hides behind the progress bars.
  • Docu Content Options
    • A warning message is now displayed when a Docu name is too long.
    • On the Look&Feel tab, “Major differences” and “Minor differences” options are now combined into one option “Data differences”.
    • The “actualized” postfix is no longer added to the output file name when “Replace source Docu” is selected for an actualized Docu on the Generation Options step.
    • The reset options on the Look&Feel tab now work correctly for all subtabs.
    • Options on the Generation Options step no longer disappear after switching between generation modes.
    • Extract DDL no longer becomes disabled after cancelling its inclusion in a Docu.
  • Docu Protection
    • A Docu Comparison Report is no longer fully protected when generated using a template with Database Security Audit Report protection.
    • Enabling Docu protection with an already saved password and password hint no longer raises a warning.
  • Diagrams (Flowcharts, Call Trees, CRUD1/2 type Matrices)
    • Subprograms and tables can have same names but only in different schemas.
    • All Call Tree diagram blocks are now clickable in the window opened from CRUD2 type matrices.
    • The filter and legend are now shown for CRUD2 type matrices.
    • All blocks of a Call Tree diagram are now clickable.
    • An R&D diagram node is no longer included at the object type level if the “Object” option is disabled at “Docu Content Options | R&D Diagram | Levels”.
  • DB Connection Window
    • Users connected as SYSDBA can now select an edition created by a Normal user.
    • A scroll bar is now available to scroll down the “Last Connections” list with many database connections.
    • Database connection can be initiated by double-clicking a database connection in the “Last Connections” list.
    • On changing an Ora Client, the list of SQL*Net service names is automatically cleared along with the TNS field.
    • An error “ORA: 38802” no longer occurs on database reconnection when a non-default edition is applied.
  • Docu Manager
    • ClearDB Documenter and docuVIEWER no longer hang on opening documents with long text in the Title, Author, or Comments fields.
    • After documents are deleted from the Docu Manager, the number of existing documents is actualized in the Feature Navigator.
    • Filtering the Docu list by “Type” now works correctly in the Docu Manager and Docu Explorer.
  • docuVIEWER
    • On installing new ClearDB Documenter while another instance is running, docuVIEWER is now closed on clicking “Close all applications”.
  • Database Security Audit
    • An access violation no longer occurs on generating a Docu with Public Synonyms and Database Security Audit Report included in this Docu.
  • Extract DDL
    • DDL can now be extracted from Docus of earlier ClearDB Documenter versions.
    • Synonyms and grants are now shown in the Object DDL for a currently logged on user.
  • Generation Status and Log
    • An access violation error no longer occurs on actualizing a Docu with objects that do not include database properties.
    • Generation time no longer counts time spent on DBI registration, in case of first document generation.
    • Tree loading time is now counted correctly as part of total elapsed time of Docu generation.
  • Job Manager
    • It is no longer possible to create a job or schedule without a name.
  • Template Manager
    • A template’s status is no longer changed to “Modified” when the template is loaded.
  • Installer/Updater
    • Uninstalling ClearDB Documenter can be interrupted.
  • Preferences
    • Values entered in the “Network Resource Authentication” group box no longer disappear after the check box is cleared.
  • Main Window
    • The “Connection string” field is no longer empty when the last generated Docu is fully password protected.
    • The “Find” window no longer appears on pressing Ctrl+F3 when a text editor is not open.
  • OSD
    • A read-only file with Code Analyzer Options can now be attached to a new OSD message without raising a warning.
  • Text Editor
    • Highlighting of pasted text now works correctly in the editor.

REMOVED FEATURES

  • Database Object Tree
    • The Docu Tree was removed from the Database Object Tree step.
  • Docu
    • Links to Non-schema object types were removed from the Observations page.
  • OSD
    • The “Installed” column and “Filter” drop-down list were removed from the Updates tab.

ClearDB Documenter 4.6 (Release 1)

Apr 15, 2016

IMPROVEMENTS

  • Core
    • Password limits are increased to the minimum of 10 characters.
  • Docu
    • Improved “Introduction” section:
      • New brief description of three output documents generated by ClearDB Documenter: Docu, Docu Comparison Report, Docu Summary Report.
      • “Docu/Report at a Glance” and “Icons Legend” on one page.
    • Improved Docu header:
      • A new block that shows the number of schema and non-schema object types; generated (instant), non-generated (instant), and generated (embedded) diagrams; Observations, and Database Security Audit issues.
      • Instant help with a brief description of numbers.
      • New style of the Docu title.
    • A new page “What is checked” was added to the “DB Security Audit” section. The page shows a table of all policies used for the audit and the number of checks that each policy consists of, including a short description of each policy.
    • “What is checked” and “Why Docu Protection” are now subnodes of the “Introduction” node in the “DB Security Audit” section.
    • In the table with Code Metrics, local subprograms are now structured in the same way as the code.
    • The “Docu Summary” page was renamed to “Docu Overview”.
    • Improved look&feel of the “Docu Overview” page.
    • If a Docu is generated with instant diagrams, these non-generated diagrams are shown in the Docu Tree with an icon which is typical for them but colored in black and white. After these diagrams are generated, their icons become colored again. If you revert diagram generation, the icons will be colored in black and white again. These newly colored icons were also added to the list of all icons in the “Icons Legend” table.
    • In the Docu Tree, the connection string is now shown next to the “Docu Overview” node and totals are shown next to the “Database and Objects”, “Observations”, and “Security Audit” nodes.
    • In the Docu Tree, nodes with zero values can now be selected by a mouse click.
    • Improved look&feel of the tables on the pages in the “Observations” section.
    • After unprotecting a Database Security Audit Report from the “Docu Overview” page, you are returned back to the “Docu Overview’ page.
    • Observations are now grouped in the similar order in the GUI and Docu: DB, Parser, Naming Rules.
    • Flagged Code Metrics are now shown in the “Parser Status” section of the “Included Database Objects” table on the “Docu Overview” page.
    • Names of columns in the “Included Database Objects” table on the “Docu Overview” page are now abbreviated.
    • Links to the “Introduction” and “Why Docu Protection?” sections are now shown on the “DB Security Audit” and “Introduction” pages.
    • Hints were added to all root nodes in the Docu Tree.
    • Pages with multiple sections are now split into subpages for ease of use.
    • “Security Audit” is now called “DB Security Audit” all over documents.
    • Updated layout of pages in the “DB Security Audit” section.
    • Updated illustrations for “Docu/Report at a Glance”.
  • Docu Summary Report
    • A “DB Security Audit” table with totals is now shown on the “Docu Summary Report” page for each included Docu if a Database Security Audit was enabled for this Docu.
    • When a Docu Summary Report is opened, its default page is now “Docu Summary Report”, not “Introduction”.
    • Docu content and generation options are now shown in a separate table on the “Docu Comparison Report” page.
    • New content on the “Introduction - Docu Summary Report” page.
    • The Docu Tree is now called “Report Tree” in all types of reports.
  • Docu Comparison Report
    • If two compared Docus do not have Database Security Audit Reports, the “DB Security Audit” subnode is not added to the “Comparison Report - Source 1<-> Source 2” section in the Report Tree. In the GUI, the “Security Audit” tab is disabled and the “Source1 and Source2 Docus do not include Database Security Audit Reports” hint is shown.
    • New content on the “Introduction - Docu Comparison Report” page.
    • New color theme for a whole Docu Comparison Report.
    • New color for the selected node in a Docu Comparison Report.
    • A color legend is now shown for differences in checks in compared Database Security Audit Reports.
    • New default background colors used to show differences in Docus.
    • Improved structure of the Report Tree.
    • Improved naming of root nodes in the Report Tree.
    • The “Naming Rule Violations” filter is now called “Parser Naming Rule Violations” and is part of the “Parser” filter group.
    • New arrangement and naming of items on the “Database Properties” page.
  • Diagrams (Call Tree, Flowchart)
    • Improved look&feel of the “Source Code” panel.
    • Clicking on a block of a PNG diagram to locate a corresponding code line no longer opens a separate tab in the browser. The code line is now located on the same page.
  • Code Analyzer
    • Overloaded procedures are now analyzed correctly and shown with prefixes in diagrams and diagram trees.
    • Support for the ACCESSIBLE BY and FORCE clauses in the CREATE TYPE statement.
  • Code Analyzer Options
    • Improved string concatenation formatting.
    • In Flowcharts, “NO” arrows are now orange by default.
  • Docu Content Options
    • Improved look&feel of the “Docu Content Options” step for the “Compare” feature and Type 3 Docu creation mode.
    • Improved layout of the “Source Docu” step.
  • Database Security Audit
    • “Database Security Audit” is enabled by default if the user has all the required privileges.
    • ClearDB Documenter checks a logon user and DB properties for the required privileges to make the “Database Security Audit” feature fully available for use.
    • Trial mode limitations in a Database Security Audit Report.
      • "Trial version" is shown instead of each 2d, 3d, and 4th checks in the “Summary” table; password cracker and code analysis in the policies 19 and 20; and check titles.
      • “Description”, “Why is this issue blocks”, and a table with details are not shown.
    • The “Security Audit” tab is indicated with a stop sign if the user does not have enough privileges.
  • Docu Protection
    • A previously used password and hint are automatically inserted in the corresponding fields on the “Protect Docu” and “Security Audit” tabs and applied for the generated Docu. If necessary, you can remove them and apply a new password and hint.
    • If a source Docu is password protected or has a Database Security Audit Report, the actualized Docu will be also password protected.
  • Docu Manager
    • Updated types of documents in the filter for the Docu list in the “Docu Manager” and “Docu Explorer”.
    • If a password protected Docu is saved as a separate file using “Save As”, this file will be password protected as well.
    • Improved look&feel of the “Docu Protection” window.
    • Improved look&feel of the “Docu Summary Report” window.
  • docuVIEWER
    • Support for Docu Summary Report generation.
    • In a Docu that includes a Database Security Audit Report, clicking in the “DB Security Audit” table on the “Docu Overview” page opens the “DB Security Audit” page where you can enter a unique password to unprotect the report.
    • Docu Summary Reports generated in docuVIEWER and Docus password protected in docuVIEWER now have the version of currently installed ClearDB Documenter in the “Version” column in the Docu list.
    • docuVIEWER now has its own standalone Online Help that can be opened by pressing F1 or clicking “Help” on the main menu.
  • DB Instance Licensor
    • The user is now prompted to register a database instance on clicking the “Start” button right before Docu generation. No database instance registration is needed to generate a Docu with the pre-installed Oracle schemas (HR, SCOTT, etc.)
  • DB Connection Window
    • Support for all types of 32-bit Oracle Client.
  • Main Window
    • Source of updates is now shown in the “OSD - Online Support Desk” group box.
    • The number of a selected Docu creation mode is now shown in the “Feature Navigator”.
  • GUI
    • Support for password unmasking.
  • System Requirements
    • Updated system requirements for ClearDB Documenter.
  • License Key
    • Annual Maintenance & Support coverage is now part of a project license.
  • About
    • The “License Agreement” file is now in the RTF format.
  • Online Help
    • Updated version of Help with new topics and more detailed description of features.

BUGS FIXED

  • Core
    • The backup folder is now validated on generating an actualized Docu (Type 3 Docu creation mode).
  • Docu
    • Links in the “Valid” column of the “DB Status” group in the “Included Database Objects” table now work correctly on the “Docu Overview” page.
    • Correct values are now shown for total objects included in a Docu.
    • The order of items in the Docu Tree now corresponds with the list of options on the “Observations” tab.
    • On the “Docu Summary” page, the “DB Security Audit” table now correctly shows totals for the whole Database Security Audit Report.
    • A Docu can now be generated with ER diagrams when constraints are disabled.
    • Expand/collapse buttons now work correctly on all pages of the “Observations” section.
    • Invalid “Materialized Views” are now shown with the correct DB status and are not included in the list if the Docu Tree is filtered by “DB Status Invalid”.
    • The Docu Tree is now filtered correctly when the “Security Audit” filter is applied.
    • Values in summary tables of Observations and links to corresponding nodes in the Docu Tree are no longer mixed up.
    • When a naming rule is applied, the correct value “VALID” is now shown in the DB status of an object.
    • Improved look&feel of the “Code Review” page of a script and stored object.
    • Clicking on links in the summary table of Observations now opens the corresponding child page with observations details.
    • The “Parser Error” page now has a correct structure: the “Source Code” table goes after the table with parser error information.
    • Objects with invalid dependencies are now shown in the list of naming rule violations.
    • The “Properties” section is no longer empty for “Sched. File Watchers”.
    • “Policy Name” and “Audit condition” of the “Unified Audit Policy” are no longer duplicated in the “Properties” table.
    • The table with object type dependencies no longer has broken rows.
    • Rationale is now shown for the corresponding Code Review rule in the bottom panel.
  • Docu Summary Report
    • Schema links in Docus included in a Docu Summary Report are internal and lead to a corresponding page within the report.
    • A Docu including only DB properties is now shown in the Docu Tree if this Docu is part of a Docu Summary Report.
    • On the “Docu Summary Report” page, in the “Included Docus” table, schema and non-schema objects now have links to corresponding pages within the report.
    • In a Docu Summary Report for multiple Docus, correct DB types are now shown for all the included Docus.
  • Docu Comparison Report
    • On the “Docu Comparison Report” page, the Docu title, author, and comments in the “Comparison Report description” table are taken from the “Generation Options” page of the “Compare” feature.
    • If Source 1 or Source 2 is a database, not a Docu, it is now shown with a proprietary icon.
    • The total number of objects with observations is now counted correctly for the observations summary table.
  • Diagrams (Call Tree, Flowchart)
    • The “Call Tree” link is now unavailable for objects without Call Trees.
  • Code Analyzer
    • Functions called from the DML statements are now shown in the Call Tree diagram.
    • The ACCESSIBLE BY clause is no longer accepted more than once in the unit.
  • Code Analyzer Options
    • On the “Code Review Options” page, the corresponding rationale is now correctly located for the rule you are searching for.
    • The “Reset” and “Reset current page to default” now work correctly on all pages where used.
  • Code Review Rules
    • The “Commit and Rollback are allowed if pragma is used” rule now raises violation if a PL/SQL block or Trigger have the “Commit” or “Rollback” commands without “PRAGMA AUTONOMOUS_TRANSACTION” in the declaring part.
    • All types of observations are now counted correctly.
  • Code Metrics
    • The “Code Metrcs” link is now unavailable if there is no relevant data in the table.
  • Docu Content Options
    • Renamed options in the “Include Comparison Report” group box on the “Common” subtab of the “Comparison Options” tab.
    • Instant help describing the “Overview Object Settings” feature was added to the “Object Options” subtab of the “General” tab.
    • The “Output folder” field is now populated with a default value when a new Docu is created.
    • When a template is loaded for the “Comparison” feature, the “Output file name” field no longer becomes empty on the “Generation Options” page if Docu options are set to default and “Use title as file name” is enabled.
    • Correct numbers of code review rules are now shown on the “Code Audit” tab and in “Code Analyzer Options”.
    • A warning message is now shown if a user enabled the “Protect Docu” or “Security Audit” feature on the corresponding tabs but did not enter a password and tried to switch to another page.
    • The “Security Audit” feature is always disabled if a Docu is generated without connection to a database.
    • A password protected Docu can now be unprotected when selected as a source Docu in Types 2, 3, 4 Docu creation modes, DDL extraction, and comparison feature.
    • When a template is loaded and password hint is changed, its length is now checked correctly.
  • Docu Manager
    • All columns in the Docu list are now populated with relevant information (connection string, Docu type, author, etc.).
    • An error no longer occurs on breaking the Docu protection process.
    • When trying to open a protected Docu in a standard HTML browser selected in “Preferences”, a message is now shown informing the user that docuVIEWER is required to view and open the Docu.
    • A Docu no longer disappears from the Docu list in the “Docu Manager” and “Docu Explorer” after password protection.
    • An access violation error no longer occurs after a Docu is password protected.
    • An error no longer occurs on breaking the Docu protection process.
    • If a Docu Summary Report is selected to be included in a new Docu Summary Report, the “Not supported Docu type(s)” message is shown.
    • A protected Docu is now always opened in docuVIEWER, regardless of which browser is set in “Preferences”.
    • Autofit now works correctly when sorting is applied to the Docu list.
  • docuVIEWER
    • The License Agreement is shown on the first startup of the application.
    • The “DB Security Audit” table on the “Docu Summary” page now shows results for the whole Database Security Audit, not part of it.
    • Clicking on an object type in a Docu included in a Docu Summary Report now opens a corresponding page of that Docu in a separate tab.
    • If “Replace diagram permanently” is not enabled, an instant diagram can be either reverted or saved by clicking the corresponding options at the top of the diagram page.
    • The “Regenerate” button is no longer shown on the diagram page without data for diagram generation.
    • If docuVIEWER is running during ClearDB Documenter installation, it is now shown only once in the list of applications that must be closed to continue the installation process.
  • Database Object Tree
    • The “Non-schema objects” node is no longer shown when the “DB properties only (no objects included)” option is enabled.
    • With the “Hide system schema” option enabled, none of the system Oracle 12c schemas are shown in the Database Object Tree.
    • Improved look&feel of the items in the “Docu Tree” panel.
  • DB Connection Window
    • Generating a new Docu based on an existing one (Type 2 Docu creation mode) no longer raises an error on database connection.
    • After a successful connection to a database, the options under “Connection Type” now become unavailable.
    • The current edition is now always shown under “Connect to”.
    • The order of columns can now be changed if necessary.
  • DB Connection Settings
    • An Oracle client is now detected correctly if two Oracle clients - 32-bit and 64-bit - are installed on one PC.
    • Connection to an Oracle database no longer breaks when ClearDB Documenter is running.
  • Generation Status and Log
    • Docu generation process no longer breaks if the “Create Preview in background” option is enabled on the “Docu Tree Preview” tab.
    • The generation log now shows correct values of database instances available in the application.
    • Docu generation no longer breaks when one object is selected twice - as a schema and non-schema object.
  • Job Manager
    • Job execution is no longer interrupted by a warning message about the inability of Internet Explorer to view diagrams in the SVG format.
  • GUI
    • The progress bar on the “Generation and Log” step no longer shows 100% when the last objects in the list are processed on Docu generation.
    • When installing or updating ClearDB Documenter, all menu elements (buttons, menu, Feature Navigator) become unavailable on “Sample Docu” extraction.
    • The “Database Object Tree” step no longer shows incorrect title when “Skip connection” or “Auto connection” are enabled.
    • Disabling check box of a tab or group box now makes all related options unavailable.
  • Extract DDL
    • An error no longer occurs when the Docu Tree is loaded with the selected database objects.
    • The last used output file options defined for DDL extraction are now saved and applied on next startup of the application.
  • Templates
    • Templates can now be loaded without any errors.
    • “Autostart generation after loading” now works correctly when a template is applied.
    • Template content can now be viewed without raising an error.
  • Preferences
    • The state of the “Prompt on editing Code Review options” check box is saved and is not changed on next startup of the application.
    • A warning message is shown on clicking “OK” or “Apply” on the “Internet Connection” page with the empty “Address” and “Port” fields.
  • Text Editor
    • The search option now works correctly with “Ignore case” enabled.
    • An error about missing preferences parameters no longer occurs for the “Find Text” feature.
  • DB Instance Licensor
    • Autofit now works correctly for columns in the “ClearDB Documenter Registered Instance Overview” window.
  • Main Window
    • If the last generated Docu was removed from the “Docu Manager”/”Docu Explorer” or deleted from the file system, it is indicated with “removed from Docu Manager/Docu Explorer” or “Docu deleted” respectively in the main window under “Last Generated Docu”.
  • OSD (=Online Support Desk)
    • When the Conquest Software Solutions website is unavailable, the “No access to Conquest server” message is shown in the main window.
    • Attachments to OSD messages can now be opened without raising an error.
    • Sorting OSD messages by “Received” now works correctly.

REMOVED FEATURES

  • Docu
    • The “Regenerate” button was removed from the diagram page of an object if this object doesn’t include any diagrams.
    • Links to “Actualized” were removed from the description on the “Introduction” page of an actualized Docu.
    • On the “Observations” page of a specific object type, the “Schema/Non-Schema Object Sub-Total” line was removed from the “Included Database Objects” table.
    • The “Category” column was removed from the “Summary - unsafe items/areas detected in the database” table on the “DB Security Audit” page.
    • The “Filter” column with check boxes was removed from the “DB Security Audit” table on the “Docu Overview” page.
    • Links to non-schema objects were removed from “Overview Graphs”.
  • Docu Content Options
    • The “Use lite style for Observation Report” option was removed from the “Observations” tab as the lite style feature is no longer available for use.
  • Database Security Audit
    • The “Encrypt Security Audit Report by password” option was removed from “Docu Content Options -> Comparison Options -> Security Audit” because a Database Security Audit Report is always password protected by default.

ClearDB Documenter 4.5 (Release 1)

Dec 16, 2015

NEW FEATURES

  • NEW: “Database Security Audit” is checking more than 600 potential security risks for an Oracle Database (up to 12c). A detailed report summarizes all failed checks. The output is grouped into POLICIES and CHECKS and provides detailed information about observed issues. The generated Security Audit Report is protected with a password by default.
  • NEW: docuVIEWER - an embedded tool to view and manage numerous Docus (database documentation) generated by ClearDB Documenter. Gives access to the whole list of generated Docus; views Docus protected with a password; instantly generates diagrams and regenerates the existing ones at all levels; and much more. Can be downloaded as a FREE standalone app as well.
  • NEW: A one page Docu Summary Report with a concise overview of Errors, Alerts, DB Anomalies, DB Security Audit warnings, etc. contained in multiple generated Docus.
  • NEW: Protection of a complete Docu (encryption and password) or its part (Security Audit Report).
  • NEW: Checks naming conventions of 59 Oracle database object types.
  • NEW: Comparison of the Security Audit data in one report.

IMPROVEMENTS

  • Core
    • Support for non-schema object types: SCHEDULER DESTINATION and SCHEDULER GROUP.
    • Support for DATAFILE as a separate non-schema object type.
    • Added icons for a Docu Summary Report and all types of Docus: a standard Docu, a Docu including a Security Audit Report, a fully protected Docu, a Docu including a comparison report. The icons are now shown in the Docu list in the “Docu Manager” and in the “Docu Explorer” of docuVIEWER.
    • The log file now includes more detailed information about the database object populating process when it is running in the auto-sync mode, and the “Preloading objects from the database” message is shown in the progress bar.
    • Significantly improved the “Generation Options” page layout.
    • Increased speed of observations generation: 300% faster.
    • Improved generation log:
      • A new option “Limit number of log files to [N]” was added to the “General” page in “Preferences”, allowing you to set a number of generation log files you want to store. The default number of log files is 20.
      • After successful Docu generation, a log file is renamed to <DocuName>.log and moved to the folder where other Docus are stored. Only broken or failed log files are stored in the “Generation Logs” folder.
      • A file with current system information is now available in the folder where generated Docus are stored.
      • A timestamp of Docu generation is now shown in the log file.
    • A pop-up window now appears on the first start of the application showing if there are any updates available. It is shown only once right after closing the “Release Notes” window.
    • Improved consistency of all confirmation messages all over the application.
  • Documentation
    • CRUD2 type matrix is now included in a Docu at the database level.
    • “Observation Report” is now split by object types at the schema level.
    • All non-schema objects are now grouped under a “Non-schema objects” node in the “Docu Tree”.
    • “Schemas” and “Non-schema objects” are now grouped under “Database and Objects” in the “Docu Tree”.
    • New style and look&feel of the report titles in the “Docu Tree” and Docu content.
    • Improved look&feel of the “DB Type Objects List” tables.
    • If the number of diagrams that can be generated is exceeded in a generated Docu, the maximum and total number of diagrams are shown at the top of the page. Point to the instant help icon to see a hint with an explanation of what should be done if the number of diagrams is exceeded.
    • Local subprograms are now shown as child items of their parent subprogram in the tree of a Flowchart diagram.
    • A “No matching items found on data collecting” hint is now shown for unavailable nodes in the “Docu Tree”.
    • Objects in CRUD matrices can now be filtered by Update, Delete, Create, and Read values.
    • “Data Redaction Policy” is now shown as non-schema object under “Policy Group(s)” in a Docu, “DB Object Tree”, “Naming Convention”, and “Object Options”.
    • Ability to filter the “Docu Tree” by multiple conditions.
    • The following message is now shown to the user in case Flowchart generation fails: “Flowchart generation has failed. Reduce the maximum number of diagram nodes on the "Flowchart" page in "Code Analyzer Options" and try again.”
    • Changes on the “Observation Summary” page:
      • “Include schema object types” was changed to “Detected non-schema object types”.
      • “Included non-schema object types” was changed to “Detected non-schema object types”.
      • The “Created” column was deleted from the schema object types table.
  • Diagrams (R&D, ER)
    • Zooming can now be specified separately for each type of a diagram.
    • Ability to apply diagram view settings to all diagrams.
    • The number of attempts to generate each diagram was increased so that generation will not be failed by external applications.
  • Code Analyzer
    • Support for interval expressions in conditions.
    • An error no longer occurs on analyzing a script with “OPAQYE TYPE”, because such a type has been excluded from the list of the supported objects and it is now skipped by the parser.
    • If there are any parser errors in the analyzed code, all these errors are now shown to the user, which significantly facilitates the error handling process.
    • Analysis of wrapped stored objects is now skipped on Docu generation, and “Skipped (wrapped object)” is shown in the Docu log.
    • A streaming clause is now supported when specified after the PIPELINED keyword.
    • Improved formatting of CASE expressions.
  • Code Metrics
    • Instead of “GLOBAL”, the object name is now shown for a script of an analyzed package/type body/specification.
    • “/”, which typically follows END in a stored program, is no longer considered as a statement in metrics calculation.
  • Code Review
    • The “Exception is not handled inside the unit” and “Exception is not handled in the BEGIN/END block” rules now raise errors when there are exception blocks in the package that is analyzed.
    • Improved look&feel of the “Code Review Options” page in “Code Analyzer Options”.
    • Trigger names are no longer duplicated.
  • Code Review Rules
    • A new Code Review rule “Identifier redeclared” was added to the list of rules.
  • Compare Documentation
    • Three more comparison sections: “Database Objects Comparison Report”, including database properties; objects missing in Source 1 and in Source 2, objects that exist in Source 1 and Source 2 with or without differences; “Observations Comparison”; and “Security Audit Comparison Report” including checks missing in Source 1 and Source 2, checks that exist in Source 1 and Source 2 with or without differences.
    • The “Click Next to select a DB for comparison” message is now shown when the user tries to select a database for comparison.
  • Object Type Options
    • A new “Include in R&D diagram as object” option was added to the “Schema Object Types” section.
    • Global options at “Docu Content Options -> Database and Objects -> Object Options” are now synchronized with the corresponding options on all object type pages if set to “Include/Exclude”. The options are not synchronized if set to “Use individual Object Type settings”.
    • “Original Source Code” was renamed to “Source Code” throughout a Docu to be consistent with the application’s UI.
  • Docu Content Options
    • Significantly improved functionality and layout of the “Docu Content Options” step:
      • Added a new “General” tab with two subtabs: “Diagram Creation Timing” and “Protect Docu”.
      • The new “Diagram Creation Timing” subtab allows you to select a diagram generation type: “Embedded Diagram” (default) - diagrams will be a part of the generated Docu; “Instant Diagram” - all data for diagram generation is included in the Docu but for the diagrams themselves; diagrams can be further generated using docuVIEWER.
      • The new “Protect Docu” subtab allows you to protect a Docu (encryption and password). You can enable/disable this feature by selecting/clearing the check box in the caption of the subtab.
      • Renamed the “Documentation Options” tab to “Database and Objects”.
      • Changed and renamed the “Observation Report” subtab to the “Observations” tab.
      • Added a separate “Security Audit” tab, allowing you to define Security Audit settings. The feature is available if you have enough privileges. The availability information is shown on clicking the “Instant Help” button. The “Security Audit Report” is protected with a global or Docu specific password.
      • Added an ability to include/exclude “Code Audit”, “R&D Diagram”, “ER Diagram”, “Summary Graphs”, “Observations”, and “Security Audit” in/from generation by selecting/clearing a corresponding check box in the caption of a tab/subtab.
      • “Summary Graphs” and “Security Audit” are disabled by default, “Observations” - enabled.
      • Removed the “Generate Observations report only” options from the “Observations” tab.
      • A warning message is shown on enabling “Code Audit” if the Parser options are disabled on the “Observations” tab.
  • Database Connect
    • Updated look&feel of the “Oracle Database Logon” window:
      • The “Oracle Database Logon” step is now called “Oracle Database Connection”.
      • The “Auto logon” option is now called “Auto connection”.
      • Improved layout of the window.
  • Database Object Tree
    • Improved look&feel of the “DB Tree Controls” and “DB Tree Options” panels on the “Database Object Tree” step.
    • A total number of objects selected to be included in a Docu is now shown at the bottom of the “Docu Tree” pane.
  • Docu Manager
    • When zipping Docus, the file name is now shown in the folder explorer when a user is trying to select a different folder as a target location.
    • A Docu can now be protected with a password. Click “Password Protect Selection” on the pop-up menu and set a password to the selected Docu.
    • New icons were added to the Docu list indicating a Docu Summary Report and all the types of generated Docus.
    • A progress bar is now shown on deleting a large number of Docus in the “Docu Manager”.
  • Generation Status and Log
    • The number of collected and documented objects is now shown to the user during the Docu generation process.
    • Summary information - totals for schemas and non-schema objects - is now shown in the log.
  • Preferences
    • The “Database Object Tree” page was added to “Preferences(Job)”, which provides an ability to customize the “Database Object Tree” page for a job.
  • Oracle Database Connection/Security Audit/Docu Protection
    • A password value can now be viewed for a newly added password.
  • Main Window
    • “Check for Updates” and “Check for Messages” menu items were added to the “Help” menu.
  • DB Instance List
    • An instant help describing security issues for DBI registration was added to “Oracle Database Connection -> Registered Database” and “Help -> Registered Databases -> Open List”.
  • Graphical User Interface
    • Improved and updated highlighting all over the application.
  • License Key
    • Added a tray notification about the upcoming license key or AMS expiration.
  • About/License Key/Main Window/Preferences
    • Improved look&feel of the license section.
  • About
    • Project license information is now shown in the “Licenses” table.
  • Online Help
    • A new topic “Moving ClearDB Documenter from one PC to another” in the “Quick Overview” chapter.
    • Updated and more detailed description of the “Docu Content Options” step for all types of Docu creation modes and features in the “The Docu Content Options step” chapter.
  • ReadMe/Online Help
    • Updated system requirements for ClearDB Documenter.

BUGS FIXED

  • Core
    • An “Out of memory” error is no longer raised on generating a Docu with a great number of objects.
  • Code Analyzer
    • Support for outer join operators after the column names in WHEN and THEN clauses.
    • Formatting of ORDER BY and FOR UPDATE clauses now works correctly.
    • Text literals of the “nq’quote_delimiter <text> quote_delimiter” are now recognized correctly in the SELECT statement.
    • The “Procedure calls itself recursively” rule now works correctly.
    • “.” is now parsed in the PATH clause of the “XML_table_column” clause of the XMLTable function.
    • Comments to non-supported statements are now removed after analysis.
  • Code Analyzer Options
    • The status of the “Readability” check boxes now changes to “all selected” after loading a file with previously saved options, where all “Readability” rules are selected.
    • The “Reset to default” option now works correctly on all pages of “Code Analyzer Options”.
    • Fixed links to open OSD and the user’s email client in the “Information” dialog box of a protected “Code Analyzer Options Profile” at “Code Analyzer Options -> Profile Owner Information -> Lost Password”.
  • Code Metrics
    • The RETURN command is now counted in the “Return Points” of a subprogram if this command is in the exception block of the code.
    • All trigger and type body code lines are now taken into account in Code Metrics.
    • One or more empty lines inside a multi-line comments are no longer considered as empty lines of code.
  • Documentation
    • The “Invalid Objects Dependencies” folders now show the correct number.
    • With the “Include Footer to Documentation” option enabled, the footer is now shown on all pages of the generated Docu.
    • An empty line is no longer shown in the list of parser errors.
  • Docu Content Options
    • Default values are now shown for Global options instead of empty combo boxes at “Docu Content Options -> Database and DB Objects -> Object Options”.
  • Compare Documentation
    • After comparing two Docus, the “Docu Tree“ now shows the Docu titles, not file/folder names.
    • Clicking disabled non-schema objects in the “Observation Report” now opens the corresponding object nodes in the “Docu Tree”.
    • Policies are no longer shown as missing in Actualized/Source 2 in the "Comparison Docu", when the “Don’t include any new or missing DB objects” option is enabled at “Docu Content Options -> Comparison Options -> Database Objects -> Comparison with Database Options”.
  • Database Connect
    • On the “Oracle Database Connection” step, the “Disconnect” button is now unavailable if a user selects a database without connection.
  • Database Connection Options
    • An Oracle client is now detected correctly if two Oracle clients - 32 bit and 64 bit - are installed on one PC.
  • DB Object Tree
    • Splitters no longer break after hiding/unhiding the “Database Controls Panel” in “Extract DDL”.
  • Job and Schedule Manager
    • The “Calendar” wizard now shows correct time and date.
  • System Information
    • TNS file names are now shown correctly on the first opening.
    • Oracle Client version is now shown correctly for Oracle Client 12.
  • About
    • Improved layout of the “Licenses” section.
    • An error no longer occurs on opening the License Agreement from the “About” window.
    • The “Technical Support” web page now opens correctly on clicking the “Read more” link for “Tech-Support primary”.

REMOVED FEATURES

  • Core
    • The “Disable non-compatible documentation generated by another version of ClearDB Documenter (shown as disabled in the list)” option was removed from the “Source 1 and Source 2” step.
    • Removed the “FAQ” menu item from the application at “Help -> Web Support -> FAQ”.

ClearDB Documenter 4.0 (Release 7)

Jun 18, 2015

IMPROVEMENTS

  • Core
    • Increased speed of documentation content generation: 60-80% faster.
    • Increased speed of the Observation Report generation: 2-3 times faster.
    • Increased speed of collecting data from a database for documentation: 40% faster.
    • If query execution takes too much time during the documentation generation process, 10, 20, or 30 minutes, ClearDB Documenter automatically reconnects to the DB session without breaking the process of documentation generation.
    • Updated system requirements for ClearDB Documenter use.
  • Diagrams (R&D, ER, Flowchart, Call Tree)
    • New version of graphical engine enables generation of large diagrams and significantly accelerates the process of documentation generation especially for big databases.
    • Increased speed for R&D diagram generation: 5-6 times faster.
    • The “Include synonyms” option has been added to the “R&D Diagram” subtab at “Docu Content Options -> Documentation Options”. With this option disabled, synonyms are not included in the generated R&D diagram, which significantly reduces its size.
    • The “Limit the number of diagram nodes to the specified maximum” option has been added to “R&D Diagram” and “ER Diagram” subtabs at “Docu Content Options -> Documentation Options”, allowing to limit the content of R&D/ER diagram by the number of elements.
    • Behavior of graphical engine can be controlled: if a diagram cannot be generated, the diagram generation process can be stopped without affecting documentation generation.
    • The default number of elements in the R&D and ER diagrams has been reduced to 200.
    • The message has been added prompting a user to decrease the number of blocks in “Code Analyzer Options” and start documentation generation once again.
  • Code Analyzer
    • Support for a new clause ACCESSIBLE in Oracle 12.
    • Support for the CREATE DDL event in the trigger on schema.
    • Support for the DETERMINISTIC keyword for a procedure in the package specification.
    • Support for the XMLNAMESPACES function without values of the expression list.
    • Support for the DOUBLE PRECISION type for parameters and variable.
    • Oracle OPAQUE VARYING statement is skipped to avoid the parser error.
    • A local variable or a parameter are now omitted from the Call Tree diagram.
    • The keyword NAME can now be used as an identifier.
    • Two new Code Review rules called “Unreferenced local variable” and “Unreferenced package/type method or standalone subprogram” have been added to the “Program Structure” node in the list of rules at “Code Analyzer Options -> Code Review Options”.
    • Two new Code Review rules called “”Magic” hard-coded literal numeric value is used in the WHERE clause of the SQL statement” and “”Magic” hard-coded literal string value is used in the WHERE clause of the SQL statement” have been added to the “Maintainability” node in the list of rules at “Code Analyzer Options -> Code Review Options”.
    • “PIVOT_CLAUSE” and “UNPIVOT_CLAUSE”are now successfully parsed with both orders of clauses being used: 1)”query_table_expression”; 2)”pivot_clause”; 3)”alias” OR 1) “query_table_expression”; 2)”alias”; 3)”pivot_clause”.
    • “MODEL_CLAUSE”, “ROW_LIMITING_CLAUSE”, “ROW_PATTERN_CLAUSE”, “PARTITION_BY”, “DIMENSION”, “OFFSET”, “FETCH” are now correctly processed being part of the SELECT statement.
  • Code Analyzer Options
    • The “Combine consecutive "subprogram call" and "assignment" blocks” option has been added to “Code Analyzer Options -> Diagram Options -> Flowchart” (main buttons bar “Options -> Code Analyzer Options”). With this option enabled, all similar commands in the code (if any) are shown in one flowchart block. This option is enabled by default.
    • The “Model 2” option in the “COM (Comments) Parameter of Maintainability Index Used in the Calculation Formula” group is now enabled by default at “Code Analyzer Options -> Code Metrics Options”.
    • Detailed description of “CRUD1” and “CRUD2” has been added to “Read More” on the “Diagram Options – CRUD” page.
  • Code Metrics
    • On analyzing/formatting code, two empty lines between comments are reduced to one line. One empty line between comments remains unchanged.
  • Documentation
    • The “All diagrams” button is removed from the toolbar of Flowchart and Call Tree diagrams in documentation if only one diagram is shown.
    • All arrows are now shown correctly on the R&D diagram in documentation.
  • Main Window
    • Major changes in the UI:
      • The “Open Documentation with expanded DB Objects Tree” group box on the “Code Audit” subtab has been moved to the “General Options” subtab.
      • The “Open Documentation with expanded DB Objects Tree” group box has been renamed to “Documentation Tree State on Opening”.
      • A set of options in the “Documentation Tree State on Opening” group box has been changed to “Expand topmost nodes only” and “Collapsed”.
      • The “Expand Topmost Nodes Only” icon has been added to the toolbar on the “Docu Tree Preview” tab.
    • The “Code Analyzer Options” check box has been renamed to “Code Audit” on the “Source Documentation” step.
    • User interface enhancement.
  • Generation Status and Log
    • With auto-sync mode enabled to populate the “Documentation Tree”, the “Preloading objects from the database” text is now shown in the progress bar and the preloading process details are shown in the log.
    • If the documentation generation process takes a long time, the user is informed about the schema being generated and the time spent. This information is shown in the generation log and is highlighted in blue.
  • DB Instance Licensor
    • To avoid confusion, an error message is displayed if a user tries to register a DBI with an already used password.
  • Docu Content Options
    • The “Hide Overview” check box has been renamed to “Hide Introduction” on the “Docu Tree Preview” tab of the “Docu Content Options” step. This option is disabled by default.
  • Online Help
    • Updated version of Help with new topics and more detailed description of features.
  • Preferences
    • The “Database Object Tree” page has been added to “Preferences – Jobs and Schedules”, which allows customizing the “Database Object Tree” for a job.
  • About
    • The “License Agreement” file is now in the RTF format.

BUGS FIXED

  • Core
    • ClearDB Documenter no longer closes on generating a Flowchart diagram.
    • With the “Check query execution idle time on generation” option enabled at “Preferences -> Session”, a warning message is correctly displayed if a documentation generation process is too long.
  • Documentation
    • All “New Docu” options are now listed on the “Documentation Summary” page.
    • A correct number of objects in folders is now shown, when a filter is applied to the “Documentation Tree” and the number of filtered objects differs from the total number of objects.
    • A correct number of schemas is now shown in the “Documentation Tree” when the “Exclude 0-value nodes in the Documentation Tree” option is enabled at “Docu Content Options -> Look&Feel”.
    • Drag&drop can now be applied to unpinned Call Tree diagrams called from “CRUD”.
  • Code Analyzer
    • Script text is now correctly formatted when an SQL statement hint and a user comment are inserted in a single line in the code.
    • Parser stack no longer overflows on a large number of concatenations.
    • Correct grammar is now used for the FOR expression.
    • Fixed syntax mistakes connected with processor directives in the procedure variables list in the working production code.
    • The “Access Violation” error no longer occurs when analyzing the TRIM(TRAILING <character> FROM <expression>) function call
    • SVG (Scalable Vector Graphics) image format can now be selected to view diagrams when Internet Explorer 8 is installed on the PC.
  • Flowchart Diagram
    •  Flowchart diagram is now generated for all types of objects.
  • Connection Settings
    • When a user changes a type of creation mode and the database connection, the application automatically reconnects to the necessary database without breaking the documentation generation process, and errors no longer occur.
    • With the “Skip connection” option enabled, the “Start” button is disabled, which does not allow generating documentation.
    • An error no longer occurs on opening the “Last Connections” tab if the Oracle Client is not installed and there are non-registered databases.
  • Database Logon
    • With the “Skip connection” option enabled on the “Oracle Database Logon” step, the “Docu Content Options” and “Generation Options” features are now available for use, which allows faster software investigation without the need to connect to a database.
  • Database Object Tree
    • On the “Database Object Tree” step, when generating documentation in Type 2 generation mode, selected objects are no more doubled and are shown correctly in the “Documentation Tree”.
    • Auto-sync selection is correctly saved/restored with the “Load objects from last generation” option enabled or when templates are used.
  • Docu Options
    • Fixed a message displayed when synonyms are included to the documentation but excluded from the R&D diagram.
    • A default file name is now automatically shown in the “Title” field once the “Use title as file name” option is disabled on the “Generation Options” step.

REMOVED ISSUES

  • Core
    • ClearDB Documenter no longer supports CHM documentation format, i.e. documentation in CHM format cannot be generated, recreated, or selected for generation. Old documentation in CHM format is viewed in gray and is not available for use. The “Save output as” filed has also been removed from the “Generation Options” step as there is only HTML format available in the application.
    • Templates can no longer be loaded after trial period is over.
  • Main Window
    • The “Fully expanded” check box has been removed from the “Documentation Tree State on Opening” group box on the “Generation Options” tab of the “Generation Options” step. Now, to expand all the nodes, use the similar option in the documentation itself.

ClearDB Documenter 4.0 (Release 6)

Mar 26, 2015

IMPROVEMENTS

  • Core
    • New option to include synonyms to "R&D (References and Dependences) Diagram". The option is disabled by default to reduce possible impact on performance of the diagram generation process.
    • Improved handling of unexpected behavior of graphical engine used for Flowchart, Call Tree, R&D and ER Diagrams generation.
    • Generation of “R&D Diagram” at the database level is disabled by default.
    • Prompts to revert all settings to default on changing documentation creation mode.
  • Database Instance Registration (=DBI)
    • New option to remember the user entries (except password) for later reuse.
    • Improved validation of the “OK” button on filling up the form.
    • Improved look&feel and content of the message about DBI pre-registration.
  • Database Object Tree
    • Improved performance of populating the tree with database objects.
    • Improved the content and look&feel of the validation report.
    • Support for standard Windows tree shortcuts.
    • Improved content of instant-help for the “Auto-sync” and “Refresh” features.
  • Oracle Database Logon
    • Simplified sorting data in the “Last Connection” list. First click the column’s title sorts data ascending, second click sorts data descending. Hold down Shift to sort data by multiple columns.
    • Displays the current connection to a database, if any.
    • Improved location of the “Auto-login” checkbox.
  • Documentation
    • Improved the content of actualized documentation (“Creation Mode Type 3”).
    • Improved content and look&fill across documentation.
  • Documentation Manager
    • HTM file extension shown in the Format column is renamed to HTML.
    • Improved hint for the “View Documentation” feature.
  • Job Manager
    • Improved changing database connection for an existing job.
  • Documentation Options
    • Improved labels for a set of controls.

BUG FIXES

  • Core
    • After pausing the process of documentation generation, the misleading message window about a long running process appeared.
    • Could run a job without DBI registration.
    • Documentation with “Creation Mode Type 4” (Extract a subset) could not be generated.
    • Did not reconnect to a proper database on switching from “Creation Mode Type 1” (create from scratch) to “Creation Mode Type 2” (based on another documentation).
    • An “Access Violation” error could be raised on fast multiple clicking the “Next” button.
    • Each documentation creation overwrote the default “Code Analyzer” options.
    • Attempted to make unnecessary changes in the read-only “Code Analyzer” options.
    • Could not disconnect properly if connection to a database was done by using an old version of Oracle Client.
    • Could not generate documentation if the documentation output folder did not exist and the user had no administration privileges in Windows.
    • There was wrong object selection if the database connection was not changed on switching from “Creation Mode Type 2” (based on other documentation) to “Creation Mode Type 1” (create from scratch).
    • Generate of documentation with the enabled "Extract DDL" option on Oracle 9.2 could hang.
    • Non-total figures in “Documentation Summary” and “Observation Report” were shown in bold.
  • Documentation
    • The “Filter” dropdown might show incorrect figures for Comparison Documentation.
    • Some of the “Look&Feel” options, for example, “Documentation Footer”, were not included to documentation.
    • Could not generate comparison documentation if the documentation name was the same as the source documentation name.
    • A non-existing page opened on clicking an object’s constraint link.
    • On clicking a link of source code, the corresponding source code line was not highlighted on the "Observations > DB: Invalid Objects" page.
    • The “Code Review” link was not disabled when the page had no content.
  • Oracle Database Logon
    • The Validate feature was enabled for incompatible documentation generation modes.
    • Connection to a database might hang on “Creation Mode Type 2” (based on another documentation).
  • Database Instance Registration
    • The database instance name was missing in the confirmation window on Documentation Comparison mode.

ClearDB Documenter 4.0 (Release 5)

Feb 17, 2015

NEW FEATURES

  • NEW: R&D (References and Dependences) diagram visualizes references and dependences
    of database objects (clickable).
  • NEW: ER (Entity Relationship) diagram visualizes tables/views and their relationships
     (clickable).
  • NEW: Option to generate diagrams in SVG (Scalable Vector Graphics) format.
  • NEW: R&D, ER, Call Tree and Flowchart diagrams includes a zoom, magnifier, income
    and outgoing elements highlighting
    feature. Only if diagrams are generated in SVG!
  • NEW: To easy and fast locate objects in ER or R&D diagrams, a mouse click on an object
    name in the list of diagram objects (above ER or R&D diagrams) will center the
    diagram and shows the object with a blinking (5 sec.) red frame. Only if diagrams are
    generated in SVG!
  • NEW: For better navigation, objects included in an ER or R&D diagram, are listed above
    diagram.
  • NEW: Highly customizable templates for ease and quick documentation generation.
  • NEW: Support for all schema and non-schema object types up to Oracle DB 12c – 58 object
    types in total.
  • NEW: New version of PL/SQL Code Analyzer engine providing 72 Code Review Rules.
  • NEW: Preview of a documentations tree structure in the GUI before docu generation.
  • NEW: Support for Oracle Editions.
  • NEW: A ClearDB Documenter 4.7 license is based on two metrics: "named Oracle database
    instances
    " and "concurrent user".

IMPROVEMENTS

  • Includes new object properties defined in Oracle DB 12c.
  • 118 Object Type specific icons in Documentation Tree and Content.
  • The documentation content title is fixed and is not scrolled out when the page is scrolled down.
  • Displays the object attribute page e.g. “Primary Key” of a table in the page navigation line.
  • Highlights the Database connection and Observation nodes in the Documentation Tree.
  • Displays the number of objects in comparison nodes of the Comparison Documentation Tree.
  • Displays the list of subroutines of Call Trees and Flowcharts diagrams in a scrollable area.
  • The content of tables of the “Documentation Summary” and “Comparison Report” pages can be expanded/collapsed.
  • New options to include to a Comparison Documentation new objects created since the source documentation was created or all missing objects in the source documentation.
  • Highlights the corresponding line of code on navigation to it in the Code Audit pages (Code Review, Structure View, Flowchart, etc.).
  • New multiple options to auto expand the Documentation Tree on Documentation opening in the browser.
  • Generation and Documentation options are split into two pages.
  • The former Job Manager and Compare Kit's are included to ClearDB Documenter 4.7 A new documentation page “DB Object Type Icons”, lists and displays all icons by object statuses such as “valid”, “invalid” and “disabled” available in a Documentation.
  • Validation of checked objects loaded to the DB Object Tree from a template or another documentation
  • Synchronizes the Database Object Tree in two ways:
    • Auto-Sync
      • includes to a documentation all "current" available objects in the database of  defined schema or object type folders
    • Refresh
      • One time synchronization of selected schema or object type nodes in the Database Object Tree
    • Validation
      • Adds and/or removes database objects from the Database Tree based on the actual situation of the database connected
  • The former Job Manager and Compare Kit's are included to ClearDB Documenter 4.7
  • A new documentation page “DB Object Type Icons”, lists and displays all icons by object statuses such as “valid”, “invalid” or “disabled” available in a Documentation.
  • Starts documentation generation from the “Generation Options” page.
  • “R&D diagram”, “ER diagram” and “CRUD2 MATRIX” documentation nodes indicates its level in the documentation tree.
  • New option to define the documentation file name as the documentation title.
  • Documentation related options are moved from Preferences to the tab “Look&Feel” of the "Docu content options" in the ClearDB Documenter 4.7 main window.
  • Disables the “CRUD1” page if no CRUD1 matrix is available for a object.
  • The labels "Source Documentation" and "Target Documentation" are renamed to "Source 1" and "Source 2" correspondingly in the Comparison Documentation.
  • Launches Google Chrome with the argument "allow-file-access-from-files" to enable it to show the Documentation content.
  • Displays non-clickable blocks of a Call Tree (such objects are not part of documentation) with gray color background.
  • Removes incomplete documentation from the system if documentation generation has been interrupted (break) by the user.
  • The “Overview” node of a Documentation was renamed to “Introduction”.
  • Maximum two ClearDB Documenter 4.7 instances can run at a time on a PC.
  • Excludes the misleading “Documentation Summary” page from a Comparison Documentation.
  • CHM format is not supported anymore to create new documentation. But CHM based documentation still can be opened using the "Docu manager"
  • Other minor improvements and fixes in the GUI and Documentation.

ClearDB Documenter 3.0 (Release 7)

May 24, 2013

Improvements

  • Core and GUI
    • Improved the notification message displayed when the user tried to run a second instance of ClearDB and the “Allow only one instance at a time” option was enabled in Preferences.
    • The “Load Objects” feature of “New documentation based on existing documentation” creation mode was moved to the popup menu of the “Load” button as a new “Load Checked Objects from Source Documentation” menu item.
    • The “Load” feature also refreshes the Object Tree.
    • Prompts the user to overwrite the existing documentation with the same file name on start of documentation generation.
    • Remembers the user selection of the documentation output folder in the “Generation Options” tab.
    • Improved display of the source and target documentation/database in the “Navigation Tree”.
    • Opens documentation in the default Internet Browser if the preferred browser option is wrong.
    • Improved information retrieval from the database for object references and dependencies.
    • Displays the documentation title in the “Navigation Tree”.
    • Resets the “Open HTML with Browser” option to the default browser if the previously selected one could not be found.
    • Ability to view documentation in Comparison mode at the Source and Target selection step.
    • Displays a warning message if the user has not included any objects in the documentation and clicks Next at the “Database Object Tree” step.
    • Improved GUI and look&feel of Code Metrics.
    • Checks if the specified Documentation Output Folder exists before starting documentation generation.
    • The setup program installs sample documentation in HTML and CHM formats. After installation, documentation will be listed in “Docu Manager”.
    • Compatible with Internet Explorer 10.
    • Support for Windows ClearType feature.
  • Docu Manager
    • New feature “Compress (zipped) selection to ..” - compresses documentation selection to a zip archive.
    • The “Docu Size” tooltip displays detailed information about the documentation and its content size.
    • Highlights the selected line.
  • Compare Documentation
    • Optionally compares object properties, source code, synonyms and grants between the source documentation/database and target documentation/database.
    • Extract DDL
    • “Ctrl+F” shortcut key was added to the Find feature in the View DDL window.
  • Documentation
    • A number of GUI and look&feel improvements.
    • Displays Code Audit links in the object's content page when the “Display Code Audit information in separate page” option is enabled.
  • Job Manager (Command Line)
    • New options “Auto” and “Manual” for Generation Output options allow to define the documentation output folder and file automatically or manually by the user.
    • Explicit paths in the job definition file change to Windows variable analogues.
  • Code Analyzer Options
    • Formatter: added the new option “1st level only” for the “General Layout -> Linefeeds -> Around a PL/SQL block”
    • Code Metrics Options: “?” buttons display descriptions for flagged code metrics.
  • Code Review Rules
    • Improved rationale description for rules: “Program Structure - The function interface complexity exceeds the specified maximum” and “Program Structure - The function parameter complexity exceeds the specified maximum”
  • Logon to DB
    • Raises a warning if 32bit Oracle Client 10g or lower is installed in a folder containing parentheses (Windows 64bit).
  • Online Support Desk
    • The column “Sent” in the “Received” table was renamed to “Sent by TechSupport” and added the column “Received”.

Bug fixes

  • Core and GUI
    • It was impossible to change or add DDL options in “New documentation based on existing documentation" mode.
    • “Documentation Description” defined in “New documentation from scratch” mode was not changed on switching to “New documentation based on existing documentation" mode.
    • In some network environments checking licensed concurrent users might be incorrect.
    • Did not support check constraints of VIEW objects.
    • Could not run a new instance even when the “Allow only one instance at a time” option was disabled.
    • Wrong counting of running ClearDB instances in Command Line mode.
    • The comparison process interrupted on error when the “Break generation on error” option was disabled.
    • Date and Time separators defined in Preferences were not applied after changing the Windows system local settings.
    • Automatically loaded objects from the source documentation when the “Database Properties Only” option was enabled.
    • The “Break” button stayed inactive while loading objects from the source documentation in “New documentation based on existing documentation” creation mode.
    • Could not break the process of loading objects and there was no progress bar in “Extract a subset from existing documentation” mode.
    • Shortcuts of the “Docu Manager” features were active at the “Options and templates” step.
    • “Add Documentation” feature was inactive when If there was no documentation in “Docu Manager”.
    • The “Use Proxy Server” option was not enabled in Preferences when the appropriated setting was enabled in Internet Explorer.
    • Links to “Code Analyzer Options” on the “Documentation Options -> Code Analyzer” tab worked incorrectly.
    • Autofix of the “Title” column of “Docu Manager” worked improperly.
    • Conversion documentation from HTML to CHM and back from CHM to HTML could raise the “Stack Overflow” error.
    • Documentation in HTML format could not be open in an HTML browser if it contained a folder with no DB objects.
    • The “Navigation Tree” could work incorrectly.
    • The “Save last <N> connections” option in the “Connection Settings” was ignored.
    • Percentage in the objects loading progress bar could be wrong when loading a large set of objects.
    • The “Skip Connection” option did not work when the list of last connections was empty.
    • “Docu Manager” kept showing description for the previously deleted documentation.
    • “Docu Manager” could not open after two conversions of the same documentation.
    • Conversion documentation from one format to another overwrote the source documentation if the “Create and save doc in its own folder with the same name” was enabled.
    • The “Include/exclude calling/called objects” option did not work.
    • Wrong GRANT DDL for EDITION objects.
  • PL/SQL Analyzer
    • REF token was not recognized properly before data type name in the VARYING ARRAY object type definition.
    • BINARY_FLOAT and BINARY_DOUBLE data types were not supported.
    • CROSS JOIN clause was not supported.
    • EXTRACT function did not support interval expression after FROM.
    • FIRST_VALUE and NEXT_VALUE functions were not supported.
    • SERIALLY_REUSABLE pragma was not supported.
    • OUTER JOIN clause was not supported.
    • PARALLEL_ENABLE with options was not supported.
    • PARALLEL_ENABLE and PIPELINED clauses might swap their positions in the code.
    • PIVOT and UNPIVOT clauses were not supported.
    • IN clause without parenthesizes was not supported.
    • SYSTIMESTAMP AT TIME ZONE DBTIMEZONE was not supported.
    • Statements having multiline string literals defined in alternative quoting mechanism were not supported.
    • Error logging clause was not supported.
    • INSERT without column list in MERGE was not supported.
    • Single expression without parenthesis in VALUES was not supported.
    • Two or more dots in the remote DB name/data type, procedure/function call was not supported.
    • Any order of HIERARHICAL_QUERY clause/GROUP_BY clause/HAVING condition in the statement was not supported. Oracle DB supports it but Oracle Documentation declares a static order of clauses.
    • Comma was missed in GROUP BY GROUPING SETS clause after analysis.
    • ESCAPE clause in a CASE expression was not supported.
    • AS without a column alias, for example SELECT 1 AS FROM DUAL. Oracle DB supports it but Oracle Documentation does not.
    • CASE..WHEN expression containing IN clause with a sub-query was not supported.
    • Parenthetical query_table_expression was not supported.
    • Complex varray reference in a WHERE clause condition was not supported.
    • References to collection types or indexed tables in an INTO clause was not supported.
    • RESTRICT_REFERENCES pragma in the beginning of the package was not supported.
    • BULK COLLECT INTO in a sub-query of a WITH clause was not supported.
    • DELETE FROM <table> RETURNING statement was not supported.
    • COLLECT aggregate function was not supported.
    • FLASHBACK_QUERY clause was not fully supported. Unlike declaration in Oracle Documentation, Oracle Database allows to execute query with both VERSIONS BETWEEN... and AS OF... clauses.
    • SAMPLE clause in SELECT statements was not supported.
    • Floating-Point conditions were not supported.
    • SET as a name of the subprogram was not supported.
    • EMPTY as a function name was not supported.
    • TYPE without attributes in parentheses was not supported.
    • XMLTABLE with XMLNAMESPACES was not supported.
    • XMLNAMESPACES without DEFAULT clause was not supported.
    • If an EXISTS clause was the last condition in a WHERE clause, then the UNION of the main query was parsed as the UNION for the EXISTS sub-query.
    • TRIGGER_ORDERING clause was not supported.
    • TRIGGER_EDITION clause was not supported.
    • LEAD and LAG functions were not supported.
    • ENABLE/DISABLE in CREATE TRIGGER clause were not supported.
    • AUTO token in the PREDICTION function was not supported.
    • A parenthesized parameter of ESCAPE clause was not supported.
    • Tokens in the “Expecting” column could be incorrect.
    • Hint comment was placed into a wrong position if it was followed by other comment.
    • The column name might be wrongly specified in parentheses on the left side of the assignment of the SET clause of the UPDATE statement if the right side was an expression.
    • WHERE condition with a long BETWEEN clause was formatted incorrectly.
    • CREATE TRIGGER/TYPE/TYPE BODY statements could not be combined with CREATE FUNCTION/PROCEDURE/PACKAGE/PACKAGE BOBY statements in one script.
    • The schema name in a library name of the type method external declaration was not supported.
    • The first identifier was missed in the formatted text in the external subroutine parameter declaration, in parameters like <ident> INDICATOR <ident>.
    • Formatting of the external subroutine parameters was incorrect in WRAPPED mode: there was no line break even if the number of parameters were large.
    • Comments starting with “--###” were wrongly treated as pseudocode comments.
    • Analysis of a trigger might cause an Access Violation error if the “Linefeed around PL/SQL block” setting was enabled.
    • “/” statement delimiter was not supported.
    • The “List index out of bounds” error might occur on analyzing some packages.
  • Documentation
    • The “Observations -> Rules Observations -> DB: Invalid Objects” folder displayed the wrong number of invalid objects.
    • The “Observations -> Rules Set Observations -> DB: Invalid Objects” folder displayed the wrong number of invalid objects.
    • The “Observations -> Evaluation Contexts Observations -> DB: Invalid Objects” folder displayed the wrong number of invalid objects.
    • There were pages with no content when Documentation contained only the Observation part.
    • Included schemas with no objects.
    • Raised a JavaScript error if the wrapped stored object had code errors.
    • Showed “Code Audit” sub-nodes even when the appropriate options were disabled.
    • The “Exclude 0 value nodes in the Navigation-Tree” option was not ignored for “Code Audit” sub-nodes.
    • A disabled SCHEDULED WINDOW object was missing in the “Observations -> DB: Disabled Objects” folder.
    • An invalid LIBRARY object had no icon.
    • ClearDB settings for generation” options were missing in the Documentation Summary page for “Extract a subset from existing documentation” mode.
    • Objects with Oracle Warnings were missing in “Observations”.
    • Invalid objects with Oracle Warnings were shown in the “DB: Objects with Warnings” section instead of “DB: Invalid Objects”.
    • Call Tree diagrams were generated improperly when the “Call Level” setting was greater than 1.
  • Job Manager (Command Line Mode)
    • It was impossible to save a job if the “DB properties only” option was enabled.
    • The specified “Output File Name” was not saved and used on documentation generation.
    • The “Title”, “Author”, “Comments”, “Output file name”, “Save output as” and “Include documentation options to log” settings and options were not saved/restored on job modification.
    • A number of “Access Violation” errors fixed.
  • PL/SQL Formatter
    • Some of the “General Layout -> Linefeeds” options worked improperly.
    • If a cursor declaration goes after the variable declaration then they were always separated by the empty line even if all linefeed options were off. The same was for the empty line between all variable declarations and the BEGIN token.
  • Call Tree
    • The INSERT relation was wrongly shown as a SUBROUTINE call.
  • Code Analyzer Options
    • Naming Rules templates for subprograms worked improperly when “Case Insensitive” options were turned off and the pattern was typed in lower case characters.
  • CRUD 2 type matrix
    • The “Stored Object” column was empty for triggers.

ClearDB Documenter 3.0 (Release 2)

Oct 17, 2011

New features

  • Compare two sets of documentation or documentation with a database!
    Compare two sets of documentation or documentation and a database and vice versa and produce a detailed comparison report included as part of the result documentation. The comparison report highlights differences between the Source and the Target; lists the objects that exist in the Source but are missing in the Target and vice versa; lists objects that have major or any differences in their definitions and properties; lists objects that are identical in the Source or the Target. Additionally, it also includes differences in database instant options and initial parameters in object differences.
  • Automate documentation generation by using integrated scheduled jobs!
    Automate documentation generation via its integrated scheduled jobs or via its command (batch) files scheduled in third party schedulers. Create jobs for complex, time consuming and long lasting documentation generation and schedule their execution in ClearDB Documenter during non-working hours. Alternatively, it’s possible to save a job as a batch file and schedule it in a third party scheduler or execute it manually via the Windows Command Line. Each documentation generation job is widely customizable in terms of generation, documentation and Code Analyzer options.
  • Actualize the content of documentation by synchronizing it with the database!
    Actualize previously generated documentation with a few steps to ensure that its content is always up-to-date and synchronized with the database. It updates properties, DDL source, references, dependences, etc. of database objects included in the selected documentation and produces a new updated version of the selected documentation. You will not be able to change neither the documentation object selection nor the documentation, Code Analyzer or generation options.
  • Extract database DDL from documentation!
    Extract database DDL from documentation (included optionally) with the ability to select object types to be extracted and to specify a number of output settings. In case of a database crash, ClearDB Documenter gives you a chance to recover the database by using the database DDL extracted from the documentation. Object DDL for each object is included in the documentation by default. DDL inclusion can easily be enabled or disabled at the documentation or object type level.
  • Generate new documentation based on the content of source documentation!
    Generate new documentation based on the content and options of source documentation. After selecting the source documentation, at the next step, all of its database objects and documentation and Code Analyzer options will be loaded to the GUI. You can easily change the database object selection as well as documentation, generation and Code Analyzer options in the appropriate steps. This feature dramatically speeds up the documentation setup and definition process.
  • Convert documentation to another format!
    Convert documentation to another format (HTML/CHM) offline. If the selected documentation was generated in HTML format, using this feature, you can easily convert it to CHM format and vice versa. You will not be able to change neither the documentation object selection nor the documentation, Code Analyzer or generation options.
  • Extract a subset from documentation!
    Extract a subset from documentation offline (no database connection needed) with the ability to remove database objects and to change documentation, Code Analyzer and generation options.
  • New GUI and wizard layout with its handy Feature Navigator!
    A new, easy to use, graphical user interface (GUI) for simplifying drilling down the features and accelerating navigation in step based wizard pages. A new tree-like Feature Navigator exposes the main features and their steps, highlights the active feature and its completed and not completed steps, showing them with specific icons. For ease of use, access to the main features is also available via nice, visible large buttons in the Main page.

Other significant enhancements and improvements:

  • Support for a complete set of 54 database object types up to Oracle DB 11gR2:
    CLUSTER, CONTEXT, DATABASE DESTINATION, DATABASE LINK, DIMENSION, DIRECTORY, EDITION, EVALUATION CONTEXT, FILE_WATCHER, FLASHBACK ARCHIVE, FUNCTION, MATERIALIZED VIEW, MATERIALIZED VIEW LOG, RULE, RULE SET, INDEXTYPE, GROUP, JAVA CLASS, JAVA SOURCE, JOB, LIBRARY, OPERATOR, OUTLINE, PACKAGE, PACKAGE BODY, POLICY, POLICY GROUP, PROCEDURE, PROFILE, QUEUE, ROLE, REFRESH GROUP, RESOURCE CONSUMER GROUP, RESOURCE PLAN, RESTORE POINT, ROLLBACK SEGMENT, SCHEDULER CHAIN, SCHEDULER CREDENTIAL, SCHEDULER JOB, SCHEDULER JOB CLASS, SCHEDULER PROGRAM, SCHEDULER SCHEDULE, SCHEDULER WINDOW, SCHEDULER WINDOW GROUP, SEQUENCE, SYNONYM, TABLE, TABLESPACE, TRIGGER, TYPE, TYPE BODY, USER, VIEW, WINDOW GROUP
  • New option to break the generation process on any error.
  • The state of documentation generation, documentation comparison, extraction of database DDL and a subset of documentation, etc. displayed in the progress window is also shown in the Windows 7 Taskbar.
  • Improved content of DB Link and External Table types objects properties.
  • DB Link type objects include synonyms to dependencies.
  • Highlights Java Source code using Java code syntax highlighter.
  • A Call Tree invoked from the CRUD matrix shows all analyzed objects which use the selected dataset object.
  • Added support of the following database object types: RULE, RULE SET, EVALUATION CONTEXT, GROUP
  • New option to include objects DDL in documentation at global non-object type and individual object type levels.
  • Documentation Manager displays a ClearDB Documenter version number used for documentation generation.
  • New option that controls inclusion of documentation options in a log.
  • The Database Object Tree saves database object selection to file for later re-use.
  • A number of generation, documentation content and GUI bugs fixed.

ClearDB Documenter 2.5 (Release 1)

May 27, 2010
New features
  • Supports a complete set of 47 schema and non-schema object types  for Oracle versions up to 11gR2:
    CLUSTER POLICY FLASHBACK ARCHIVE
    CONTEXT POLICY GROUP MATERIALIZED VIEW
    DATABASE LINK PROCEDURE MATERIALIZED VIEW LOG
    DIMENSION PROFILE REFRESH GROUP
    DIRECTORY QUEUE RESOURCE CONSUMER GROUP
    EDITION ROLE RESOURCE PLAN
    FUNCTION SEQUENCE RESTORE POINT
    INDEXTYPE SYNONYM ROLLBACK SEGMENT
    JAVA CLASS TABLE SCHEDULER CHAIN
    JAVA SOURCE TABLESPACE SCHEDULER CREDENTIAL
    JOB TRIGGER SCHEDULER JOB
    LIBRARY TYPE SCHEDULER JOB CLASS
    OPERATOR TYPE BODY SCHEDULER PROGRAM
    OUTLINE USER SCHEDULER SCHEDULE
    PACKAGE VIEW SCHEDULER WINDOW
    PACKAGE BODY   SCHEDULER WINDOW GROUP
  • Includes PUBLIC SYNONYMs, PUBLIC DATABASE LINKs and RECYCLE BIN objects to documentation.
  • Incorporates NEW PL/SQL Parser Generation. Analyzer now supports up to 99% of SQL and PL/SQL keywords and reserved words.
  • Generates documentation in HTML format (default format) through a new setting to define the preferred HTML browser to open documentation.
  • Generates CRUD2 type matrix on schema level.
  • New Documentation Options is split into Object Options, Code Analyzer and Observation Report sections. The new tree-like object type options navigator simplifies access to the options of a specific object type. For easier navigation the Object Type Options tree is sorted in the same way the Database Object Tree is sorted.
  • Sends one or a selection of documentation from  History by Email, zipped. It simplifies sharing of multi-file HTML and «suspicious» CHM format documentation.
  • Logs on to a database by using LDAP and Direct connections.
Other significant enhancements and improvements:
  • New and significantly improved graphics engine generates flowchart and Call Tree diagrams and CRUD matrices faster and more accurately.
  • New optional «Overview» page explains documentation structure to help new users accelerate learning.
  • New option (enabled by default) to show Code Audit information (Code Review, Structure View, Code Metrics, Flowchart, Call Tree, CRUD1) in object sub-nodes.
  • New options to sort the Database Object Tree logically (enabled by default) or alphabetically. To be consistent, the setting is automatically applied to the Object Type Options Tree and Output Documentation Tree.
  • New connection setting «DB type» helps the users organize their DB connections in groups; e.g. DEVELOPMENT, PRODUCTION, TEST and others. Assigns background and foreground colors to easily identify them while working with the contents of a mission critical database.

ClearDB Documenter 2.0 (Release 1)

Nov 11, 2009
Improvements
  • Added a prompt on enabling the "Generate Observation Report Only" setting
  • Hides unused options if the "Generate Observation Report Only" is enabled
  • Added a "Documentation content" line to the Log window
  • Adds file extension to documentation file if missed
  • Prompts on documentation file overriding
  • Displays a warning message if the user is about to expand the whole object tree
  • Disables the "Hide system schemas" and "Hide empty items" settings when the "DB properties only" option is enabled
  • Disables all unused "Documentation Options" tabs when the "Generate DB only" option is enabled
  • Displays "SYSDBA/SYSOPER" in "Connection String" of the Documentation Summary page
  • Does not show unused documentation options in Log and in the documentation settings summary page
  • Error number of Code Audit is a link to the object source code
  • Extended the list of system schemas
  • Displays a long template name as shortened with the full name in the tab's hint
  • A table width of list of objects and observations fits to the documentation page width
  • Sorts the Metrics list by subroutine's name with the GLOBAL line at the first line
  • Adds "CREATE OR REPLACE" to the stored object source code
  • Improved Observation Report object type nodes names and captions
Bug fixes
  • Raised an "Access violation" error on Step #5 if connection to a database was skipped on Step #2
  • Sometimes standalone programs and functions in the flowchart page were wrongly treated as a package subroutines
  • Could raise an "Access violation" error while frequently clicking the "Next" button
  • Did not make a backup copy of the license key on applying the changes in Preferences
  • The Statistic pane on Step #3  did not show info if not all objects of a type folder were selected
  • An invalid object's icon was not red in the 'Problem Observations' page
  • A schema name was missing in Total of the object summary table
  • Renaming documentation file to the same filename removed it from the Doc. History list
  • Could not rename documentation file in the Doc. History list when it was open
  • Wrong source code of a schema trigger
  • Sorting by file size worked incorrectly in the Doc. History list
  • Template file name was shown without full path in the settings summary page
  • Some GUI controls were displayed incorrectly on 120 dpi mode
  • The newly saved template was not become opened and active
  • If no template is loaded don't show any template name on the templates tab
  • System schemas were selected when the user disabled the "Hide system schemas" option
  • The last lines of Log were hidden under the bottom border of the Log window after generation
  • Removed odd highlighting and underlining effects in the Object Tree
  • The newly saved template was not saved in the template list
  • Template deletion did not close the deleted template
  • Wrongly generated "Observation Report" when the "Generate DB only" option was enabled
  • All Object Tree nodes were collapsed after disabling the "Hide System Schemas" option
  • Documentation generation failed on Instant Client and XEClient