AutomatedQA: Award-winning tools for software testing and quality assurance

Home » Products » AQdevTeam » What’s new in AQdevTeam 1.2

What’s new in AQdevTeam 1.2

Overall Improvements

The Full-Text Search engine uses indexes now. This increases the searching performance tremendously. In addition, the Select in Preview context menu item in the Full Text Search panel was renamed to Preview Content.
Now when sending an item via email, it is sent as a single .mht file rather than a bunch of files in various formats. The .mht file (which is in MHTML format) includes the item itself and all the attachments stored with the item.
Now when exporting items to a file it is possible to configure which item fields to export, in which order, which layout (vertical or horizontal) the report will have and what colors to use in the report. In addition to HTML, XLS, RTF and TXT formats, now you can export items to a file in XML or MHTML format.
Now it is possible to import items to the database from XML files. For instance, you can use an XML report saved from the Issue Explorer (see Exporting Items to a File) This allows you to quickly move items between different databases or import several prearranged items immediately.
The Display Options dialog has been changed.
It is no longer possible to enable both the Required field and Use default on edit properties for an item field, since it is useless.
Actions that can be executed for the current item are displayed in alphabetical order.
Records in the Audit Trail panel can be sorted not only in reverse, but also in direct chronological order.
The restriction on the size of the string kept in the Audit Trail's Reason field does not exist any more.
The maximum size of an internal attachment (which is entirely kept in the database) is limited to 10 MB. If the file is larger than 10MB, it should be attached to items as an external attachment, that is, the database will contain only links to such files, while the files are kept on local disk. This is done to restrict the database growth.
It is now possible to read instant messages sent to an instance of AQdevTeam Client that was installed using the Light configuration.
It is now impossible to remove an item from the database if the item is open in the Edit form.

Macros and Visual Macro Builder

A new group of operations, Printable Report, has been added. Operations from this group allow you to create customizable reports.
The operations from the new group called AQdevTeam let you easier enumerate projects, item types, items, item fields and Audit Trail records stored in the current AQdevTeam database.
It is now possible to save attachments from email messages that are obtained using the Receive Email operation.
The Configuration property of the Compile Visual C# .NET Project, Compile Visual Basic .NET Project and Compile Visual C++ .NET Project operations became required. As a result, your existing macros that use these operations may need to be changed.
Now it is possible to use roles in server macros.
The error in operations from the FTP group has been fixed.

Database Structure Changes

The format of the AQdevTeam Server databases has been changed: fields of the Raw data.Memo and Raw data.BLOB types no longer exist. Instead, the following new field types have been added: Raw data.Text memo, Raw data.Rich text memo and Raw data.Picture. You can update the structure of your legacy databases when installing AQdevTeam Server, or later, using the Database Manager.

New Controls for Customizable Forms

The new component, TAuditTrailControl, displays the current item's status history within the Preview Pane or Edit Form. Using this component saves you from switching to the Audit Trail panel.
The new component TItemLinksControl displays a graph that represents how items linked to the current one are linked to each other.

Changes in Programming Objects

For each collection derived from the Collection object, AQdevTeam provides the new index property, Items, instead of the GetItem method. This property allows you to display all methods and properties of the appropriate collection item in the Code Completion window. Actually, the GetItem method still exists for backward compatibility, though it is no longer displayed in the Code Completion window.
Now, to get the item currently selected in the Issue Explorer panel, use the IssueExplorerSelection object. The AQdevTeamCurrentItem object does not correspond to the item currently selected in the Issue Explorer; it corresponds to the last edited item only.
The AQdevTeamCurrentAction, AQdevTeamCurrentStartStatus and AQdevTeamCurrentEndStatus objects are available only when an action is being executed.
The CreateItem, CreateChildItem and EditItem methods of the new AQdevTeamUIActions object allow you to call the Edit form in order to create a new item or edit an existing one.
The second parameter of the PostMessage, PostWarning and PostError methods of the Log object became optional.

Remote Console Installation

To avoid errors, it is not allowed to install AQdevTeam Server under a Terminal Services Client or any other remote console.
Copyright © 1999-2008, AutomatedQA, Corp. All Rights Reserved.
Home | Legal | About | Contact | Site Map | Print