AgilePoint BPMS v5.0 R2 for .NET 3.5, .NET 4.0, and Genesis Edition
AgilePoint BPMS v5.0 SP3 for Universal Edition and Azure
© 2014 AgilePoint, Inc. All rights reserved.
| 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.
In SharePoint 2007, a Completed workflow remains for a few minutes in the InProgress state, even after the workflow has changed to the Completed state in WFStatus and EnterpriseManager.
This issue occurs due to a known issue from Microsoft in SharePoint 2007. This fix addresses the issue with AgilePoint and SharePoint 2007. This is not an issue for SharePoint 2010.
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 an InfoPath form library. These emails are related to a bug in SharePoint 2010 related to event handling InfoPath form 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 InfoPath form library based process instance.
This fix is an additional refinement of FIX 06.0009, released in AgilePoint BPMS v5.0 SP2, so that this functionality can better handle SharePoint environments under high load.
In a ListForm AgileWork used as a SubmitStep, some fields that are set to display are not displaying.
This fix addresses the following issues:
The Task List Web Part may still show some issues in some environments.
This fix includes the following enhancements:
This fix addresses the following issues:
In a custom data source, if the display name has spaces, then the data source lookup does not work.
In the SP Common Dialog AgileWork, if a SharePoint column is of type Boolean, and the value is True, the check box is not checked at runtime.
In the SP Common Dialog AgileWork, if the Date Picker control is the last field in the form, the pop-up does not appear in the proper position.
In a custom data source, if one or more field is configured improperly, then no fields display, even the fields that are configured properly.
OpenTasksInNewWindow is not working for SharePoint ListForms.
OpenTasksInNewWindow does not work for InfoPath forms when the task is accessed from the Process Viewer.
SP Common Dialog AgileWork does not work for InfoPath Process Templates.
When configuring the custom attribute data source to display the Modified Date column, it shows the time in UTC format, thus offsetting the value from the expected value.
If a document is checked out, the Update Metadata AgilePart fails to update the document, but no exception occurs.
On the Task List Web Part on the Workflow Status page, if no task is selected, the Global Actions does not display the "no action found" image.
If an InfoPath task is in New status, and a user attempts to open it before taking assignment, a message occurs incorrectly stating that the task has been completed.
In Japanese environments, in the SharePoint Connector Configuration dialog box, the OK and Cancel buttons do not display.
When adding a SharePoint calculated field using custom data sources to the Task List Web Part, instead of showing the value of the SharePoint calculated field, it is showing the output type of the field in the Task List Web Part.
In the SharePoint Task List Web Part, if the text fields are marked Read Only, and a postback happens on the SharePoint page, the field values are cleared.
The calculated column value is modified after the initial submit of a SharePoint ListForm.
The text for the Test Query tab is missing in the CAML Query AgilePart.
The CopyFiles AgilePart logs an error even if the target folder exists.
When two different processes with different schemas have the same custom attribute configured for the custom data source, an error occurs.
In the Content Listener AgileConnector, if a SharePoint list is created in one of the sub-sites and it is associated with a process, the process does not appear in the drop-down in the configuration window.
Even if a Move Files AgileShape does not find a document in the source library, it still creates an empty file in the target library.
On the SharePoint Edit Form page, if you have a custom Web Part along with the AgilePoit List Form Web Part, and the custom Web Part makes a postback, the fields that are marked as Read Only by the ListForm Web Part are getting cleared after the postback.