What’s new in AQdevTeam 1.1
Product Information
Productivity Tools
New in AQdevTeam
Support & Resources
Overall Improvements
Due to improvements in algorithms of interaction between the client and server, the overall speed of AQdevTeam has been increased.
Centralized Database Management
AQdevTeam includes a special utility, the Database Manager, that
lets you back up and restore databases for AQdevTeam
Server, as well as update the structure of your legacy databases when
migrating to a newer version of AQdevTeam Server. The Database Manager is
part of your AQdevTeam Server installation (<AQdevTeam Server for
InterBase>\AQdTIBTool.exe or <AQdevTeam Server for ADO>\AQdTADOTool.exe).
To learn more about this tool, see on-line help on AQdevTeam Server.
Macros and Visual Macro Builder
The new Submacro and Run Submacro operations let you organize and run other Macro Builder operations like routines.
Submacros can also run in response to an error.
The new Directory Exists operation allows you to check whether the desired directory exists.
Two new operations let you compile help files in .hlp and .chm formats and analyze the results of the build for critical errors and warnings.
Two more new operations let you build installation programs with InstallShield Professional 6 and InstallShield Developer 7.
Changes in the Compile Visual C++ nn operations: Now you can specify Visual C++ project options directly from the Macro Builder. In the previous version, you could only specify a configuration.
Server macros can now use plug-ins. The Properties dialog of AQdevTeam Server allows you to install or uninstall plug-ins in AQdevTeam Server.
Filters
Filters can now be applied to BLOB fields, for instance, to the Details field.
There are new case-insensitive filter conditions for text fields.
There are two new filter conditions for Date fields: Greater than or equal and Less than or equal.
The Show parents and Show children filter options are now stored as a part of the filter criterion. In the past, they were common for all filter criteria.
Operations with Items and Projects
The new item in the Issue Explorer context menu, New Item in Another Project, lets you add items to a project that differs from the current one.
In the previous version, you could attach files and file links to items. Now you can also attach hyperlinks and links to files that are located in a version control system.
You can move items to other projects using only a few mouse clicks.
Now you can easily change the parent-child relationship for projects in the Project Manager dialog. For instance, you can make a top-level project a child (subproject) of another project and vice versa.
User Interface Changes
The Project Explorer panel has the [All projects] node now. This lets you quickly view all bug reports, suggestions, notes and items of other types stored in the database.
A new option of the Project Explorer, Show item types, specifies whether AQdevTeam displays item types within the Project Explorer panel.
A new option of the Macro Repository panel, Auto-load server-side log, specifies whether AQdevTeam automatically loads a server macro log to the Macro Execution Log panel for server macros that run from the Macro Repository panel.
A new option of the Macro Execution Log panel, Clear panel upon loading a server-side log, specifies whether AQdevTeam clears the panel when loading a server-side log.
User Management and Permissions
The database has a new user group, Everyone, that includes all users registered in the database. This group greatly simplifies the sharing of views and form layouts among users.
Item collections in subprojects now inherit user permissions from the item collections in their parent projects. For more information on how permissions work.
Changes in Programming Objects
A new property,
AQdevTeamManager.IsRunningOnServer, specifies whether a macro is running on the server (this is possible if this macro is a server macro).
A new method,
ItemRecord.LinkToAnotherItem, allows you to link one item to another via scripts. In addition, the new ItemRecord.LinkedItems property returns a collection of all items linked to the given item.
The
BaseItem object contains two new methods - GetAllItems and GetPrimaryItems - that return the collection of items. The difference between these methods is that the collection returned by GetAllItems includes items of child projects while the collection returned by GetPrimaryItems does not contain these types of items.
The
FieldValue.DecoratedString method now returns the contents of a BLOB field as text. Before, this method did not support BLOB fields. To get a BLOB field's contents in a binary format, use the FieldValue.GetValue method.
The
Commit method was moved from the ItemRecord object to the BaseItem object. Now the method accepts one parameter: The item in which you want to save the changes you have made.














