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.
| Fixes | |
The following issues have been fixed in this release for AgileForms.
This fix addresses the following issues:
If the user attaches any file with a Japanese or Chinese name, the file name is replaced with an underscore.
In a multi-section AgileForm if a lookup returns multiple search results, and a user selects one of the results, the buttons on the form (Next or Cancel, for example) stop working.
Where read-only controls are used in a PDF created by the AgileForms PDF generator, the default values overwrite the actual values.
In AgileForms, translation is not allowed for the messages "Are you sure you wish to delete this entry?" and "Don't ask this again".
When a user creates a SharePoint list lookup, and uses a custom attribute with additional text in the Site URL field, the list lookup does not work. For example, http://{SharePointSite}/sites/apworkflow
When a user changes a drop-down control value that is bound to a web service lookup, a warning message appears saying something like, "Try to navigate away from the current page. Are you sure you want to navigate away from this page?"
Uploading user uploads to SharePoint, and replacing them with a hyperlink. This allows users to upload larger attachments.
Voting configuration in AgileForms Process Adaptation Shape does not work on the second iteration.
If the Field Layout control is set to CSS, and you try to change the horizontal size of your controls, a fatal error occurs.
Advanced Lookup does not work in the advanced validation section. This fails for section validations, display conditions etc.
For forms with controls that are bound to a lookup field from an external data source, if the lookup is modified (such as through the resource options or changing environments), the binding is not updated unless the user clicks "Update" on the field.
In the form Designer, when designing a subform, the field Properties pop-up appears at the top of the page, instead of appearing next to the field. On longer subforms, this is an issue because it is possible for the Properties pop-up to appear outside the visible area of the page.
When creating SharePoint lookups, if the SharePoint site doesn't have any sub-sites, then an error occurs when running "Get Servers" on the SharePoint Fields Wizard.
For NTLM based WebServices, the WSDL file cannot be read directly from a URL. Instead we need to download the WSDL as local file and then read while configuring the Web Service look up.
AgileForms is downloading images and CSS files from an external URL, which causes delays and sometimes does not work without an Internet connection.
Data Population does not work for AgileForms.
SharePoint Document Library integration works when defining it in the AgileForms administration interface, but not in the Envision interface. It simply does nothing.
Forms with only labels or headings throws a runtime error. It needs to have at least once input type field.
Several issues occur with the Allowed File Types group administration:
If a user creates 2 fields in the form designer, and provides the same value for the Data Name property, AgileForms provides a warning, but allows the conflict to exist. However, the end user receives an error at runtime. This issue has been fixed so that if there are fields with duplicate Data Names, AgileForms automatically appends a unique, random character string to prevent a runtime error.
When setting up SharePoint List Integration, if you delete one SharePoint field, all Form Field Token values are cleared.
When changing a DateTime field to the Display Style of text box, a fatal error occurs.
If you have a Richinput control in your form, and you try to open the form in preview mode, a JavaScript error occurs.
When the user accesses AgileForms Server administration options, a "session expired" message always appears.
The CAML, WSE, and SAP AgileSshapes do not return multiple records if used in AgileForms based process.
If an AgileForms AgileShape uses SharePoint list integration, it is not possible to modify a notification email.