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.
| Release Notes v5.0 SP4 / 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 an SPDoc process, the metadata from a document library is not being synchronized properly with a document if the document is in a folder within the documentation library. (This issue does not occur if the document is in the document library root.)
In the WFStatus page for a running or completed process, only assigned and overdue tasks appear. Completed tasks do not appear.
The Update Meta Data AgileShape gets suspended when the mapped custom attribute does not have a value.
In the Task List Web Part, setting the Type of List property to My Team and Sub does not show any tasks if there is no team or sub-team present. Tasks assigned to the authenticated user should appear.
When AgilePoint SharePoint Integration is running in IIS mode using Claims Based Authentication, Approve, Publish, and Submit AgileShapes fail because the prefix "0#.w|" appended to the user name passed during Claims Based Authentication is not properly handled.
If setting OpenTasksInNewWindow in the AgilePoint Configuration list is set to False, AgileForms tasks still open in a new window.
The Retrieve List Item AgilePart fails if the list item is inside a folder.
If you change the name of a SharePoint list, and then run a process with the Copy List Item or Move List Item AgilePart, the process is suspended.
If a folder name contains spaces, the Copy List Item, Move List Item, and Update Meta Data AgileParts suspend the process.
Even if setting OpenTasksInNewWindow in the AgilePoint Configuration list is set to false, web forms tasks open in a new window.
If Open task by clicking the task link is set to true in the AgilePoint Task List Web Part, tasks always open in a new window, even if the setting OpenTasksInNewWindow in the AgilePoint Configuration list to false.
If a task is assigned to a dynamic group, and status is New, the option Reassign Selected Tasks form AgilePoint Task List Web Part Global Action Menu should be disabled.
The Update Meta Data AgileShape does not work when the default view is not AllItems.aspx.
The CAML Query AgileShape fails to retrieve the mapped column values if one of the column values is absent.
If a document library is renamed, the Copy Files AgileShape fails when copying files from one folder to another within the document library.
The Publish Content AgileShape fails if there are lookup columns in a document library.
The Publish Content and Approve Reject Content AgileShapes fail if there are more than 100 items in a folder.
The wrong value of the SharePoint numeric field is displayed in Enterprise Manager if the decimal separator is not set to use a period (.) in the regional settings on the AgilePoint Server machine.
When an SPDoc process is initiated, checkin comments for the process model disappear.
For a process is started before AgilePoint BPMS v5.0 SP3 was applied, but it completed after v5.0 SP3 was applied, the status link in SharePoint does not change from InProgress to Completed, even though the process is completed in AgilePoint. The following exception may appear in the SharePoint log:
Engine RunWorkflow: System.Workflow.Activities.EventDeliveryFailedException: Event "OnTaskChanged" on interface type "Microsoft.SharePoint.Workflow.ITaskService" for instance id "26c1eb3a-b2ef-4e14-9d0a-71335cfe2dc4" cannot be delivered. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array. at System.Workflow.ComponentModel.Serialization.ActivitySurrogate. ActivitySerializedRef.System.Runtime.Serialization.IDeserializationCallback.OnDeserialization(Object sender) at System.Runtime.Serialization.DeserializationEventHandler.Invoke(Object sender) at System.Runtime.Serialization.ObjectManager.RaiseDeserializationEvent() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fC...
When an exception occurs, the UpdateInfoPath AgileShape is not suspended.
If an UpdateInfoPath AgileShape is suspended, the InfoPath schema XML is still updated.
The Use UTF 8 Encoding option always returns false. This leads to server errors in environments that require UTF 8 encoding, such as Japanese.
Occasionally in the SharePoint Task List Web Part, when a user clicks Reassign in the Task column list, the task is not reassigned.
If the Delete Files AgileShape does not find a specified file, the process is suspended. The default behavior has been fixed so that when a specified file is not found, the Delete Files AgileShape is marked as complete, and the process moves forward.
When an AgileShape in a SharePoint process immediately follows the Start shape, and uses a custom attribute corresponding to a SharePoint column value, the AgilePoint fails to retrieve the value of the custom attribute.
On the SharePoint Task List Web Part, in the Task column, when the name of a task contains more than one consecutive space, the sort and filter functionalities do not work correctly.
On the SharePoint Task List Web Part, applying a filter does not redirect the Web Part to the first page to display the results.
If the Task List Web Part is configured to bring down a lot of tasks, such as for >2000 tasks, occasionally during the loading of the Task List Web Part, an XslException occurs. The reason for this exception is the XSLT Timeout which ultimately results in the entire SharePoint page not loading. Additional error handling has been added to avoid the entire SharePoint page crashing.
When Priority is set using custom attributes, the SharePoint Task List Web Part takes more time to load.
A process with a CAML Query AgilePart designed in AgilePoint BPMS v5.0 SP1 fails to execute at runtime when the process is published from a v5.0 SP3 environment.
In the AgilePoint Configuration List, the password is not getting encrypted if the Configuration List name is localized.
The Task List Web Part displays more results than the value of the "Max. Tasks to Retrieve" property.
When a Task is assigned to a group, tasks are displayed in red, even if the task is not overdue.
In the Task List Web Part, when a user sets Group By and Sort By to "Tasks" using Edit Web Part, it displays "None" in the Group By and Sort By in the Task List Web Part.
For custom data source, if a column is set to show as a link, the HTML code for the link is shown in the filter drop-down instead of the column value.
The Create ListItem AgileShape fails if Allow Multiple Selection is set to True for a Person or Group field in a SharePoint List.
For SharePoint 2010, the New Site AgileShape fails to update the title of the site when the UseUniquePermissions property is set to True.
In the Task List Web Part, the sort functionality is not working correctly for the custom DateTime and Number fields created using Custom Data Source.
For column data to render as a link the data type must be String or blank. If Render as Link is selected and any other data type is selected, the Render as Link option is ignored. This rule has been enforced with the implementation of this fix.
In the Task List Web Part, after applying the FIX 06.0105, the Custom Data Source columns' values are not displayed.
On the Task List Web Part, in the Process Viewer, clicking an activity does not show the activity information. This happens only at the non-root site collection level. For example, http://[machine name]:[port]/sites/[site name]
In this example, there is site collection at the /sites/[site name] level, and there is no root site collection, such as, http://[server name]:[port]/
For a Multiple Lines of Text SharePoint column, the Create List Item AgileShape displays the literal HTML markup, rather than rendering the content as formatted HTML.
Display on Quick Launch option for Create SharePoint List shape does not display on the quick launch, even if it is selected.
Create ListItem AgileShape fails when the SharePoint list has a People/Group column that is set to allow multiple selection.
On the SharePoint ListForm AgileShape, a field can be marked as both Hidden and Read-Only, even though these should be mutually exclusive options.
If there is a hyphen (-) in a SharePoint list name, the Copy ListItem AgileShape recognizes the list name as invalid.
Using the File Drop Event Service, if more than 300 files are dropped at once, the event is not recognized immediately.
When an InfoPath Form is submitted, AgilePoint does not wait for the Form Library to be updated before updating the AgilePoint process schema.
When configuring a SharePoint List DataSource, if any field is added, the list URL becomes visible under the DataSources parameter. However the OK button is enabled even if List URL has not yet been configured.
When the Create ListItem encodes an ampersand (&) as an XML special character (&) twice, so "&" displays at runtime.
CAML Query fails when the Where clause value contains operator symbols that are also XML special characters -- for example, "&" and "<."
ViewFormData.aspx returns a JavaScript error in case of SharePoint 2010 environment.
SharePoint list fields that are set up as lookup columns are not synchronized for SPDoc or SPList based processes.
The Update MetaData AgileShape fails to set the value of a column to null for DateTime columns, Calculated columns, Text columns, Person/Group columns,or Look up columns and HyperlinkPicture column with default values.
The priority of a task cannot be changed in the SharePoint Task List Web Part in non-English environments.
The ListForm AgileShape does not have a validation for the SubmitStep property.
In the Delete List AgileShape cannot be configured to work with a Microsoft Office365 URL.
If a participant tries to open a completed task, an incorrect error message appears.