© 2011 AgilePoint, Inc. All rights reserved.
| Release Notes v5.0 SP2 / Fixes |
The following issues have been fixed in this release for AgilePoint Integration for SharePoint. All fixes in this release are for SharePoint Integration v2 only, unless otherwise specified.
Overdue tasks are not showing up in the correct color on the day they became overdue.
If a SharePoint form library has been enabled to use InfoPath client-based forms, and the process has been associated with the library to be initiated when a new form is created, an error message says that the root element is missing. However, manual initiation of the process works on the same library.
Link To Item is not working on the WFStatus page in SharePoint.
In SharePoint 2010, the Initiate a Process option for the Process Template Web Part is always opening a form in the InfoPath client, even if the form library is set to open form in the browser.
The Open Task option does not work in the task list if the SharePoint file name contains an apostrophe (').
Support is required for Yes and No keywords along with 1 and 0 for Boolean fields.
With this fix, SharePoint stores the values as 1 and 0, and we allow users to type Yes or No if they want.
If a SharePoint document library is set up to automatically start an AgilePoint process when a document is uploaded, it is possible to receive an error similar to the following: "The file xxx has been modified by SHAREPOINT\system on xxx." This error most commonly happens in slower SharePoint environments. It is caused by a race condition where the process attempts to start before the document upload is complete.
This is a SharePoint issue, but an AgilePoint fix has been created that delays the start of the AgilePoint workflow until the metadata has been updated.
The original behavior (do not wait for the metadata to start the process) is still available via configuration setting. For more information, see (v2 Only) AgilePoint Configuration List.
If the SharePoint Document library has mandatory metadata columns (custom or site columns) then the workflow initiation fails while uploading a document.
For AgilePoint Integration with SharePoint 2010, occasionally administrator email notifications are sent indicating that AgilePoint has prevented a duplicate process instance from being created in a document library. These emails are related to a bug in SharePoint 2010 related to event handling in document libraries.
With this fix, AgilePoint handles this SharePoint bug by performing a pre-check to ensure that no process instance exists for a document before trying to create a document-library-based process instance.
In SharePoint 2010, in the Process Template Web Part, the Initiate a Process action item was missing.
ListForm does not capture the exact value of the LookUp column or the People column.
If an AgilePoint role includes a group as a member, tasks created by the Dynamic Group shape are not appearing in the Task List.
If you are using custom data source functionality for SPList and SPDoc processes, when the internal names and display names are different for SharePoint fields, the custom columns are not displaying in the Task List.
The Delete File Shape in the SharePoint stencil does not throw an exception when the file does not exist.
The Copy ListItem AgileShape throws an exception if the SharePoint fields contains any special characters for XML.
The following error message is appearing in the Event Viewer, even though this feature is optional: "OpentaskInNewPage cannot be found".
The Copy ListItem AgilePart fails if the list has PersonOrGroup or LookUp field types.
Exception handling is not working for the Excel Write Shape.
The custom data source functionality fails to retrieve data if SharePoint Integration is not enabled on the root site collection.
Custom data sources with display names that used spaces were not working.
The SharePoint Looklist value is not being returned to AgilePoint when the value is set to none.
In SharePoint 2010, the Update Meta Data AgilePart is not updating the metadata for a document set.
In the Update Meta Data AgilePart, if you try to pass a null value to a People and Group field, it is not updated.
If a SharePoint List Form shows a Required Field validation message, all the hidden and read-only fields appear.
If a SharePoint AgileShape throws an exception, and the process instance is suspended, it is not possible to roll back this suspended process to a previous activity in order to re-execute the SharePoint AgileShape.
In the Download File AgilePart, if a document library URL was not found, no exception is being thrown by SharePoint.
The SharePoint ListForm AgileShape does not capture the exact value of the LookUp and People columns.
When a process template is set up to kick off a process instance when a document is checked in, in some cases the process instance is not started.
The Take Assignment & Open Task link does not work with ASP.NET external application tasks in the AgilePoint task list.
Workflows with the Download Files AgilePart were suspended while downloading files with empty or NULL strings.
The CAML Query AgilePart does not work for AgileForms. When output mapping is clicked, the AgilePart throws a "Root element missing" exception.
If a target library has required metadata fields, the CopyFile, MoveFile, CopyListItem, and MoveListItem AgileShapes fail to copy or move the file, but an exception is not thrown.
The CAML Query shape throws an exception when the SharePoint column name has a colon (:) character.
Append-only, multi-line text box values are duplicated by the Update Meta Data AgilePart.
Unable to use SP Common Dialog Shape when a SP Column name has an colon (:) character.
© 2011 AgilePoint, Inc. All rights reserved.