Quest® Development Studio for SharePoint
Version 4.0

Release Notes

February 2008

© Quest Software, Inc. 1999-2008.

Contents

License Upgrade
Getting Started
Overview 
System Requirements
Installation
What's New
Known Issues
Global Operations
History of Changes In Previous Releases
For More Information

 

License Upgrade

Quest Development Studio for SharePoint version 4.0 requires a new license file for version 4.x. 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

 

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:

    • What's new in Development Studio 4.0

    • Quest Development Studio 4.0 Technical Brief

    • SharePoint for Universal Access White Paper

Back to Top

 

Overview

Quest Development Studio for SharePoint 4.0 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 major addition to this version is the System Integration (SI) Web Parts. The SI Web Parts enable you to display, create and edit data in your external systems. In this release, 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.

Back to Top

 

System 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. 

 

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.
     
  2. 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:

    • SQL Server 2000, SQL Server 2000 Enterprise Edition, SQL Server 2000 Desktop Engine (WMSDE).
    • SQL Server 2005 Enterprise Edition, SQL Server 2005 Standard Edition, SQL Server 2005 Workgroup Edition, SQL Server 2005 Express Edition, SQL Server 2005 Developer Edition.

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

 

Installation

In order to install this version of Quest Development Studio for SharePoint, you must uninstall any previous installation of Quest 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.

Back to Top

 

What's New

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. CR43593 - The first control in the List Form retained the focus after the user press the tab key once. The user must press the tab key twice before the focus was moved to the next control.

  15. 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


Known Issues

SharePoint 2007 Web Parts

The following are the known issues in SharePoint 2007 Web Parts:

  1. The installer does not work if you run IIS in 32-bit mode in 64-bit Windows 2003 Server. You must run IIS in 64-bit mode in 64-bit Windows 2003 server for our Web Parts to work.

  2. The SharePoint 2007 Web Parts set does not contain Quest Calendar Web Part. The Quest Calendar Web Part will be included in a future release for SharePoint 2007 Web Parts.

  3. The Quest Bread Crumb, Quest User Display are not part of the release for SharePoint 2007 because SharePoint 2007 contains built-in bread crumb and user display.

  4. The Quest Page Redirector is not part of the release for SharePoint 2007 and its functionality may be included in a future Quest Cascading Menu and Quest Panel Menu for SharePoint 2007.

  5. The Quest List Form cannot edit a particular instance of an event. It can only edit the property of the event series.

  6. 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.

  7. 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.

  8. CR43417 - The LinkTo field in the Quest List View will not work if the field name contains parentheses.

  9. CR46535 - The Quest List View does not sort the value in the People and Group fields when multiple values are allowed.

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

  11. 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).

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

  13. 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.

  14. CR49580 - The Quest List View does not have Send To Document Center context menu item.

  15. 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.

  16. 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.

  17. 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.

  18. 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.

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

  20. CR44672 - The Quest List View does not display email addresses as hyperlink.

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

  22. CR49853 - The SI List View does not retain the expand/collapse of the grouped fields after the page is posted back.

  23. 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.

SharePoint 2003 Web Parts

The following are the know issues in the SharePoint 2003 Web Parts:

  1. 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.
  2. 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


Global Operation

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

 

History of Changes In Previous Releases

Version 3.5.2

Licensing

In the previous version, the license is checked when the Web Parts are loaded on the page for the very first time. In this version, we perform the license check during installation. Please see the note in the Installation section above.

Bug Fixes

The following bugs are fixed in the SharePoint 2007 Web Parts:

  1. The Quest List View and the Quest Chart View do not show any record when filtered with a date field.

  2. The Quest List View configurator failed when the site is saved as a template and then instantiated in different URL in different server where the original site collection is not accessible. This is because the Quest List View internally stored the URL of the original site.

  3. The user was unable to checkout or delete the document from the Quest List View if the document library resided in another site collection.

  4. The user could not connect the Microsoft Text Filter with Quest List View. When attempting to do so, the popup dialog box appeared blank instead of showing the dropdown with fields to filter.

  5. In a certain machine, the Web Parts could not be able to find the license information and thus would not work.

The following bugs are fixed in the SharePoint 2003 Web Parts:

  1. The Quest List View did not display the Modified and Created date of a document in a document library properly. It displayed the date in "YYYY-MM-DD hh:mm:ss" format regardless of the regional settings of the site.

  2. The Quest List View generated error if the user tried to delete, checkout or set an alert on a document if the document library resided in another site collection.

  3. In a certain machine, the Web Parts could not be able to find the license information and thus would not work.

Version 3.5.1

The Web Parts for SharePoint 2003 did not have any update in this release.

The following bugs are fixed in the 3.5.1 Patch Release for SharePoint 2007 Web Parts:

  1. The Quest List View opens wrong URL for the edit form when pointed to User Information List

  2. The document Name field is blank when the Quest List Form is set to DisplayDocument

  3. The Quest List View generates an error when searching based on the date field and the regional setting is set to English (UK)

  4. The Quest List View mixed up the link for the upload document when the NewFormUrl attribute in the Viewed Lists property is defined

  5. When the web page is not checked out, the Quest Selector will generate an error when the user tries to select another entry in the dropdown.

  6. The Title attribute does not have any effect in the grouped field in the Quest List View.

  7. Quest Chart View crashes the web page when Y axis min/max/step were set incorrectly.

  8. Some of the fields in the Quest List View will show System.Data.DataViewRow if SiteURL of the list is set to "/".

  9. The 'Filter' item in the Quest List View toolbar should be hidden when no searched fields are defined.

  10. The Quest List View crashes when a field name that is being used in the display fields property is changed

  11. The ER Diagram in the Quick Start Guide shows wrong Foreign Key for the Tasks list

  12. The help file for the Custom Action is missing an image.

  13. If the Web Parts are unable to locate the license information, more trace information will be provided.

Version 3.5

The Web Parts for SharePoint 2003 have not been updated since the previous version (3.0) was released.

This release are the first release where the Web Parts for SharePoint 2007 are available. For those of you who are familiar with our SharePoint 2003 Web Parts, the following are some new features that we put into our SharePoint 2007 Web Parts.

General Changes to all Web Parts

  1. The Web Parts have new configurator. The new configurator is much easier to use than the old one. The new configurator enables you to edit every Web Parts property. You don't have to switch between the configurator and the "Modify Shared Web Part" property panel anymore. You can access the configurator by clicking Web PartMenu > Configure. The only configurator that is not done is the configurator for the Quest Panel Menu.

  2. New and improved CAML Filter. The old CAML Filter is awkward and not very intuitive. You will find that the new CAML filter is easier to use than the old one.

  3. The Web Parts look and feel can be customized with Skins. Our product is shipped with some predefined skins. You can create your own skin if none of the predefined skins fulfills your need.

Changes in Quest List View

The details for the changes described below can be found in the Quest List View Help File (Web PartMenu > Help).

  1. The Quest List View can handle multiple content types if your list supports multiple content types. You can display the fields from any content type. The Quest List View will also create different New button for each content type and folder.

  2. The Quest List View only shows items from the selected folder if the folder panel is enabled (by setting Show Folders Button to true). Formerly, the Quest List View would display items from the current folder of every list that you display in the Quest List View.

  3. We add mass replace capability in the Quest List View. The Quest List View will display the replace panel if you click Actions > Replace in the Quest List View's toolbar. You can replace the value of a certain field for multiple rows at once. You can either select the items that you want to replace or define a condition for which items to be replaced.

    NOTE

     

    If you try to replace hundreds of rows at once, the replace action may get a timeout error before it is able to finish its operation. This feature works very well if you select the items that you want to replace or you narrow down the items that you want to replace with search criteria.

     

  4. You can aggregate the values of one or more fields and display its result in the group header. This feature works if you set the Grouped attribute of the Field element to true. In that case, you can add one or more aggregate functions (e.g.: Count, Sum) to that grouped field.

    NOTE

     

    If you are displaying items from a big list or rolling up information from multiple lists, we recommend that you do not group any fields in the Quest List View. When you group any fields in the Quest List View, the Quest List View must retrieve all items from the list to the Web Server. If you have a big list, this can affect the performance of your Web Server.

    In general, to increase the performance of the Quest List View:
    1. Do not group any fields.
    2. Use CAML Filter instead of Complex Filter.
    3. Use Next and Prev paging mode instead of Numeric paging mode.

     

  5. You can display information from the parent list and child list together in the Quest List View. We call this feature Hierarchical List View. For example, you can display Customers and Orders information, Tasks and Task Serial Notes in the same view.

  6. We add recursive rollup capability into the Quest List View. You can specify that you want to rollup information from lists with a certain name from every sub-sites. This keeps your from maintaining the list of lists that you want to display in the Quest List View in a dynamic environment where you add a sub-site often.

    NOTE

     

    The more sub-sites you have, the more time it takes to retrieve and display the data. Please make sure that your hardware can handle the number of sub-sites that you want to roll up with this feature.

     

  7. You can sort the entries in the Quest List View by clicking the grid header instead of the sort panel. The sort panel was no longer there.

  8. You can copy or move documents to another folder or another document library. Please note that this functionality is only available for document library. In order to enable this functionality, check the Show Copy/Move Button property in the Toolbar Appearance tab.

  9. When the folder panel is enabled, you will see the name of the current folder above the grid. This gives you visual clue of which folder that you are in even when the folder panel is in the collapsed state.

  10. The ability to define custom actions for the Quest List View. This capability enables you to add custom buttons in the toolbar and custom item in the context menu. The buttons and context menu items can be connected to pre-built actions or your own custom actions.

  11. If you use javascript in the CalculatedValue attribute in the Viewed Lists property, you can only call one javascript function that returns a string. This means the javascript function that you use in the SharePoint 2003 Quest List View may not work properly. Please see the help file of the Quest List View for more information.

Changes in Quest List Form

The details for the changes described below can be found in the Quest List Form Help File (Web PartMenu > Help).

  1. The Quest List Form can display fields from multiple content types if you list supports multiple content types. All you have to do is to define one Fields element for each content type. The Quest List Form will display all fields from the content type if the Fields element for that content type is not defined.

  2. You can view, attach and manage the attachment in the list item using the Quest List Form. The attachment section shows up at the bottom of the Quest List Form. This feature is available in the NewListItem, DisplayListItem and EditListItem mode.

  3. You can have the toolbar at the top, bottom or both of the Quest List Form.

  4. You can filter a lookup or cross-site lookup field with another lookup or cross-site lookup field. This functionality is like having a Quest Multi Selectors embedded in the Quest List Form itself. This is very handy in case you have something like Region and Office Location lookup fields in the Quest List Form. Using this feature, you can display only office locations that are in the selected region.

  5. The Quest List Form can store the item that it currently displays and edit in the session (the session variable name is defined in the Session Name property). Formerly, you had to use a hidden persistent selector to store the displayed item in the session and this process was tedious.

  6. You can define custom actions for the Quest List Form. This capability enables you to do things like having a second Save button that goes to different page after saving the item, validate the entry with complex validation logic, copy the item to another library after saving it, etc.

  7. There is a new property to control the visibility of the Attachment field. This property is called Display Attachment Field. If you set this to true and the attachment capability in the list is enabled, the Quest List Form will display the field to attach one or more files.

  8. Manage Permissions button was added to the Quest List Form toolbar. This button will open the page to manage permissions on the list item. You can hide this button by setting the Show Manage Permissions button property to false.

  9. The first editable control in the Quest List Form will grab the focus when the Quest List Form is loaded for the first time.

  10. The combobox control for the choice fields, single value lookup fields or cross-site lookup fields will auto-complete as you type in its input field.

  11. You can sort and filter the regular lookup field by using the SortField and CamlFilter attribute. Previously, this capability only exist for cross-site lookup field. This capability enable you to use regular lookup field even when you need sorting and filtering.

Changes in Quest Chart View
  1. The ability to apply a complex filter to the data series. This capability enables you to display the data from the same field in different series, where each series contains different filter. For example, you can display total shipment from different warehouses by using the warehouse name for the filter in the series.
Changes in Quest Selector

  1. We add the CAML Filter Expression property to the Quest Selector. CAML Filter is more efficient than the complex filter in the Filter Expression property.

  2. You can display the choices in the Quest Selector's dropdown in a grid format. You do this by defining the Display Fields property. This makes it easier for the user to see the data.

  3. You can type into the Quest Selector's input part and the Quest Selector will go to the entry that match the input.

Changes in Quest Multi Selector

  1. The capability to hide a certain selector. Hiding the selector is useful in case you do not want the user to change the value in one of the selectors.

  2. The new changes to the Quest Selector also applies to the Quest Multi Selector.
Changes to Quest Panel Menu
  1. You can define multiple panels in the panel menu in one list because the list for the panel menu supports "Parent Menu Id" column. The item with no "Parent Menu Id" will become a new panel. You can also cascade the menu items in the panel menu if you wish eventhough we recommend to use the Quest Cascading Menu Web Parts for this purpose.
Changes to Quest Cascading Menu

  1. The cascading menu supports Horizontal and Vertical orientation.

Back to Top

 

For More Information

Other Document Sources

The complete Quest Development Studio for SharePoint documentation suite includes the following:

Contact Quest Software:

Phone: 949.754.8000 (United States and Canada)
Email info@quest.com
Mail:

Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA  92656
USA

Web site: www.quest.com

Please refer to our Web site for regional and international office information.

Contact Customer Support:

Quest Software’s world-class support team is dedicated to ensuring successful product installation and use for all Quest Software solutions. If you have questions, please contact our technical support staff. Please include the version number and, if your question is about an error message, include the error text as well.

SupportLink: www.quest.com/support
Email: support@quest.com

You can use SupportLink to do the following:

  • Create, update, or view support requests
  • Search the knowledge base
  • Access FAQs
  • Download patches

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