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 AgileForms.
When a user clicks outside a Rich Input field, a dialog appears asking, "Do you want to navigate away?"
A Lookup Select One field in autosuggest mode doesn't cause a JavaScript error if a display value is null.
The completion and cancel URLs are missing from the form details tab.
The default language patch from AgileForms v5.0 SP2 is not included in SP3.
Lookup Select One fields in autosuggest mode work if the display value contains leading or trailing spaces.
Large HTTP headers in a Kerberos environment cause a JavaScript error.
If a form includes a text area field with length counter enabled in the library, an error occurs when another form in the process is opened in the Form Designer that doesn't have the text area control.
Validation messages appear inconsistently on repeating subforms.
If you specify an extra style sheet for a form on the details tab, it isn't included on the review page, but it is included on all other pages.
Using the plus (+) character in the instr() calculated field function causes the entire calculation to fail, so no value is returned.
After applying AgilePoint v5.0 SP3, user upload integration fails to save uploaded files to AgileForms Server.
On the Update Resources window, the View & Update All Imported Resources in Current Form link provides a list of components that can be updated on the Update Resources window. This link does not work.
View & Update All Imported Resources in Current Form link should provide a list of components that can be updated, but this is not working. When a web service lookup is modified, it appears in the list with out of date status, but the lookup cannot be updated.
Print PDF shows an incorrect print layout. All the controls in the form appear in linear order, and it ignores the layout designed using the layout feature in the Print menu.
Creating a new Advanced web service lookup fails to retrieve the WSDL of a web service with NTLM authentication.
The form designer opens in tabular mode, even if the default form rendering mode is CSS.
Auto Registration fails for new users who are members of a large number of groups.
CSS positioning issue with calculated fields in library table.
If AgileForms is not running on port 80, when the user right-clicks any of the control added inside a compound field to see its properties, an error appears.
Mandatory conditions dependent on calculated field values are correctly updated when calculation changes.
Sharepoint Document Library integration actions do not generate the correct base URL when selecting a document library inside a subsite.
When a multiple select control is configured for in-field help inside a sub form, and the sub form is configured to column view, the multiple select control shows help text in each repeating row or data row. Help text should display in the header row only.
For a repeatable subform, when the advanced property of subform Don't automatically show blank row is checked, the Add button is hidden, and there is no way of adding a new row in repeatable sub form.
AgileForms with more than 500 input fields do not work after Microsoft .NET Framework security update.
Update Form Components screen crashes if lookup in a form has been deleted.
Lookup Select One value is lost if it depends on the value of a field defined later in the form.
Repeated values (<AF :*> token syntax) are not supported in a web service call.
When a user right-clicks on a button (such as Lookup or Calculated Field) in the form designer, an error appears.
The upload field SharePoint URL is replaced if the file has already been uploaded.
SharePoint lookup field updates are not applied to form in Update Resources screen.
When closing a pop-up sub-form, a "Method does not exist" error appears.
Right-clicking in design mode occasionally displays the wrong field properties.
XML file integrations do not work correctly in AgileForms.
Platform-specific integration action types display incorrectly in AgileForms.
The Rich Text field's Add Hyperlink function does not work in v5.0 SP3.
On using a Lookup Select One object that gets its source from a SharePoint List, the Lookup returns "String;#" as the prefix of the returned values for calculated fields.
Users cannot edit library columns in AgileForms once the list or library columns in SharePoint have been renamed.
The NTLM SOAP handler does not return error responses correctly when the connection fails.
Filtering criteria in a SharePoint List Lookup against a Yes/No column always evaluates to False, and does not return any item.
When editing a SharePoint List Lookup, the change does not appear on the screen after updating.
The Import Process as XML File option does not work for AgileForms processes.
If no AgileForms process has been published yet, the AgileForms Process Initiator Web Part displays an error message, instead of saying "No process found."
When you attempt to export an AgileForms process as XML, the AgileForm file (not the Envision process) becomes corrupted.
An apostrophe in a process instance name causes an exception.
Display conditions applied to a repeating subform are only applied to the first row.
In v5.0 SP3, the ability to edit a section directly by right-clicking the section number was erroneously disabled. This functionality has been re-enabled.
The {ListID} token is not correctly updated when you delete any row in a repeatable subform that is not the last row.
If a repeatable subform has a blank row, the subform is not populated with data.
Images included in PDFs do not work correctly when an AgileForms IIS site is not running on port 80.
Compound fields now support 2 additional options:
In a compound field, the entry() function is not working properly.
Sections appear in the form designer, but not in the AgileForms library.
When you create a new Active Directory user, if you do not have values for full name or email address, the user is not added. With this fix, a default value is entered automatically, so the user can be added.
AgileForms logs are now stored under the FS2 within the AgileForms Server installation.
In previous releases, the logs were stored under the hard coded path C:\platform-logs\