Quest®
Web Parts for SharePoint
Version 5.1
Release Notes
October 2009
Contents
Welcome to Quest
Web Parts 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
|
NOTE |
Please
read this if you have custom skin files for the qCalendarView web part,
Rich Text Editor in the list form or the tree view for the complex
category field in the list form.
The above controls were affected by the upgrade of
the Telerik controls. We upgraded the Telerik version in our product
from Q2 2008 to Q2 2009. Unfortunately, the skin files for the Q2 2008
are not compatible with the skin files for the Q2 2009. Therefore, you
must do one of the following:
-
Recreate your skin files by copying one of the
existing skin files under C:\Program Files\Common Files\Microsoft
Shared\web server extensions\12\TEMPLATE\LAYOUTS\QuestSoftware\Telerik\Q22009\Skins.
-
Upgrade your old skin files using the skin
converter that is provided by Telerik. The skin converter program
can be found here:
http://converter.telerik.com/skinconverter/.
Please note that we strongly recommend that you take
the first option, which is to recreate the skin files by using one of
the new Q2 2009 skin files. Based on our test, the converted skins do
not always work. Besides, the old skins do not support the insert image
dialog box that is used by the rich text editor. Please note
that we do not support the incompatibility issue between your old skins
and the converted skins. If you take option #2, you do it at
your own risk.
Please note that this upgrade does not affect the
custom skins for the other web parts, such as the qListView, qPanelMenu,
qCascadingMenu, etc. The other web parts still uses the older version of
the Telerik control, which is version Q2 2007 SP1.
|
|
NOTE |
If you
are currently using version 4.x, you need a new license to upgrade to version 5.1.
Please do not attempt to upgrade to version 5.1 if you do not have the
new license file for Quest Web Parts for SharePoint 5.1.
To upgrade your existing license, please go to the
following URL:
http://license.quest.com/upgrade.
If you encounter an issue upgrading your license
using this page, please contact your sales representation to get a new
license file or send an email to
license@quest.com.
Quest Web Parts for SharePoint does not include
SharePoint 2003 Web Parts anymore. If you need SharePoint 2003 Web
Parts, please contact support for instructions on how to obtain Quest Development Studio
for SharePoint 4.2.
|
Thank you for installing Quest Web Parts for
SharePoint 5.1.
Quest Web Parts for SharePoint enhances SharePoint’s
application development capabilities with drag-drop-configure Web parts,
reducing 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.
Back
to Top
This release of Quest Web Parts for SharePoint includes the following new
features:
Configuration Editor tool
- (Req 3818) The Configuration Editor Tool contains new
functionality to mass index discussion lists. This is useful in case of
a Notes migration scenario where you migrated multiple discussion lists and
you need to index those lists after the migration is done.
- (CR 73589) The QuestSoftware section editor contains 3
new parameters: Max Rollup Depth, Max Rollup ListCount and Max
Query Row Count. These three parameters can be used to restrict how
deep the rollup operation should go, how many lists should be included in
the rollup operation and the maximum number of rows should be returned
during a query to the SharePoint server, respectively. Please see the help
file for the Configuration Editor tool for more detail.
All Web Parts
- (Req 4086) We added 3 pages to the SharePoint Central
Administration to manage the deployment of the web parts. These three pages
enable you to select which web parts to deploy in the web
application level and site collection level.
- (Req 3832) We added HideUserGroups and ShowUserGroups
attributes to the Custom Actions property in every web part that supports
it. These new attributes enable you to show or hide the custom action
(context menu item and toolbar button) visibility based on the group
membership of the current user.
- (Req 4004) We upgraded some of our Telerik controls to
version Q2 2009. This upgrade affects the qCalendarView, qDiscussionView
and qListForm web parts. Please note that the skin files in version Q2 2009
have a new format which is not backward compatible with the Q2 2008 skins.
Please note that some of the web parts such as qListView still use Q2 2007
SP1 version and therefore are not affected by this upgrade. Please read the
note at the beginning of this release notes regarding this upgrade for more
details.
- (CR 70471) We added new custom action type called
ReturnToMasterChart. This custom action can be used to return to the
master chart page based on the MCID HTTP parameter.
- (CR 68292) You can use "." (single dot) as the List
Name property in the qListForm or the ListName attribute in the Viewed Lists
property of qListView, qCalendarView, qChartView and qDiscussionView when
you place those web parts in AllItems.apsx, NewForm.aspx, EditForm.aspx,
DisplForm.aspx or Upload.aspx. The "." will be interpreted as the name of
the list that owns the page. This capability increases the usability factor
of your list template because you don't have to change the name of the list
when you instantiate the list template using a different name.
qListForm
- (Req 4013) The ability to call a custom action code to
initialize one or more fields in the form.
- (Req 3821) The ability to define conditional behavior
of the form components (field, group of fields and tab) using the new Form
Component Behavior property. There are four types of conditional
behavior that you can define: HideWhen, ShowWhen, EnabledWhen and
DisabledWhen. For example, you can define the behavior to show the Resolved
By and Resolved Date fields when the Status field is changed to Resolved.
- (Req 2768) The rich text editor contains the ability to
insert an image into the editor. If the image is in your local drive, the
Insert Image dialog box will enable you to upload the image as an attachment
to the list item.
- (Req 4012) The qListForm has a new Form Type called
CreateDocument. This new Form Type enables you to create a new document
based on the template in the content type or external list and to fill in
the metadata for the newly created document at the same time.
- (Req 3202) We added HideUserGroups and ShowUserGroups
attributes to the Display Fields property to enable hiding or showing
certain fields based on the group membership of the current user.
- (CR 70829) The qListForm has a new property called
Check Overwrite Existing File CheckBox. This property determine the
default value of the 'Overwrite Existing File' checkbox in the upload document
form. This checkbox is only available when you set the Form Type to UploadDocument.
- (CR 64676) The qListForm can now auto-fill a
field based on the value of an HTTP Parameter.
- (CR 65753) The Field element in the Display Fields
property supports a new attribute called AllowEdit. This attribute
allows the auto-fill field, such as FixedValue, ConsumeValueFromSession,
ConsumeValueFromRowFromAnotherWebPart to be edited.
- (CR 68435) The Field element in the Display Fields
property supports a new attribute called HideSelectAndUnselectAll.
This attribute allows you to hide the Select All and Unselect All links in
the multi choice field to be hidden.
- (CR 69190) We added a new property called Drop Down
Skin Name to control the appearance of the drop down control for the
lookup field, choice field and cross-site lookup field.
- (CR 71211) We added a new property called Show Save
File As TextBox to enable the user to show the control to rename the
file during single file upload. The user may need to rename the file in case
the document library already contains a file with the same name.
qListView
- (Req 3202) We added HideUserGroups and ShowUserGroups
attributes to the Display Fields property in order to enable hiding or showing
certain fields based on the group membership of the current user.
- (CR 62318) The filter panel supports master-detail
capability now. The master-detail capability enable you to filter a lookup
or cross-site lookup field based on another lookup or cross-site lookup
field.
- (CR 66235) The qListView now supports the point of presence
feature in the People and Group field.
- (CR 67723) The filter panel supports filtering the list
view by the Item Location field.
- (CR 71121) The filter panel supports the "Contains"
operator for filtering the Lookup field, Choice field and People and Group
field. When the "Contains" operator is selected, the filter control will
turn into a text box where the user can enter the key word for the filter.
- (CR 70232) The filter panel supports searching all
fields. This capability can be enabled by setting the Show Search All
Fields Control in Filter Panel property. The search all fields criteria
will be run against the following field type in the list: Single line of
text, Multiple lines of text, Choice, Lookup, Person or Group and Hyperlink
or Picture.
- (CR 70694) We added a new property called Fields
Excluded from Replace Panel. This property enables you to define what
fields should be excluded from the Field Name dropdown in the replace panel.
qDiscussionView
- (Req 3202) We added HideUserGroups and ShowUserGroups
attributes to the Display Fields property in order to enable hiding or showing
certain fields based on the group membership of the current user.
qSIListForm
- (Req 4013) The ability to call a custom action code to
initialize one or more fields in the form.
- (Req 3821) The ability to define conditional behavior
of the form components (field, group of fields and tab) using Form
Component Behavior property. There are four types of conditional
behavior that you can define: HideWhen, ShowWhen, EnabledWhen and
DisabledWhen. For example, you can define the behavior to show the Resolved
By and Resolved Date fields when the Status field is changed to Resolved.
qPanelMenu
- (CR 64153) The qPanelMenu has a new property called
Expand All Parent Menu Items On Load. This property will expand all the
menu items that has sub menu items underneath it when the page is loaded.
Back
to Top
The following is a list of
issues addressed and enhancements implemented in this release of Quest
Web Parts for SharePoint.
|
CR73635 |
The Upload Multiple Documents link redirect the
user to single file upload when the Show Upload Button property is set
to Multiple File Upload only. |
|
CR74158 |
The display format in the Calculated Value is not
working. For example, when you specify <%{0:c}Price%> it won't format
the Price field as currency. |
|
CR74113 |
The qListView shows System.Data.DataRowView in the Edit field when it
points to a list that is not a document library. |
|
CR74145 |
The qItemDisplay cannot be connected to the qListView using "Send Row
To" and "Get Filter From" |
|
CR73971 |
The qListForm does not validate the required multi value lookup field
during save. |
|
CR73967 |
The qListForm crashes when autofilling a number field and the source
field is empty. |
|
CR68354 |
The Title Resource ID attribute is filled in with
the value of the Title attribute when editing a Field element in the
Display Fields property editor of the qListView. |
|
CR72970 |
The Manage Permissions and Check In/Out buttons should not appear in the
qListForm (in DisplayListItem mode) when the user does not have
permission to carry out those operations. |
|
CR41293 |
The qListView displays the plain text multi line
text field in one line eventhough the entry contains line break in it. |
|
CR72369 |
The qListForm does not display the People and Group fields according to
the field setting when the People and Group field is auto filled. The
People and Group field is always displayed by the user name eventhough
the field is set to be displayed with another
field, e.g.: Phone Number. |
|
CR72531 |
The qListForm will use the ID of the looked up item instead of the text
when you refer to a lookup field in the CalculatedFormat field. |
|
CR72654 |
The qCalendarView does not show the last day of the appointment if the
end date is a DateTime field with DateOnly format. |
|
CR72969 |
The CAML Filter for Folders property does not support dynamic value,
e.g.: value taken from HTTP parameter. |
|
CR71451 |
The alert email only sends partial information about the list item to
the user |
|
CR70865 |
The CAML filter editor should use the output field type instead of
Calculated when constructing CAML filter for Calculated field. |
|
CR69904 |
Some of the operator in the CAML Filter editor is not grammatically
correct. For example, "Equals To" should say "Equal To". |
|
CR68250 |
The Include Sub Folders checkbox in the qListView's filter
panel should be checked by default. |
|
CR65797 |
The Rich Text Editor control in the qListForm
cannot use a custom skin name. |
|
CR70009 |
The qListForm does not display the Attachment field when the Form Type
property is set to DisplayListItem. |
|
CR70691 |
The ShowValues in the Chart Attributes property does not work. The
qChartView and qSIChartView still shows the values in the chart even
though this attribute is set to false already. |
|
CR70773 |
The DateTime field value that is modified in the custom action is not
persisted by the qListForm. |
|
CR71489 |
The qChartView does not copy the HTTP
parameter of the current URL into the drill down chart URL when the user
clicks the chart to drill down. This causes problem when drilling down
more than 1 level. |
|
CR71723 |
The qListForm auto fill the field with ID1;#Value1;#ID2;#Value2 if the
source field is a multi value lookup field. The
value should be presented as Value1;Value2 instead. |
|
CR71964 |
qListView experiences performance issue when displaying data from a big
document library and the Type and Edit column are displayed. |
|
CR72483 |
The chart view crashes when the value that is used in the X axis
contains ' in it. |
|
CR71642 |
The qListView shows empty value in a Yes/No field as "Yes". |
|
CR71489 |
The qChartView does not include the other
HTTP Parameters in the URL when drilling down. This is an issue when you
drill down 2 level deep because at the second drill down, you lose the
context of the drill down at the first level. |
|
CR71451 |
The alert email only sends partial information about the list item to
the user when the item was created using qListForm. |
|
CR69274 |
The Web Part crashed if the user invokes "Modify Shared WebPart" in the
Web Part Menu. |
|
CR70253 |
The qChartView generates an error when a People and Group field is used
in X Axis. |
|
CR70203 |
When auto filling a single line of text field using a lookup field, the
qListForm uses ID;#Title format instead of just the plain title of the
selected item in the lookup field. |
|
CR70218 |
The qListView does not sort the group header correctly if it is a lookup
field. |
|
CR70114 |
The qChartView and qSIChartView displays 0 if a
certain data point in the chart does not have any data in the list or in
the external system. In case of no data, the qChartView and
qSIChartView should not display any data plot at all for that particular
data point. |
|
CR70214 |
The qChartView crashes when the anchorSides attribute is defined in the
Chart Attributes property. |
|
CR69481 |
The list view does not rollup list item from subsites two levels down with item level permission granted. |
|
CR69571 |
The chart view does not handle mulitple lists when worked in List View Link Mode. |
|
CR65797 |
The Rich Text Editor cannot take the custom skin name |
|
CR69877 |
The 64 bit installer failed to add solution package to SharePoint store with null reference error. |
Back
to Top
The following is a list of issues known to exist at the time of Quest Web
Parts for SharePoint release.
|
CR68091 |
The Print button in the list view opens up a blank page the first time
it is invoked. You need to close the window for the blank page and try
it again for it to work. |
|
Telerik |
If you have another third party Web Part that uses Telerik control of
different version on the same page, one of the web parts may not work
properly. For example, it has been reported that the Quest Selector will
not work if there is another Web Part that uses RadComboBox of different
version than the one the Quest Selector uses. |
|
CR65512 |
Tree view panel displays wrong Categorized discussions' Tree when one of
Category name is selected and "Delete" button is pressed |
|
CR65549 |
The value in the left-justified column does not line up with the header |
|
CR65415 |
Group fields are not displayed correctly if some lookup values are blank |
|
CR65221 |
The ItemStyle attribute is not applied to the group header |
|
CR63578 |
The group header coloring disappears after the parent record is expanded |
|
MICROSOFT |
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. |
|
CR56120 |
The cancel button in the list form causes
validation when the Next Page URL or Go Back URL is set to the same
page. |
|
CR61851 |
Selected Item Style property in the Quest List View does not override
the selected item style defined by the skin for some skins such as
Black, Default, Telerik and Vista. |
|
CR62690 |
The column header in the SI List View is not
aligned according to the HorizontalAlign attribute of the Field element
in the Display Fields property. |
|
CR60571 |
There are several issues for Exporting feature in
the Quest List View and SI List View:
1. The column generated with CalculatedValue cannot be imported
2. The column that contains images like Type column of a document
library cannot be imported
3. If you have too many columns displayed in your list view, the PDF
export result will squeeze all the columns into the width of the page.
4. When exporting to CSV, blank cell will be replaced with
|
|
CR52913 |
The options for multiple value lookup field contains (none) when the
value is optional |
|
CR54423 |
Quest Item Display does not filter out the list view when it
is empty. |
|
CR59107 |
The color value in RGB format is converted to #XXXXXX format by the
Color Appearance property editor in the Calendar View |
|
CR59273 |
The numeric pager did not get displayed correctly for some skins in the
Quest List View and SI List View. |
|
CR59589 |
The DateTime field will be blanked out when using the replace panel in
the Quest List View and the new value is set to a string. |
|
CR60456 |
The date only field always displays the time part in the Quest SI
Selector |
|
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). |
|
MICROSOFT |
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. |
|
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.
|
|
CR53213 |
The lookup field postback causes
404 error when the list name contains " - " in the list form |
Back
to Top
You must ensure your system meets the minimum hardware and software
requirements described in this article:
http://office.microsoft.com/en-us/sharepointserver/HA101945391033.aspx
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:
- Windows 2000, Windows XP, Windows 2003, Windows Vista
client with IE6, IE7 or IE8.
Level 2 Web browsers
- Win 2000, Win XP, Win2003, Vista client with Firefox 1.5,
Mozilla 1.7 or Netscape 8.1
- Unix/Linux with Firefox 1.5 or Netscape 7.2
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.
Back
to Top
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
The first question that people usually ask is "How do I get started
with Quest Web Parts 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/web-parts-for-sharepoint/.
-
If you want to try Quest Web Parts 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).
-
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. 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.
-
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.
Product Overview
Quest Web Parts for SharePoint contains 18 Web Parts
for SharePoint 2007:
-
Data Viewer Web Parts: qListView, qChartView, qExcelViewer,
qCalendarView, qDiscussionView
-
Data Entry Web Parts: qListForm
-
Data Selector Web Parts: qSelector, qMultiSelector, qItemDisplay
-
Navigation Web Parts: qPanelMenu, qCascadingMenu, qPageRedirector
-
Display Web Parts: qCaptionDisplay, qHelpLink
-
System Integration (SI) Web Parts:
qSI ListView, qSIListForm, qSISelector, qSIChartView
The SI Web Parts enable you to display, create and edit data in your
external systems. Out of the box, the SI Web Parts
support the DAO Provider for:
- Web Services
- SQL Server
- Oracle
- Domino Server using XML over HTTP
The SI Web Parts can connect with
Web Services that return the following types of objects:
- Data Set (System.Data.DataSet)
- Data Table (System.Data.DataTable)
- Data View (System.Data.DataView)
- Array of Data Set. The SQL
Server HTTP Endpoint returns this kind of data. SQL Server HTTP Endpoint is
the method to expose your stored procedure as Web Services. Please see the
SI Developer Guide document on how to set one up.
- Array that can be serialized into XML and then converted
into Data Set.
- XML String that can be converted to Data Set.
- XML Node that can be converted to Data Set.
If your external system is not supported, you can
write your own Data Access Object (DAO) Provider. Please see the System Integration Developer Guide
chapter in the Quest Web Parts for SharePoint Documentation
on how to
write your own DAO provider.
Installation Instructions
Quest Web Parts 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 Quest Web Parts for
SharePoint chapter of the User Guide. You can also view the Installation
module of the Quest Web Parts 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.
After you install the product, ensure the following:
- An entry for HTTP Handlers is required in your web.config file for the
ASP.NET AJAX to function properly. 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
For upgrading Quest Web Parts for SharePoint to version
5.1, uninstall any previous installation of Development Studio for SharePoint
or Quest Web Parts for SharePoint.
You can uninstall the old version of the product by Selecting
Start > Quest Software > Development Studio for SharePoint/Quest Web Parts
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
Web Parts for SharePoint, you must restore the skin folders
manually at the above location.
|
Back
to Top
Version 5.0
The following are the new features in this release:
All Web Parts
- The term "Web Part Configurator" has been changed to "Web
Part Editor". In the context menu of a Quest Web Part, the menu item has
been changed from "Configure" to "ezEdit". All Quest Web Parts have had name
changes as well. The names have been changed from "Quest List View", "Quest
SI Chart View", etc. to "qListView", "qSIChartView", etc.
- (Req 3694) Microsoft ASP.NET Ajax Extension 1.0 DLL is
automatically installed in the GAC if one is not present. This DLL is
required by some of the web parts. You do not have to download and install
Microsoft ASP.NET Ajax Extension 1.0 manually anymore.
- (Req 3560) The Quest Web Parts for SharePoint
installation adds a few list templates such as the list templates for panel
menu and cascading menu, help link, caption display and resource list.
Therefore, when you need one of these list, you don't have to create the
list manually. You can simply select it from one of the available templates
in your site.
- (Req 3559) The SharePoint solution package that is used
by the installer contains all the files that will be deployed in the
SharePoint 12 hive folder. This is part of an ongoing effort to make the
SharePoint solution package self contained. This means that when you install
our webparts, you will not see the files extracted to the 12 hive folder
anymore. The files will be transmitted from the configuration database to
your server over the wire. This also means the installation takes
much longer that it did in the previous version.
- (Req 3558) The Advanced tab in the web part
editor now contains the Target Audiences field where you can set the
target audiences for the web part. We have also ensured that our web parts
work correctly when the Target Audiences is set.
qDiscussionView
- (Req 3548) The qDiscussionView web part is a new web
part. It enhances the way you view a Discussion Board list. qDiscussionView displays the discussions and the responses in a tree structure making
it easier to navigate between different discussions and responses. The
preview panel also enhances the usability of the Discussion Board list. For
more details on this new web part, please see the help file for the web
part.
qListView
- (CR 66451) Provide a new property to select
which upload button is displayed in the toolbar (single file upload,
multiple file upload or both)
- (CR 66302) A new property called Show Include Sub
Folders CheckBox In Search Panel was added. This property determines
whether the Include Sub Folders checkbox should be displayed in the
search panel. This checkbox is useful when the folder panel is enabled
because in this case the list view will restrict the view and search only in
the currently selected folder. If the Include Sub Folders checkbox in the
filter panel is checked, the subfolders of the current folder will be
included in the search.
- (Req 3551) A new tab called "Context Menu Appearance"
is added to the web part editor. This tab contains properties to
control the visibility of individual context menu items in the list view.
qListForm
- (Req 3694) "Mark Private" button is added to the
toolbar. This button only shows up in the new form, edit form or display
form when the item being displayed or edited was created by the currently
logged in user. The user can mark an item private so that only they can see
the item in the view. One exception to this is the SharePoint administrator
who can always see any item in any list.
- (Req 3549) The SI Column now supports item picker. In
the previous release, the SI Column was always presented in a dropdown
control. This is prohibitively slow when the SI Column is looking up big
data from the external data sources. The item picker helps alleviate this
issue because you can do lookup by using a certain key. This is very similar
with how BDC column is using the item picker.
qChartView
- (Req 3696)A new Chart View web part has
been added that supports 3 dimensional charting. For more details on this
new web part, please see the qChartView help file. The old Chart View web
part is still supported but has become obsolete.
qCalendarView
- (Req 3551) A new tab called "Context Menu Appearance"
is added to the web part editor. This tab contains properties to
control the visibility of individual context menu items in the calendar view.
qSIChartView
- The SI Web Parts have been tested against SAP. You can now display,
create and edit the data in your SAP system via web services.
- (Req 3695) A new SI Chart View web part
has been added that supports 3 dimensional charting. For more details on
this new web part, please see the qSIChartView help file. The old SI Chart
View web part is still supported but has become obsolete.
The following are the bug fixes in this release:
|
CR65222 |
The list view displays the workflow status field as number instead of
the text of the status |
|
CR63898 |
The drill down chart does not work if there are
two charts present in the page. NOTE: this issue was fixed in the new
qChartView. The issue is still present in the old qChartView that was
marked obsolete. Please use the new qChartView to avoid this issue. |
|
CR67232 |
The SI List Form throws an exception when the SetSessionName property is
set and there is an unserializable object coming
from an OUT parameter |
|
CR64553 |
The list form now supports the SortOrder attribute for the lookup and
cross-site lookup field. Previously, you have the ability to sort the
lookup and cross-site lookup field, but you could only sort them in
ascending order. Now, you can specify ascending or descending order for
the sort. |
|
CR65943 |
The people editor in the list form loses its value after a postback from
a lookup field. In order to fix this issue, we add a new property called
"Enable AJAX". There is a known issue in the SharePoint People Editor
control and AJAX. The only way the SharePoint People Editor control can
persists its value is by disabling AJAX (setting the Enable AJAX to
false). |
|
CR67326 |
The List Form does not handle the default value of a DateTime field if
the default value is calculated field. |
|
CR66786 |
The custom save button that does not perform validation in the Quest
List Form will not save the value if the data is invalid. |
|
CR64031 |
The LinkTo column in the SI List View is blank
when exported to Word or Excel. |
|
CR66523 |
The SI Web Parts generate error when executing stored procedure in the
Oracle database that uses DB Link to connect to the Microsoft SQL
Server. |
|
CR66601 |
The SI List Form cannot autofill the boolean field correctly. It always
populates the boolean field with true (Yes). |
|
CR66522 |
The SI List Form generates error when adding new item using SharePoint
List web services |
|
CR66145 |
The Quest List Form does not recognize a field as required when multiple
content type is used |
|
CR66389 |
The custom Save button in the Quest List Form does
not send the email notification |
|
CR66425 |
The Quest Chart View does not show data from the items that are
contained in subfolders |
|
CR66493 |
The display fields property editor generates an error that the list does
not exist when the viewed lists property contains list definition with
IncludeSubsites="true" and the first subsite does not contain the list
with the specified name |
|
CR66159 |
The Quest List View does not display the value of the lookup field as
hyperlink |
|
CR66430 |
The Quest Chart View is missing the following properties: X Axis Item
Font, X Axis Item Color, X Axis Axis Color, X Axis Mark Color, Y Axis
Item Font, Y Axis Item Color, Y Axis Axis Color, Y Axis Mark Color. |
|
CR66044 |
The approve/reject button always points to the approve.aspx in the
_Layouts folder of the top level site. |
|
CR64525 |
Add a property to wire the upload button to the Upload.aspx in the
_layouts folder because Microsoft List Form in the Forms/Upload.aspx
reformats the URL incorrectly. |
|
CR65503 |
The list view displays the Hyperlink or Picture column (in Picture
format) as broken link if the Description part of
the URL is blank |
|
CR65550 |
The cross-site lookup field generates an error if the user cannot access
the looked up list |
|
CR65732 |
The list view requires browse directories permission for the folder
panel while it is not really needed |
|
CR65529 |
The custom action in the list view does not receive the selected item
when the selected item is located in a subfolder |
|
CR65278 |
The Edit button in the list form always uses the ID http parameter
instead of the "ID HTTP Parameter Name" when opening the edit form. |
|
CR65403 |
The list form crashes when it is trying to display a field with name
"Form". |
|
CR58355 |
The list form is unable to autofill a People and Group field or Lookup
field with another People and Group field or Lookup field, respectively. |
|
CR65064 |
Using the ConsumeRowDisplayFormat in the Quest List Form's Display
Fields property causes null reference exception. |
|
CR64919 |
The LinkTo column in the SI List View does not work if it contains only
<%URL Column%>. |
|
CR64746 |
The number for the % field does not show up in the
group header. |
|
CR64751 |
The list view does not display the item if the
user does not have view permission on the list eventhough they have view
permission on the items. |
|
CR64460 |
The Edit icon in the Edit column in the list view
points to the wrong URL. The URL contains ? before the ID parameter
instead of &. |
|
CR63604 |
The Upload button in the Quest List View generates wrong URL when the
list view is placed in a meeting workspace. |
|
CR64492 |
The List Form cannot edit a list item when the user has view only
permission at the list level eventhough the user has edit permission in
the list item level . |
|
CR64456 |
The GoToURL custom action in the SI List Form does not pickup the Input
parameter when the Form Type is set to DisplayEntity. |
|
CR64231 |
The Quest List Form configurator throws null reference exception in a
non English Dutch. |
|
CR64230 |
The Print and Export buttons (under Actions button) are visible by
default in the Quest List View and Quest SI List View. |
|
CR64319 |
The Quest List Form ignores the default value of a boolean (Yes/No)
field. |
|
CR64248 |
The Quest List Form and Quest List View crashes when displaying site
column when the user is not site collection administrator. |
|
CR64088 |
The CalculatedValue field that calls javascript generated an XML parsing
error if the parameter to the javascript function contains &. |
|
CR64086 |
The Actions button in the toolbar is visible eventhough there is nothing
in it. This is happens when you set "Show Filter Button at Top" is set
to true. |
|
CR64054 |
The SI Column does not display the value from the column specified by
the DataTextField when the Form Type is set to DisplayEntity. |
|
CR64013 |
The SI List Form generated an error when trying to
save a blank DateTime field to the Oracle database. |
|
CR64041 |
The SI List Form displays today's date as default value in the required
DateTime field when the FormType is set to NewEntity. |
|
CR63995 |
The SI List Form displays DateTime field with date time format of
DateOnly as date and time value when the FixedValue attribute is set to
<Today/>. |
|
CR63836 |
The list form fills in a non required DateTime
field with minimum DateTime value during autopostback of a lookup field. |
|
CR63639 |
The Custom Action's Perform method only receives the first item that are
selected in the Quest List View. |
|
CR63518 |
The people editor control in the Quest List Form does not save its value
when it's disabled. |
|
CR63512 |
The cross site lookup field is not saved by the custom save button. This
happens if the custom validation logic in the custom save button cancel
the save event and the user fix the data and click the custom save
button again. |
|
CR63485 |
The Operator dropdown in the filter panel for FixedOperator field is no
longer disabled after the values in the filter panel is restored upon
page revisit. |
|
CR63459 |
The SI List View does not replace the field replacement expression (<%FieldName%>)
in the LinkTo attribute when the List Searcher Mode property is set to
true. |
|
CR63156 |
The Calendar View crashes when the user resizing an item from a non
Calendar list, such as a Tasks list. |
|
CR63354 |
Some windows that contain the Next button might get covered by another
window during the installation process giving the impression that
the installation process hangs. |
|
CR63455 |
The list view does not handle the CalculatedValue field property when
displaing dissimilar list. |
|
CR63405 |
The value of the CalculatedFormat field is
not saved when the data is saved using a custom toolbar. |
Version 4.3
The following are the new features in this release:
All Web Parts
- (Req 3280)
Quest Web Parts for SharePoint is now deployed as a
SharePoint Solution. The benefit of the solution package deployment is the
ability to deploy Quest Web Parts for SharePoint in selected Web
Applications using the SharePoint Central Administration site. It also
provides the flexibility to turn on/off Quest Web Parts for SharePoint as a
site feature. When a new site or site collection is created, the Admin or
Site Designer can activate the Quest Web Parts for SharePoint Feature to
enable the web parts for newly added site collections.
- (Req 3265) The
ability to use a dynamic variable in the CAML Filter. The value of the filter
can now be retrieved from the Session variable and the HTTP parameter.
Previously, you could only hard code the value of the filter.
- (Req 3201) A new
custom action type to start the SharePoint workflow.
- (Req 2994) The ability to recognize the OEM license.
When an OEM license is detected, the Configure and Help menu items under the Web
Part Menu will not be shown.
Quest List Form
- (Req 3208) Quest List Form now supports the SharePoint BDC column. You
can also search for the BDC column in the search panel of Quest List View, Quest
Calendar View and Quest Chart View.
- (Req 3208) The Quest List Form also supports the SI Column.
Similar to the BDC column, the SI Column enables you to create a lookup field to the
data in external system. The SI Column uses the same mechanism as the SI Web
Parts to connect to the external system, the DAO Provider.
- (Req 3204) The
Quest List Form is now able to use the People Editor control for the People
and Group field instead of the Quest List Form people selector. In order to
do so, the user must check the UsePeopleEditor attribute in the
Field setting in the Display Fields property.
- (Req 3204) The
ability to use current user as the default value of the People and Group
field. In order to do this, you should set the
UseCurrentUserAsDefaultValue attribute in the Field setting in the
Display Fields property to true.
- (CR 60878) The ability to use a different name for the
ID HTTP Parameter by defining the name in the ID HTTP Parameter Name
property. This feature is added to overcome a SharePoint bug where the page
in the document library cannot take an ID that is bigger than the number of
documents in the document library. To overcome this bug, place the list form on a page in a
document library, rename the ID HTTP Parameter to something other then ID, such as
LID. This new property is also added to the Quest List View and Quest
Calendar View so that they will use the same name expected by the list form
when they open the display form or edit form of an item.
- (CR 55892) The ability to auto-fill a field by using the
current user information. You can use one of the following expressions in
the FixedValue attribute: <CurrentUserName/>, <CurrentLoginName/>,
<CurrentUserID/>, <CurrentUserEmail/>.
- (CR 62002) The ability to control the width of the
controls in the list form by using the Width attribute of the Field
element in the Display Fields property.
Quest List View
- (Req 3243) You can
colorize the rows in the List View based on the value in a certain column.
For example, all appointments in meeting room A are red, all appointment in
meeting room B are blue, etc. You accomplish this by defining the
Appearance Field Name and Color Appearance properties. This
feature is also added to the SI List View.
- (Req 3217) The
ability to expand the filter panel when the list view is loaded for the
first time. Previously, in order to do this, you had to turn on the list
searcher mode. However, in list searcher mode, you had to perform a search first
before the data is shown. With the new property, Expand Filter
Panel On Load, you can expand the filter panel by default without
using the list searcher mode. This feature is also added to the Quest
Calendar View, Quest Chart View, SI Chart View and SI List View.
- (Req 3217) A new
property called Panel Button Location to define the location of the
command buttons in the filter panel. The options are top, bottom or both.
Previously the buttons were always shown at the top and bottom which can
clutter
the filter panel especially when you only have one or two fields in the
filter panel. The same property also exists in the Quest Calendar View and
Quest Chart View, SI Chart View and SI List View.
- (Req 3256) The
ability to apply the CAML Filter for Folders on the first level folder only.
This property is called Apply CAML Filter on First Level Folder Only.
- (Req 3210) The
ability to export the grid in the list view to PDF, Excel or Word format by
clicking the Actions > Export button in the toolbar. You must set
the Show Export Button to true for this button to appear. The same
feature is added to the SI List View.
- (Req 3248) The
ability to print the grid in the list view by clicking the Actions >
Print button in the toolbar. You must set the Show Print Button
to true for this button to appear. The same feature is added to the SI List
View.
- (Req 3207) The
ability to open the context menu by clicking the drop down arrow in the
context menu column. You can display the context menu column by setting the
Show Context Menu Method property to ShowContextMenuColumn
or RightClickAndShowContextMenuColumn.
- (CR 61444) The ability to determine the maximum number
of rows retrieved by the list view by using the Maximum Row Count
property. This can be useful in several scenarios such as when you want to display the
last 5 modified documents in the "my document" library.
- (CR 51361) The ability to expand all the parent records
in the hierarchical list view when the list view is loaded by setting the
Expand Child View On Load to true.
Quest Calendar View
- (Req 3194) You can
colorize the items in the Calendar View based on the value in a certain
column. For example, all appointments in meeting room A are red, all
appointment in meeting room B are blue, etc. You accomplish this by defining
the Appearance Field Name and Color Appearance properties.
Quest Chart View
- (Req 3195) The
ability to create a drill down chart view. There are two new properties
related to this feature: Drill Down Chart URL and Show Return
To Master Chart Button. Please check out the CBT on how to create a
drill down chart. This feature is also added to the SI Chart View.
- (Req 3196) The
ability to generate the data series in the chart dynamically. For example,
if you want to create the data series for different countries to display the
yearly sales amount. If the name of the countries in your data is fixed, you
can hard code the data series in the Configuration property of the
Chart View. However, if the number of countries in your data is
unpredictable, you can generate the data series dynamically by using the
FilterFieldName attribute in the Items element in the
Configuration property. This feature is also added to the SI Chart
View.
- (Req 3199) The
ability to display a background image in the plot area of the chart view. This
feature has also been added to the SI Chart View.
All SI Web Parts
- (Req 2750) The SI Web Parts now include the
Oracle DAO Provider. There are 3 methods to write or retrieve data from your
Oracle database: stored procedures, table direct or writing your own PL/SQL in
the Catalog.
- (CR 61902)
A new property called Display Messages from DAO Provider
has been added. If set to true, the SI Web Parts will display all messages that
are returned from the external system. If set to false, the messages will be
suppressed.
SI List Form
- (Req 3193) The
ability to display the custom action error message in a popup dialog box, in
the list form itself or in both. You can do this by setting the Custom
Action Error Display property. In addition, the error message
will not replace the fields in the form as the previous version of the SI List Form did.
- (CR 63997 - Hotfix) The ability to display an empty
selection (an item with empty value) in the dropdown for SI Column. You can
do this by setting the ShowEmptySelection and
EmptySelectionItemName attributes in the Lookup element in the Display
Fields property.
SI List View
- (Req 3260) The
ability to pass the filter criteria to the DAO Provider. Previously, the
filter criteria entered in the filter panel was applied to the data that was
returned by the external system. This can be very inefficient especially when
dealing with a large set of data. By passing the search criteria to the DAO
Provider, the filtering happens in the external system and results in a much
smaller data set being returned. In order to pass the filter criteria to the DAO Provider,
you set the Filter Criteria Usage property to PassToDAOProvider
or PassToDAOProviderAndFilterData. This feature is also added
to the SI Chart View.
The following bugs were fixed in this release:
|
CR62983 |
The date and time in the Calendar view is always shown with MM/DD/YYYY
format regardless of the Locale in the Regional Settings. |
|
CR62679 |
"Click here to test" link in the Hyperlink or Picture column in the
Quest List Form does not work. |
|
CR62848 |
The list view generates a null reference exception when the user filters
the data using multi choice field and does not select any value in the
multi choice field |
|
CR62132 |
The Rich Text Editor strips off the URL of the
hyperlink
if the
hyperlink points to a page within the root of the site |
|
CR62892 |
The Calendar
View crashes when displaying an item with start date after the end date |
|
Req3205 |
Set dropdown
height in the lookup and cross site lookup field in the List Form to
avoid the dropdown from getting so long that the user has to scroll down
in the browser to get to the bottom of the list |
|
CR58491 |
The filter
for the list view is not persistent when the user returns to the page |
|
CR59235 |
When the cell
value is empty, the bottom border of the cell is not rendered |
|
CR58333 |
The list form does not detect the required multi choice field as
required |
|
CR60390 |
The list form does not support custom field |
|
CR60695 |
Some toolbar buttons (such as Link Manager button) in
the rich text editor generates error when clicked |
|
CR 54218 |
AJAX issue in IE 6. This issue results in several
things such as the list view freezes when the user clicks on the smart
link column, etc. In order to overcome this, we check for the browser
version and turn off AJAX automatically when IE 6 is detected. However,
you can also turn off AJAX explicitly in the list view by setting Enable
Ajax property to false |
|
CR 58491 |
The filter, page index and sort criteria in the
list view do not persist when the user returns to the page |
|
CR 58970 |
The list form does not show the previous versions
of Multiple Lines of Text with "Append Changes to Existing Text". |
|
CR 59932 |
The Save custom action does not save the metadata in
the upload form |
|
CR 59933 |
The list form generates error if the minor
versioning in the document library is turned on |
|
CR 60374 |
The chart view displays null reference exception when linked to the list
view |
|
CR 61620 |
The custom display of the list view is not
refreshed when the user clicks different page in the pager |
|
CR 55486 |
The list view performs poorly when displaying People and Group
field |
|
CR 61579 |
The <%Folder%> replacement expression does not work in the custom
display in the list view when the Display Fields property is empty |
|
CR 61784 |
List Form generates error when using ConsumeSession DisplayFormat
attribute in the Display Fields property |
|
CR 62080 |
The People and Group field control, the lookup field control (with
multiple values) and cross site lookup field control (with single
value) do not persist their values when the control is disabled |
|
CR 62084 |
The date time field contains its old value when
inspected in the custom action eventhough the date time field control is
blank |
|
CR 62140 |
The CAML filter might not work when applied on indexed columns |
|
CR 61364 |
The tooltip does not pop up for some field type in
the list form. This is especially true for read only field |
|
CR 61948 |
The selection list box for the People and Group field and multi value
lookup field is too small that it only displays 4
rows. It is very hard to see all the selections especially when it
contains many rows of information. |
|
CR 57775 |
Memory leak in the webparts because SPSite and
SPWeb objects are not properly disposed |
|
CR 58843 |
The calendar view generated an error when the time zone of the site is
set to a time zone that does not recognize daylight saving time |
|
CR 60632 |
The calendar view shows the appointment for the daylight saving time
period in the wrong spot |
|
CR 51604 |
The list form cannot show the ID field of the list item |
|
CR 56960 |
The custom action generates an error when it takes parameter from row
from another web part |
|
CR 58350 |
Error occurs when saving read only date field and the site regional
setting is set to Dutch |
|
CR 60705 |
The choice field does not display blank selection when the default value
of the field is set to blank |
|
CR 60844 |
Hierarchical list view with 2 parent lists and 2 child lists shows 2
child views for every parent record |
|
CR 60882 |
New button for document library doesn't work correctly for some content
type such as Basic Page or Link to a New Document |
Version 4.2
The following are the new features in the Web Parts for
SharePoint 2007.
- The Quest Calendar View Web Part has been added for SharePoint 2007.
The Quest Calendar View aggregates data from one or more
SharePoint lists and displays it in calendar form. This feature requires you
to install Microsoft ASP.NET AJAX Extension 1.0 and an addition to your web.config file, so
please review the upgrade instructions below:
Summary of Upgrade Procedure.
- The Quest Page Redirector Web Part has been added for SharePoint 2007.
The Quest Page Redirector sends users to a designated URL. A
common example would be redirecting users to their home sites.
- The Chart View and SI Chart View now have the capability to display
chart item color based on range in Y axis value. You can also define the
color of the chart image's border as well as the color of the plot area's
border.
- The SI Chart View now has the ability for users to define
search criteria using the Filter panel. The Web Part author can define the
fields that will be shown in this panel using the SearchedFields property.
- Quest Development Studio for SharePoint has been tested on 32 bit Windows Server 2008.
The following bugs were fixed in this
release:
|
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 Quest 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 resets 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. |
Version 4.1
SharePoint 2007 Web Parts
The following are the new features in the Web Parts for
SharePoint 2007.
- The SI
Web Parts include these additional DAO Providers:
-
ADO.NET connections to SQL Server 2005 are now supported.
-
Direct connections to Domino server using XML over HTTP protocol are now
supported
- The Web
Services DAO Provider supports complex type and XML parameters when calling
the web method.
- For the
List form and SI List Form, you can now configure the form to be displayed
in a tab layout or a custom layout. The custom layout capability enables you
to code your own layout manager to control the location of each control and
to create additional controls on the form.
- The Help
URL property, found in the Advanced tab of the Configurator, can now be
modified to point to another URL such as the URL for a custom help file for
the user’s application.
-
Documents can now be forwarded in an email from the List View and List Form
- For the
List View and SI List View, a new property to display selection column has
been added. Currently, in order to select a row, you must click the row. To
select multiple rows, you click another row while holding down the Ctrl or
Shift keys. Now, there is another option for selecting rows. You can add a
checkbox to the List View or SI List View that when checked by the user,
indicates the row is selected. This checkbox is added to the List View or SI
List View using the new property called "Selection Column Type" in the
Configurator.
- In the
Chart View and SI Chart View, there is a new property that gives the user
the choice to generate a chart image using the session or a local folder.
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="<%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
-
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.
-
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.
-
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
-
The SI Web Parts contain 4 different Web Parts: SI
List View, SI List Form, SI Selector and SI Chart View.
-
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.
-
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.
-
The SI List View, SI Selector and SI Chart View
enable the user to display data from their external systems in
SharePoint.
-
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:
-
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.
-
The ability to apply CAML Filter on Folders using
CAML Filter for Folders property.
-
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.
-
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.
-
The List View displays the appropriate icon for the
Recurrence field in the Calendar or events list.
-
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.
-
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.
-
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.
-
The ability to define different styles for odd numbered
rows and even numbered rows using the Item Style and
Alternating Item Style properties.
-
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)
-
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).
-
You don't have to specify DynamicAssemblyPath
attribute in the web.config file anymore when debugging a custom action
class.
-
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.
-
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.
-
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.
-
The Grid Lines property was removed because its
functionality was superseded by the settings in the skins for the List View.
-
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:
-
CR43616 - The List View did not display any data when consuming
a filter with a DateTime field from another Web Part.
-
CR28557 - The List View crashed when trying to display data
from an empty list.
-
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.
-
CR47438 - The List View did
not send the deleted items to the recycle bin.
-
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.
-
CR47176 - The List View could not create a new
InfoPath document by using the "New" button in the toolbar.
-
CR49047, CR49046 - The List View crashed when the Page Size was set to a
negative number or zero.
-
CR48980 - The New button in the List View could not handle InfoPath
Form Service.
-
CR46905 - The List View did not refresh its content after the
"Discard Checkout" operation was performed on a document.
-
CR25251, CR43415 - The buttons at the top of the search panel and replace
panel did not work.
-
CR44238 - The Show User Groups and Hide User Groups
properties in the List View did not work.
-
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.
-
CR43413 - The Key Field Name selection in the Dependent
Lists property editor got reset when editing the list.
-
CR46619 - The list settings in the Viewed Lists property editor
disappeared after adding a child list or a dependent list.
-
CR43411 - The Display Fields property editor mixed up the order
number of the fields when the user tried to reorder the fields.
-
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.
-
CR43582 - The List View always displayed the values of a currency
field with 2 decimal places even though the field setting specified it
differently.
-
CR42316 - The CalculatedValue field in parent record in a hierarchical List View will display System.Data.DataRowView when
the parent record is expanded.
-
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:
-
The List Form displays the version of the displayed or
edited document properties at the bottom of the form.
-
The following buttons are added to the toolbar: Manage
Copies, Version History, Workflows, Alert Me.
-
The List Form supports the IWebPartRow interface. The List Form still supports the IRowProvider
interface. However, the IRowProvider interface implementation is marked
obsolete.
-
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.
-
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:
-
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.
-
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.
-
CR41671 - The rich text editor didn't adjust its height based
on the number of lines setting in the field.
-
CR47438 - The List Form did
not send the deleted items to the recycle bin.
-
CR46891 - The List Form loaded very slowly when
displaying an item from a very big list.
-
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.
-
CR49477 - The hyperlink for the file name when the Form Type
was set to DisplayDocument did not work correctly for InfoPath Form
Service.
-
CR49057 - The List Form crashed when trying to display a folder
metadata and the Form Type was set to DisplayDocument.
-
CR48457 - There were a few occasions when the Multiple File Upload
did not prompt the user for metadata.
-
CR46542 - The spell checker button in the rich text editor was
shown even though the rich text editor did not have spell checking
capability.
-
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.
-
CR45035 - Users could still compose an email message even though the
Allow Custom Message property was set to false.
-
CR44653 - The List Form did not validate required Date Time or
People and Group fields.
- 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:
-
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.
-
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:
-
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.
-
CR41830 - The Chart View crashed when the value of the MinValue
attribute is greater than the value of the MaxValue attribute.
-
CR49575, CR43616 - The Chart View did not display any
data when consuming a filter with a DateTime field from another Web Part.
-
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.
-
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.
-
CR49453 - The chart image format was always BMP even though the
Chart Image Format property was set to some other image types.
-
CR49817 - The Chart View crashed when connected to Microsoft List
View using a DateTime field.
-
CR49566 - The Chart View showed Date Time value in the X Axis with
wrong format.
-
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.
-
CR48109 - There were a few occasions when the Chart View generated
the following error: "A generic error occured in GDI+".
-
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:
-
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:
-
CR42715 - The Selector crashed when the Selector Width, DropDown
Width or DropDown Height properties were set to a negative value.
-
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:
-
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:
-
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:
-
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:
-
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
Contacting Quest Software:
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:
- Quickly find thousands of solutions (Knowledgebase articles/documents).
- Download patches and upgrades.
- Seek help from a Support engineer.
- Log and update your case, and check its status.
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
© 2009 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:
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, Fusion
Charts.
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