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.
The following issues have been fixed in this release for AgilePoint Envision.
If the size of process model file in Envision is greater than 15 MB, and the Visio file is saved repeatedly without closing Envision session, Envision memory usage increases and eventually throws an "Out Of Memory" exception.
This fix addresses the following issues related to the WCF AgilePart:
Occasionally in high-volume, high-speed environments, when many process instances are using the Update Custom Attribute AgilePart at once, an exception occurs, and the process stops.
This fix addresses the following issues:
The user-defined data property configured at design time in all the AgileWorks is not saved as client data under ManualWorkItem.
In Update Custom Attribute AgilePart, if an Xpath contains an @ character, the code validation fails.
The Data Type drop-down is not cleared if a Complex type node is selected in the Xpath Picker.
The PDF Converter shape does not convert .xls and .xlsx files.
If an incorrect URL is being used at runtime, the debug log is capturing the design time URL.
When configuring a web service, when entering the parameters, if the user presses Enter, the window closes without saving the values.
Inside the Managed Code C# snippet, the Intellisense for System.Xml and System.Web is not working.
In Japanese environments, the window for the Read Files AgilePart is not displaying properly.
Text-based email templates do not support new line characters.
The Word AgilePart is appending a file extension to the destination URL.
Schema Intellisense is not refreshed in the Email Template Editor when the schema is modified while the Email Template Editor dialog is open.
If a value is not configured, the validation for the Word Creator AgilePart is not working.
In the DateTime AgilePart, the configuration for the Input time 2 format field is not getting saved.
In an AgileShape, if the Length value is changed, this is not reflected in the value of the Expected Time property.
If a Shared Custom Attribute value is changed, the new value is not reflected in the running process instances.
If multiple Update Custom Attribute AgileParts are running at the same time, a race condition occasionally occurs where one instance of the AgilePart is able to update the value successfully, but another fails. The concurrency mechanism for the Update Custom Attribute AgilePart has been enhanced to avoid this issue.
If a process includes a Process Adaptation AgileShape, and a rework occurs on the process, the tasks that were previously completed within Process Adaptation AgileShape are completed automatically.
In the XML schema dialog, an unhandled exception occurs when a user modifies the element name and changes the type.
The manage process attributes functionality is allowing duplicate attributes to be defined.
In the Word AgilePart, when a user clicks Load Fields, the first element in the Word template is not loaded.
The values set by user-defined properties in a Dynamic Group AgileShape are not getting saved to the AgilePoint database.
In Visio 2010, when a user right-clicks on a non-AgilePoint shape, the Convert to Activity option is not available in the context menu.
In the PDF Converter AgileShape, if an image is larger than 8.5" x 11", the image is cut off. This has been fixed so that the images are now shrunk to fit the page.