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 R2 / Fixes | |
The following issues have been fixed in this release for AgilePoint Server.
In Enterprise Manager, when the average event processing time displays, sometimes it incorrectly displays with a minus sign (-).
In the MailApproval AgileConnector, in the Connect to SharePoint window for SharePoint based processes, if the administrator selects the Custom Use option, users are not authenticated correctly.
In the MailApproval AgileConnector, in the Connect to SharePoint window, the default selection should be AgilePoint System User, but it is not.
In the MailApproval AgileConnector, when approving or rejecting incoming requests from SharePoint based processes, the X in the body of the e-mail should be optional.
In the MailApproval AgileConnector, when approving or rejecting incoming requests from SharePoint based processes, approval values should only be True or False in the body of the e-mail.
When there are multiple NLB AgilePoint Server environments, such as a Production NLB environment and a QA NLB environment, if the Production AgilePoint database is copied for testing purposes, and the QA AgilePoint Server is connected to the copied database and restarted without restarting the QA CSM, then the QA AgilePoint Server connects to the Production CMS and causes unexpected problems.
When a large number of process instances are started using Database insert event service, the memory consumption for the AgilePoint Server process increases, and remains high even after all of the events are processed. AgilePoint Server must be restarted to free up the memory locked by the process.
When the AgilePoint system user does not have permission to write the last synchronized date in Windows Registry, the ADSync module runs every 5 minutes. This causes the server process to accumulate a lot of memory that does not get disposed. Sometimes even if the ADSync runs once every day, the server process accumulates lot of memory because of synchronizing multiple groups with thousands of users.
The exception, "NullReferenceException key not found," occurs when using AgilePoint Server in Dutch, French, and Arabic.
In the MailApproval AgileConnector, on the Configure Email Approval window, on the Settings tab, the controls are not visible for the EWS settings.
In the MailApproval AgileConnector, if the protocol is IMAP, messages are not deleted after they are processed for approval or rejection.
In the MailApproval AgileConnector, approving or rejecting a request is not processing properly if the email format is of HTML type and uses a web-based email clients or a mobile device for processing requests.
When Event Services uses EWS mail server or IMAP mail server, duplicate process instances are created, thus initiating an infinite loop of creating process instances. This is an issue in AgilePoint BPMS v5.0 SP4 only.
When Event Services uses IMAP or Exchange Server 2007, email attachments are not saved, even if it has been configured to do so.
If an error occurs while processing events, the error message is not stored in the AgilePoint database.
With this fix, the error message is stored in a WF_LARGE_TEXT table in the database.
WFEvent object returned by CreateWorkItem API call has empty WorkItemID.
Migrating a process instance fails if the process was originally instantiated based on a process model created in an AgilePoint version prior to v5.0, but the process model was modified, saved, and republished using AgilePoint v5.0 or higher.
When migrating a process instance from one process model version to another, the data schema does not get updated.
Numerous and concurrently long running synchronous AgileParts prevents the processing of the Suspend or Cancel Process Instance events.
If a user name includes an at (@) symbol — for example MYDOMAIN\user@email.com — and in an email template the user name is referenced in the To or CC field, the user name cannot be resolved at runtime, and AgilePoint Server fails to send emails using the template.