Quest® Development Studio for SharePoint

Version 4.2

Release Notes

July 2008

Contents

Welcome to Development Studio for SharePoint

New in this Release

Resolved Issues and Enhancements

Known Issues

System Requirements

Global Operations

Getting Started

Summary of Upgrade Procedure

History of Changes in Previous Releases

For More Information

 

Welcome to Development Studio for SharePoint

Thank you for installing Development Studio for SharePoint 4.2. 

Development Studio for SharePoint enhances SharePoint’s application development capabilities with drag-drop-configure Web parts, eliminating the need for custom coding to build sophisticated business applications in SharePoint.

 

We suggest that you check the KnowledgeBase at http://support.quest.com for additional samples, Tech Notes and answers to Frequently Asked Questions.

License Upgrade

Quest Development Studio for SharePoint version 4.x requires a new license file. If you are a current customer and you are using version 3.x of our product,  your existing license file will not work. If you don't receive an email with a new license file, you must contact your sales representative to get a new license file. The upgrade is free of charge as long as you are current on your Annual Service Maintenance.

 

Back to Top

New in This Release

This release of Development Studio for SharePoint includes the following new features:

 

Back to Top

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of Quest® Development Studio for SharePoint.

CR57289 Some of the Web Parts does not specify the correct URL in the Source HTTP parameter. This causes the Quest List Form's Cancel or Save button to return the user to a page with a missing HTTP parameter.
CR57335 The PerformValidation attribute is added to the Quest List Form's custom action so that the required fields will be validated when the custom action is performed.
CR53951 The browser freezes for a long period of time when you click on "Add Condition" inside the CAML Filter configurator. This happened in IE6 browser in Windows XP with Service Pack 2.
CR55594 In the List View, the data disappears when sorting the list view based on a column that only exists in one of the lists.
CR55661 The List View opens the target page of Hyperlink column in a new window. It should open in the same window.
CR55662 The List View displays a Picture column as a hyperlink. It should display as a picture.
CR55563 The behavior of the Configuration Editor is incorrect when "DOMINO"/"CUSTOM" systems are added. When the user adds a new system with a system type of "DominoXMLOtherHTTP" then selects a new system, the system type should be "DominoXMLOtherHTTP" but the actual system type is "Oracle". In the case where the system type is created with "Custom", the actual result is that the system type is "DominoXMLOtherHTTP".
CR55564 When a System is deleted in the Configuration Editor, a confirmation window should appear.
CR55565 When a System is deleted in the Configuration Editor, the System settings pane (right pane) keeps the settings of the DominoXMLOtherHTTPdeleted system. As a result, the application returns an exception if some settings (for example: System Type) are changed.
CR55370 In the SI List View, the CalculatedValue and LinkTo attributes show ButtonColumn when used together
CR55201 The System Integration Web Parts cannot handle Dynamic CRM metadata.
CR55041 The DevStudio Web Parts should display an appropriate message to the user when the wrong configuration file is specified for system integration. Currently, the page crashes and the user is redirected to a generic SharePoint error page. Note, this only happens on a web page that has SI web parts as these types of web parts check for system plug in configurator.
CR49681 In the SI List Form, the Actions editor generates XML with unnecessary attribute when the Action Type="GoToSource"
CR56140 In the List View, the Reset button in the filter panel resets the fixed operator to Exclude from Search
CR56495 In the SI List View, the CalculatedValue attribute does not work
CR56682 In the Chart View, the web page crashes when YAxisValueRange is used
CR56702 In the List View, copying one document from one library to another causing null object reference exception
CR56711 The List View generated NullRefereceException when the Display Fields is empty
CR56628 The List Form does not delete an instance of recurring event correctly
CR55970 In The Configuration Editor, the changed section of the Web.config file should be highlighted when the user selects a problem and presses the "Fix It" button
CR53865 Add the ability to customize the tooltip in the List Form.
CR54337 Add the ability to turn off the "* indicates required fields" message in the List Form and SI List Form.
CR54407 Add the ability to hide the "Click here to upload multiple files" link in the List Form.
CR57134 The <CurrentUserName /> expression does not work in the CAML filter if it contains a space.
CR57103 The SI Selector returns a "cannot find column DESC" exception when "Sort in Ascending Order" is switched off.
CR56741 In the List View, the CAML Filter editor saves the wrong option for the choice field.
CR57088 In the List View, the group header is always expanded if the Field element contains Title attribute.
CR56141 In the List Form, the list form display is shifted to the right in Mozila Firefox 3 and older.
CR54355 The Actions > Alert Me toolbar button appears in the List View when login anonymously.
CR57012 The Chart View and SI Chart View need properties to control the color of the chart border and image border.
CR56906 In the SI Chart View, the Reset button in the filter panel resetd the fixed operator to Exclude from Search.
CR56861 User receives a null reference exception when dropping the SI List View onto web part page.
CR57054 In the Panel Menu and Cascading Menu, if the target URL contains a relative URL, it will be appended to the master page URL instead of the URL of the current page. Because of this bug, current users have had to append "../.." in the relative URL to compensate the additional "_catalogs/masterpage". In  order to not break current users' applications, a new property called "Target URL Relative To Master Page URL" has been added. By default, this property is set to true thereby maintaining the buggy behavior but preventing the current applications from crashing. In order to get rid of the buggy behavior, current users need to set this property to false where the relative URL will then be calculated correctly relative to the URL of the current page.
CR57026 Add the new property, 'Enable New Item Link In Child View', to the List View to hide the New Item link in the child view.

 

Back to Top

Known Issues

The following is a list of issues known to exist at the time of Development Studio for SharePoint release.

SharePoint 2007 Web Parts

  You cannot connect the Web Parts in the list forms (NewForm.aspx, EditForm.aspx, DispForm.aspx or Upload.aspx). SharePoint will inform you that the maximum number of connection has been exceeded. This is true for any Web Parts, not only for Quest Software Web Parts. This issue has been reported to Microsoft and Microsoft acknowledges this to be an issue. So far, Microsoft has not provided a workaround for this issue. Fortunately, Quest List Form Web Part can be used in any page. Therefore, if you need to connect the Quest List Form Web Part with another Web Part, you can do so on a regular page. You can set the URL of the new form, display form or edit form in the Viewed Lists property of the Quest List View to point to this regular page.
CR57130 The installer returns "Object reference not set to an instance of an object" in 64 bit Windows Server 2008.
CR57727 The all day event that spans multiple days shows up only in the first day of that event in the Calendar View.
CR57312 The all day event slot in the Calendar View is too small. If you have multiple all day events, they may overflow to the next cell. This bug occurs in some of the skins of the Calendar View including the default view but not in some other skins.
CR57708 The recurring events that are created in Quest List Form do not show up in Microsoft Outlook when the Calendar view is connected with Microsoft Outlook.
CR57380 Removing the Quest Development Studio for SharePoint WebParts Feature does not remove the Web Parts from the WebParts gallery.
CR56960 The Quest List Form's Custom Action will not work if the Quest List Form consumes row from another webpart. The following error occurs when the custom action is invoked: This web part must be connected to a row provider when the "ConsumeRowDisplayFieldName" attribute is defined.
CR43417 The LinkTo field in the Quest List View will not work if the field name contains parentheses.
CR46535 The Quest List View does not sort the value in the People and Group fields when multiple values are allowed.
CR46535

The Quest List View does not sort the value in the Choice fields when multiple values are allowed.
CR41658

The Custom Action configurator in the Quest List View and Quest List Form does not list the ICustomAction classes whose DLLs are deployed in the Global Assembly Cache (GAC).
 

The Quest List View will sort Calculated Field (with Number return values) in alphabetical order instead of numerical order.
CR49580

The Quest List View does not have Send To Document Center context menu item.
CR49842

The Display Fields property editor in the SI List View cannot execute the default operation when one or more of the default operation parameters come from the row consumed from another web part.
 

A multi line text is displayed in a single line in Quest List View.
CR44672

The Quest List View does not display email addresses as hyperlink.
CR48298

The Multiple File Uploads capability of the Quest List Form only works when the Quest List Form is placed in the Upload.aspx.
CR49853

The SI List View does not retain the expand/collapse of the grouped fields after the page is posted back.
CR43593 The first input control in the Quest List Form retains the focus after you hit the Tab key. You have to hit the Tab key one more time before the focus is moved to the next control in the list form.
CR53213 The lookup field postback causes 404 error when the list name contains " - " in the list form

SharePoint 2003 Web Parts

 

 

 Quest Development Studio for SharePoint only supports .NET 1.1. If you run your SharePoint site under .NET 2.0 framework, you will get an error. To check the version of .NET that your site is running on, please open the IIS management console, right click the website for your SharePoint site and click Properties. Click the ASP.NET tab and make sure that the ASP.NET version is 1.1.x, not 2.0.x.
  The Quest Calendar View and Quest List Form cannot edit a particular instance of an event. They can only edit the property of the event series.

 

Back to Top

System Requirements

Before installing Development Studio for SharePoint, ensure your system meets the following minimum hardware and software requirements:

Requirements for SharePoint 2007

This article describes the requirements for SharePoint 2007:

http://technet2.microsoft.com/Office/en-us/library/6a198d15-f6bc-40ba-9240-c294059e3a821033.mspx?mfr=true

The following are the client side requirements for SharePoint 2007:

Although administrative tasks on SharePoint sites are optimized for level 1 browsers, Office SharePoint Server 2007 also provides rendering support for other browsers that are commonly used. To ensure that you have complete access to all the functionality, we recommend that you use a level 1 browser for administrative tasks.

Level 1 Web browsers:

Level 2 Web browsers

If a browser is not listed in either level 1 or level 2, it is not supported. For example, older browsers — such as Internet Explorer 5.01, Internet Explorer 5.5x, Internet Explorer for Macintosh, and versions of third-party Web browsers that are earlier than the ones listed as level 2 browsers — are not supported.

Level 1 Web browsers take advantage of advanced features provided by ActiveX controls and provide the most complete user experience. Level 1 browsers offer full functionality on all SharePoint sites, including the Central Administration Web site.

Level 2 Web browsers provide basic functionality, so that users can both read and write in SharePoint sites and perform site administration. However, because ActiveX controls are supported only in level 1 browsers and due to the functionality differences within different browsers, a different user experience might be provided and there could be some variances from the user experience from the level 1 browsers. 

The Mac OS is not supported at this time.

Requirements for SharePoint 2003

The following are the server side requirements for SharePoint 2003:

  1. Windows Server 2003 (with the latest Service Pack)

You can use one of the following editions: Standard Edition, Enterprise Edition, Datacenter Edition, Web Edition (requires full version of Microsoft SQL Server.

All other components will be installed with Windows Server 2003. You may install all the components on one computer, or distribute it across different computers depending on your requirement.

  1. Microsoft .NET Framework 1.1

Quest Development Studio for SharePoint only works with .NET Framework 1.1. It will NOT work with Microsoft .NET Framework 2.0.

  1. IIS 6.0

You must install the following components: Common Files, SMTP Service and World Wide Web Service.

  1. SQL Server

You can use one of the following versions of SQL Server:

NOTE

 

If you use SQL Server 2005 as your back end, you must read the following article on how to install SharePoint with SQL Server 2005 back end:

http://support.microsoft.com/kb/917446

 

 

NOTE


Please use the SQL Server 2000 Desktop Engine (WMSDE) or SQL Server 2005 Express Edition in the development and testing environment only. It is not suitable for a production environment.

 

 

NOTE



Please ensure you install the latest service pack for SQL Server.

 

 

  1. Windows SharePoint Services with Service Pack 2

WSS is available as part of Windows Server 2003 R2. You can download the WSS for free from the following site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=B922B28D-806A-427B-A4C5-AB0F1AA0F7F9&displaylang=en

  1. SharePoint Portal Server 2003 with Service Pack 3 (optional)

You can install the SPS 2003 on top of WSS. Please note that unlike WSS, SPS 2003 is licensed software. You can find more information about SPS 2003 from the following site:

http://technet.microsoft.com/en-us/office/sharepointserver/bb267364.aspx

 

NOTE



If you are installing WSS 2.0 or SPS 2003 in 64 bit platform, please make sure you read the section about Support for Windows Server 64-bit Version in this article:

http://office.microsoft.com/en-us/techcenter/HA100806971033.aspx#1

You must make sure that WSS and/or SPS work before proceeding with Quest Development Studio for SharePoint installation.

Please make sure that you run ASP.NET 1.1 in your SharePoint site. Please see the Installing and Configuring ASP.NET 1.1 section in the following document on how to do so. You must use the command line option in 64 bit platform since the ASP.NET tab is not available.

http://office.microsoft.com/en-us/winsharepointadmin/HA100598511033.aspx

 


The following are the client side requirements:

  1. One of the following browsers:
  1. Microsoft Office 2003

You can edit SharePoint pages in the browser but you need Microsoft Front Page 2003 to edit the list forms. In addition, the Datasheet View in AllItems.aspx and the Multiple File Upload in Quest List Form will work only if you have Microsoft Office 2003 installed.

 

We recommend you run Windows Update on the server and client after installing all components.

NOTE



You must be an Administrator on the local computer to perform the installation.

 

NOTE


For more information about the system requirements for SharePoint, please go to http://www.microsoft.com/windowsserver2003/techinfo/sharepoint/sysreqs.mspx.

 

 

Back to Top

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

 

Back to Top

Getting Started

The first question that people usually ask is "How do I get started with Quest Development Studio for SharePoint?". There are several ways to get started with our product. Choose one that will best suit your needs. All the tools that are mentioned below can be downloaded from our product page at http://www.quest.com/Development-Studio-for-SharePoint.

  1. The easiest way to get started is to order the Quest Development Studio Evaluation Kit from our product page. A set of DVDs will be sent to your registered address. The DVD contains a virtual machine image that will run for 30 days. The following are installed on the virtual machine image: Quest Development Studio for SharePoint, the application templates, the Computer Based Training (CBT) and the application templates for the CBT.
  2. If you want to try Quest Development Studio for SharePoint in your SharePoint environment, you can download the software by clicking the Download Software link on our product page. The Documentation (help files) for the Web Parts is included in the software. The help files are a good reference for the properties and attributes in the Web Parts. However, if you want to know how to configure the Web Parts, you need to download the Computer Based Training (CBT).
  3. You can download the Computer Based Training (CBT) from our product page. The CBT contains a printed training manual and videos that show you how to configure our Web Parts. If you don't have the Evaluation Kit, you should download the SharePoint sites for the CBT. You need to restore the SharePoint sites for the CBT in your SharePoint environment. Once you do that, you can perform the exercises in the CBT.
    NOTE: you need MOSS 2007 to restore the SharePoint sites for the CBT because these sites were originally created in MOSS 2007.
  4. We also provide a recorded demonstration of the capabilities of our products. This can be found on our product page. This is a good way to get a quick glance on our product without getting too technical.
  5. The following documents might be useful for you as well:

Product Overview

Quest Development Studio for SharePoint 4.2 contains 2 different set of Web Parts. The first set of Web Parts is for SharePoint 2003 (WSS v2 or SPS 2003) and the second set of Web Parts is for SharePoint 2007 (WSS v3 or MOSS 2007). You will be prompted to select the correct set of Web Parts in the beginning of the installation process. The Web Parts in the two environments are similar but not identical.

The following are the list of Web Parts for SharePoint 2003:

The following are the list of Web Parts for SharePoint 2007: The SI Web Parts enable you to display, create and edit data in your external systems. The SI Web Parts can connect with Web Services that return the following types of objects: If you have an external system that does not provide Web Services or your Web Services do not return one of the above types, you can write your own Data Access Object (DAO) Provider. Please see the System Integration Developer Guide chapter in the Quest Development Studio for SharePoint Documentation on how to write your own DAO provider.

Installation Instructions

Quest Development Studio for SharePoint requires administration rights on the SharePoint server during installation. If your SQL Server is located on a different machine than the SharePoint server, please ensure that you login as a domain user that has permission to write to the SharePoint configuration and content databases in the SQL Server.

To install the product, please click the installer executable and follow the steps provided by the installer. For complete installation instructions, see the Installing Development Studio for SharePoint chapter of the User Guide. You can also view the Installation module of the Quest Development Studio for SharePoint Computer Based Training (CBT). If you are planning to use the System Integration Web Parts, please see the System Integration Configuration File module in the CBT as well.

 

Back to Top

Summary of Upgrade Procedure

For upgrading Development Studio for SharePoint to version 4.2, uninstall any previous installation of Development Studio for SharePoint. You can uninstall the Quest Development Studio for SharePoint by Selecting Start > Quest Software > Development Studio for SharePoint > Uninstall.

NOTE


The uninstall process will delete the skin folder for the Telerik controls:

c:\Program Files\Common Files\Microsoft Shared\Web Server Extension\12\Template\Layouts\QuestSoftware\Telerik\<Version>\NET2\RadControls\<ControlName>\Skins.

Please make sure that you backup any skin folder that you added or customized.

If you had Quest Development Studio for SharePoint version 3.5.2 or later installed on your machine, the uninstall process will give you an option to backup the skin folders at the location of your choice.

After installing the new version of Quest Development Studio for SharePoint, you must restore the skin folders manually at the above location.

 

To install the product, please click the installer executable and follow the steps provided by the installer.

After you install the product, ensure the following:

  1. Microsoft ASP.NET AJAX Extension must be installed for the new Calendar View to function properly. For download, see http://www.asp.net/ajax/downloads/default.aspx
  2. An entry for HTTP Handlers is required in your web.config file for the new Calendar View. Open up your web.config in the Configuration Editor. A message indicating the missing entry will appear in the message window. Select the message and click the 'Fix It' button. Save the file. This will add the required HTTP Handlers entry.

Back to Top

History of Changes in Previous Releases

Version 4.1

SharePoint 2007 Web Parts

The following are the new features in the Web Parts for SharePoint 2007.

The following bugs were fixed in this release:

CR50694 When you select multiple items in the SI List View and click a toolbar button created with the Actions property, the operation is only performed on the last clicked item. The toolbar button is supposed to perform the operation on all selected items.
CR49482

The check-in/check-out status of the document is not preserved after it is moved using the Copy/Move panel in the Quest List View.
CR49679

The toolbar buttons in the SI List Form might appear in the wrong order when the Position attribute for the action item is specified.
CR49757

The Quest Selector always shows the value of the Date Time field as date and time even though the field settings specifies it as date only.
CR50005, CR50007

The first control in the SI List Form does not get the focus when the form is loaded if the type of that field is Choice or DateTime.
CR48669

After clicking the Download a Copy context menu item, another context menu item and the Web Part Menu > Configure menu item won't work until the page is refreshed. The workaround for this is to use the LinkTo="&lt;%FilePath%%gt;" attribute in one of the fields in the Quest List View. That attribute will turn the column into a smart link column that the user can click to download a copy of the document.

CR53504 The Edit Item and Cancel button in the list form redirectes the user to an invalid URL when the form is opened with smart link
CR51403 The cascading menu generates an error that the access key was too long even though the access key was only one character long
CR52884 The lookup field site column does not work in the list form
CR54010 Excel Viewer webpart cannot handle international characters
CR54435 The group header expansion state always follows the setting of the first grouped field

Version 4.0

SharePoint 2003 Web Parts

There are no changes for SharePoint 2003 Web Parts in this version except for the requirement to use a new license file.

SharePoint 2007 Web Parts

The following are the new features and bug fixes in the Web Parts for SharePoint 2007.

All Web Parts

  1. The help files have been consolidated into one CHM file (Compiled HTML). The CHM file gives you features such as Table of Contents, Indices to different topics, Search capability, etc. If you open up the help files using the "Web Part Menu > Help", the HTML version of the documentation is opened. This HTML version provides the same functionalities as the CHM version.
  2. The version of the Telerik control has been upgraded to Q2 2007 SP1. This might result in a different look and feel in some of your Web Parts. Another thing to note is Telerik changed the default skins of many of their controls. When they do that, the old default skin is renamed to Default2006. Wherever this happens, we have renamed the name of the default skin in our Web Parts to Default2006.
  3. The installer will give you a chance to extract the temporary setup files to a folder of your choice in the beginning of installation process.

New System Integration (SI) Web Parts

  1. The SI Web Parts contain 4 different Web Parts: SI List View, SI List Form, SI Selector and SI Chart View.
  2. The SI Web Parts provide an API to create a custom Data Access Object (DAO) Provider to connect to external systems that are not supported out of the box by the SI Web Parts. Please see the System Integration Developer Guide chapter in the Quest Development Studio for SharePoint documentation on how to write a custom DAO Provider.
  3. The SI Web Parts provide an API to create a custom configurator if the default Web Part configurator does not suit your need. Please see the System Integration Developer Guide chapter in the Quest Development Studio for SharePoint documentation on how to write a custom configurator.
  4. The SI List View, SI Selector and SI Chart View enable the user to display data from their external systems in SharePoint.
  5. The SI List Form enables the user to display, edit and create new data from and to their external systems.

Changes in Quest List View

The following are the new features in the Quest List View:
  1. The ability to turn off multi column sorting. If you turn off multi column sorting, the user can only sort the data based on one column at a time.
  2. The ability to apply CAML Filter on Folders using CAML Filter for Folders property.
  3. The List View displays the appropriate icon for the Type field in the document library. This icon also shows the check-in/check-out status of the document.
  4. The List View displays the icon for the Edit field in any list. This icon will redirect the user to the edit form for the item when clicked.
  5. The List View displays the appropriate icon for the Recurrence field in the Calendar or events list.
  6. The List View is now a consumer for the IWebPartParameters interface. The List View still supports the IRowConsumer interface. However, the IRowConsumer interface implementation is marked obsolete.
  7. The CAML Filter property supports the date range filter using OffsetDays attribute. This means you can always use the CAML Filter property instead of the complex filter property. The complex filter is slower then the CAML Filter. The complex filter is left there only for backward compatibility reasons.
  8. The ability to specify the style of a particular column by using the ItemStyle attribute in the Display Fields property. Previously, you could only do this by using the ItemCssClass attribute that required you to pre-define a CSS class first.
  9. The ability to define different styles for odd numbered rows and even numbered rows using the Item Style and Alternating Item Style properties.
  10. The following buttons are added to the toolbar: Alert Me, Action > Open with Windows Explorer (for document library), Action > Connect to Outlook (for document library, tasks or contacts list)
  11. The following menu items are added to the context menu: Version History, Workflows, Download a Copy (for document library), Edit Document (for document library), Create Document Workspace (for document library).
  12. You don't have to specify DynamicAssemblyPath attribute in the web.config file anymore when debugging a custom action class.
  13. The custom paging and grouped fields can work together now. Previously, the custom paging was always disabled whenever there were grouped fields in the List View. This could result in performance degradation when the List View displayed information from a big list.
  14. The List View prompts the user whether they want to check out a document into a local working folder before a check out is performed.
  15. A new property called Show Upload Button has been added. This property is used to control the visibility of the Upload button in the toolbar. Previously, the Upload button's visibility was affected by the Show New Item Button property. Therefore, you could not set the visibility of the New Item button and the Upload button separately.
  16. The Grid Lines property was removed because its functionality was superseded by the settings in the skins for the List View.
  17. A new property to sort the child view was added. This property is called Child View Sort Fields.
The following bugs were fixed in this release:
  1. CR43616 - The List View did not display any data when consuming a filter with a DateTime field from another Web Part.
  2. CR28557 - The List View crashed when trying to display data from an empty list.
  3. CR41670 - The CAML Configurator didn't convert Yes to 1 or No to 0 when the user setting up the condition for the Boolean field. Yes and No didn't work in the CAML filter expression.
  4. CR47438 - The List View did not send the deleted items to the recycle bin.
  5. CR29508 - The List View always checked out the file to the local drafts folder. This is an issue if the user tries to open the document from the server afterwards.
  6. CR47176 - The List View could not create a new InfoPath document by using the "New" button in the toolbar.
  7. CR49047, CR49046 - The List View crashed when the Page Size was set to a negative number or zero.
  8. CR48980 - The New button in the List View could not handle InfoPath Form Service.
  9. CR46905 - The List View did not refresh its content after the "Discard Checkout" operation was performed on a document.
  10. CR25251, CR43415 - The buttons at the top of the search panel and replace panel did not work.
  11. CR44238 - The Show User Groups and Hide User Groups properties in the List View did not work.
  12. CR44166 - The Dependent Lists property editor did not work correctly when the user tried to add the same list twice. The editor could not distinguished between the two lists when they were the same.
  13. CR43413 - The Key Field Name selection in the Dependent Lists property editor got reset when editing the list.
  14. CR46619 - The list settings in the Viewed Lists property editor disappeared after adding a child list or a dependent list.
  15. CR43411 - The Display Fields property editor mixed up the order number of the fields when the user tried to reorder the fields.
  16. CR43399 - The List View did not show the values of the People and Group field correctly when multiple values were allowed in the field settings.
  17. CR43582 - The List View always displayed the values of a currency field with 2 decimal places even though the field setting specified it differently.
  18. CR42316 - The CalculatedValue field in parent record in a hierarchical List View will display System.Data.DataRowView when the parent record is expanded.
  19. CR37711 - The target folders in the Copy/Move panel were not listed alphabetically.

Changes in Quest List Form

The following are the new features in the Quest List Form:
  1. The List Form displays the version of the displayed or edited document properties at the bottom of the form.
  2. The following buttons are added to the toolbar: Manage Copies, Version History, Workflows, Alert Me.
  3. The List Form supports the IWebPartRow interface. The List Form still supports the IRowProvider interface. However, the IRowProvider interface implementation is marked obsolete.
  4. The List Form is now a consumer for the IWebPartRow interface. The List Form still supports the IRowConsumer interface. However, the IRowConsumer interface implementation is marked obsolete.
  5. You don't have to specify DynamicAssemblyPath attribute in the web.config file anymore when debugging a custom action class.
The following bugs were fixed in this release:
  1. CR41854 - The List Form crashed when it was connected with a Quest Selector and you did not select any field when connecting them and click the Finish button.
  2. CR41772 - The List Form displayed an error message when one of its field consume a row from a Quest Selector and the user selected "None" in the selector.
  3. CR41671 - The rich text editor didn't adjust its height based on the number of lines setting in the field.
  4. CR47438 - The List Form did not send the deleted items to the recycle bin.
  5. CR46891 - The List Form loaded very slowly when displaying an item from a very big list.
  6. CR48298 - When using Multiple File upload feature on a document library that contains multiple content types, the last document that was uploaded was always assigned the default content type.
  7. CR49477 - The hyperlink for the file name when the Form Type was set to DisplayDocument did not work correctly for InfoPath Form Service.
  8. CR49057 - The List Form crashed when trying to display a folder metadata and the Form Type was set to DisplayDocument.
  9. CR48457 - There were a few occasions when the Multiple File Upload did not prompt the user for metadata.
  10. CR46542 - The spell checker button in the rich text editor was shown even though the rich text editor did not have spell checking capability.
  11. CR45252 - The People and Group field in the List Form showed users from every group even though the field setting only specified that only users from a specific group were shown.
  12. CR45035 - Users could still compose an email message even though the Allow Custom Message property was set to false.
  13. CR44653 - The List Form did not validate required Date Time or People and Group fields.
  14. CR43397 - The rich text editor did not change its appearance after the skin name was changed.

Changes in Quest Chart View

The following are the new features in the Quest Chart View:
  1. The Chart View is now a consumer for the IWebPartParameters interface. The Chart View still supports the IRowConsumer interface. However, the IRowConsumer interface implementation is marked obsolete.
  2. A new property to control the color of the plot area was added. This property is called Chart Plot Area Color. The plot area is the area contained within the X Axis and Y Axis.   
The following bugs were fixed in this release:
  1. CR39300 - The search panel for the chart view did not set the default value that was specified in the Field element in the Searched Fields property.
  2. CR41830 - The Chart View crashed when the value of the MinValue attribute is greater than the value of the MaxValue attribute.
  3. CR49575, CR43616 - The Chart View did not display any data when consuming a filter with a DateTime field from another Web Part.
  4. CR36200 - The SortFieldName and SortFieldOrder in the Configuration property did not work. When specified, they did not sort the values in the X axis at all.
  5. CR49457 - When the ShowItemLabel attribute was set to false, the X Axis values turned to 1, 2, 3, etc and the X Axis values became the item labels. The correct behavior when the ShowItemLabel is set to false is the X Axis values stay the same and the item labels should become invisible.
  6. CR49453 - The chart image format was always BMP even though the Chart Image Format property was set to some other image types.
  7. CR49817 - The Chart View crashed when connected to Microsoft List View using a DateTime field.
  8. CR49566 - The Chart View showed Date Time value in the X Axis with wrong format.
  9. CR49513, CR48678 - The Chart View did not show numbers or currency in the X axis, Y axis or Item Labels in correct format. The numbers did not have comma or thousands separator.
  10. CR48109 - There were a few occasions when the Chart View generated the following error: "A generic error occured in GDI+".
  11. CR43084 - The Configuration property editor was not aware of the "Turn On List View Link Mode" property.

Changes in Quest Selector

The following are the new features in the Quest Selector:
  1. The Selector supports the IWebPartRow interface. The Selector still supports the IRowProvider interface. However, the IRowProvider interface implementation is marked obsolete.
The following bugs were fixed in this release:
  1. CR42715 - The Selector crashed when the Selector Width, DropDown Width or DropDown Height properties were set to a negative value.
  2. CR46550 - The Selector generated a null reference exception when pointing to an empty list and the Show Empty Selection property was set to true.

Changes in Quest Multi Selector

The following are the new features in the Quest Multi Selector:
  1. The Multi Selector supports the IWebPartRow interface. The Multi Selector still supports the IRowProvider interface. However, the IRowProvider interface implementation is marked obsolete.

Changes in Quest Item Display

The following are the new features in the Quest Item Display:
  1. The Item Display supports the IWebPartRow interface. The Item Display still supports the IRowProvider interface. However, the IRowProvider interface implementation is marked obsolete.
The following bugs were fixed in this release:
  1. CR49588 - In some cases, the Item Display generated an error that the key has been added.

Changes in Quest Panel Menu

The following bugs were fixed in this release:
  1. CR49370 - The panel in the panel menu could not be expanded when there was a Quest List Form on the page with empty required fields.

 

Back to Top

For More Information

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com/.

From SupportLink, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.

 

Back to Top

 

© 2008 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

http://www.quest.com/

Email: legal@quest.com

Refer to our web site for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk,   Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

 

Third Party Contributions

This product includes the copyrighted software of the following third party suppliers:

ComponentOne Studio for ASP.NET 2005, FreeTextBox, Infragistics NetATelerik RadControls for ASP.NETdvantage, Matt Kruse Calendar Popup, Matt Kruse Color Picker, QuickWebSoft Event Calendar, Telerik RadControls for ASP.NET.

 

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

 

Back to Top