Fixes for SharePoint Integration

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.

06.0131.01
The SharePoint Task List Web Part fails to sort by assigned date by default.
06.0132.01
In the Workflow Settings of a SharePoint List, if you choose a content type other than All (such as Schedule or Item), hidden and read-only fields do not display correctly in the SharePoint ListForm.
06.0133.01
The Retrieve List Item AgileShape cannot retrieve metadata for SharePoint lists or document libraries where validation settings are applied.
06.0134.01
Update Meta Data AgileShape fails to update a column of type Person/Group with a value from another column of type Person/Group.
06.0134.02
When using the SharePoint CSOM AgileConnector, the Create List Item AgileShape fails to create a list item if the target SharePoint list has been renamed.
06.0134.03
When using the SharePoint CSOM AgileConnector, when the Create List Item AgileShape creates a SharePoint list item, it sets the URL of the list item incorrectly in the SubDocUrl process attribute.
06.0134.04
For the SharePoint CSOM AgileConnector, if some input parameters are incorrect, or if the wrong credentials are configured in the AgileConnector configuration, SharePoint AgileShapes fail to execute, and the following exception message is logged: "object reference not set to an instance of an object."
06.0134.05
For the SharePoint AgileConnectors, performance has been improved for synchronizing metadata when a process moves from one AgileShape to the next.
06.0212.01
If an AgileForms task is opened from the SharePoint Task List Web Part, and the option "Open task from task link" is selected, the URL includes the extra characters "/FormRender.aspx," which is incorrect.
06.0213.01 (Enhancement)
For Ascentn.SharePoint.AgileConnector, if a SharePoint list has more than 8 lookup or person/group columns, metadata synchronization fails.
06.0213.02
While using Ascentn.SharePoint.AgileConnector with SharePoint 2013, the InfoPath SubProcess AgilePart fails to initiate a subprocess.
06.0213.03
In the SPCSOM AgileConnector, when a person/group column is set to allow multiple values, the corresponding process attribute values in AgilePoint Server are given the prefix Microsoft.SharePoint.Client.FieldUserValue[]
06.0213.04
The Copy Files AgilePart always creates a blank document in the destination library on Office 365.
06.0214.01
The AgilePoint workflow launcher fails to initiate a workflow for a SharePoint list or document library that is created through Visual Studio using a custom SharePoint list template or document library template.
06.0216.01
For the Copy Files AgilePart, if an incorrect source URL is supplied, no exception occurs, and the process moves forward instead of getting suspended.
06.0218.01
When using the SPCSOM AgileConnector, the Approve/Reject Content AgileShape fails if a SharePoint document library contains duplicate file names.
06.0218.02
In the SPCSOM AgileConnector, in the Delete ListItem AgileShape, if the SharePoint list is renamed, the AgileShape fails to delete the list item.
06.0218.03
The Create ListItem AgileShape fails to create a list item if list has a column of type Person or Group.