Main Product Version: 10.1
Service Release Version: 10.1.1
Date of Release: 01/05/2015
- Mi-Forms is dependent on .NET Framework 4.5. Be sure to install the appropriate framework revision before installing Mi-Forms.
Changes to the Mi-Forms .NET Object Model, and Windows SDK
Enhancement – Added ability to disable touch globally and to disable specific touch gestures
New properties have been added to the MiFormsComponent to allow for the disablement of touch globally and for the disablement of specific touch gestures such as zooming, panning and swiping.
Enhancement – Image capture dialog in image annotations now handles rotation properly
The image capture dialog used to capture images for image annotations now handles rotation properly and provides the ability to explicitly rotate the image as needed.
Enhancement – A new property Wrap was added to the GridColumnProperty object
A new property that allows wrapping of data displayed in a column in a grid.
Enhancement – A new property allows for emulation of a stylus with a mouse
A new property MouseStylusEmulation has been added to the MiFormsComponent to allow for testing of inking via mouse.
Enhancement – Added Data Replication DLLs and documentation to installer
The DLLs necessary for Windows data replication and the documentation on how to use data replication has been added to the SDK installer.
Bug Fix – Attempting to render an image of a sub-form session in a reloaded session fails
If a session already containing a sub-form session is reloaded, then attempting to render an image of any page in that sub-form session will fail. This has been resolved.
Bug Fix – Toggling the Highlight property of barcode fields does not redraw the field
If the Highlight property is toggled on an already displayed barcode field, the field does not properly redraw itself. This has been resolved.
Bug Fix – Toggling the Highlight property of grid fields does not redraw the field
If the Highlight property is toggled on an already displayed grid field, the field does not properly redraw itself. This has been resolved.
Bug Fix – Changing the highlight color of a dynamic label does not redraw the field
If the color of highlighting on an already displayed dynamic label is changed, the field does not properly redraw itself. This has been resolved.
Bug Fix – Toggling the Highlight property of fields currently underneath regions does not redraw the field
If a field is currently underneath a semi-transparent visible region, the field does not properly redraw itself. This has been resolved.
Bug Fix – Loading a form into the component while the width or height of the component is set to 0 prevents subsequent redraws
If a form is loaded into the MiFormsComponent while its width or height is 0, the component will prevent itself from redrawing. However, when the component is then resized the form will continue not to properly redraw itself until the page is changed or the currently active form is changed. This has been resolved.
Bug Fix – Attempting to set focus to a field while the height or width of the component is set to 0 causes an exception
If a form is loaded into the MiFormsComponent while its width or height is 0 and then focus is set to a field, the component will raise an exception. This has been resolved.
Bug Fix – Building a form’s XML representation with background images results in an absence of background images if they have been added via AddPageBackgroundImage
If a form is loaded into the component having had its background images added via AddPageBackgroundImage() and that page is not displayed to a user, then when creating a form XML representation that should contain the background images, the background images are missing. This is most notably the case when the server attempts to export a session export that should include background images. This has been resolved.
Bug Fix – getGridSelectedRowIndex returns incorrect value after the grid is cleared
If a user selects a row in a grid and then script subsequently clears the grid, the value returned from getGridSelectedRowIndex will still be the last selected row rather than -1. This has been resolved.
Bug Fix – setValue exceptions in Internet Explorer if used on an individual checkbox
If the setValue API call is used on an individual checkbox (rather than the group), this will raise an exception in Internet Explorer. This has been resolved.
Changes to the Windows Mi-Forms Client & Agent
Enhancement – Added Data Replication DLLs to installer
The DLLs necessary for Windows data replication have been added to the Client installer.
Bug Fix – Launching the Client from a digital pen docking causes the validation window to be sized to a width of 0
If the Client is launched as the result of a digital pen docking, the validation window in data review mode is set to a width of 0 and it must be toggled off and on to be visible. This has been resolved.
Changes to the iOS, Android and Mobile Web Mi-Forms Client
Enhancement – Supports launch via URL scheme
It is now possible to launch the application from another application, and to start a specific form with prefilled data.
Enhancement – Improved password storage
The application now stores passwords on the local device in a more secure fashion.
Enhancement – Network error messages improved
The error messages displayed when encountering a network error (e.g. when attempting to upload a form while disconnected) have been improved.
Enhancement – Added ability to launch new instance of same form on discard
When discarding a form, it is now possible to automatically launch a new instance of the same form.
Bug Fix – GPS field may display incorrect value in eastern longitudes
If a GPS field is configured to use the ‘X’ format character, then in eastern longitudes, then rather than an “E” appearing in the field’s value, the current elevation will be inserted. This has been resolved.
Bug Fix – Changing server settings while offline after having logged in with valid credentials does not provide a proper error and instead ignores the change
If a user has logged into ServerA with valid credentials and then attempts to change to ServerB while offline, the application will detect it being offline and not save the changes to use ServerB. This has been resolved in that when changing server information the device must be able to make a successful connection. If it cannot, then the user is prompted and the changes are reverted.
Changes to the Mi-Forms Designer
Enhancement – Added Data Replication DLLs and documentation to installer
The DLLs necessary for Windows data replication and the documentation on how to use data replication has been added to the Designer installer.
Changes to the Mi-Forms Server
Enhancement – Improved Active Directory synchronization
Active Directory synchronization has been improved in several ways as noted below:
- Synchronization schedule is now based on wall clock rather than on time since last sync. This means that if the server or app pool is restarted, a synchronization will not occur until the appropriate amount of time after the previous sync rather than immediately.
- In a clustered environment, only a single node will attempt a synchronization at a given time
- Active Directory synchronization may be disabled via web.config if for instance a specific node should not attempt synchronization
- Active Directory may be made to log to a separate log file
- The user interface for Active Directory synchronization has been moved to the standard administration pages rather than the global administrator page
Enhancement – Improved customer setup page
The customer setup page for adding or editing customer details has been improved both in interface and functionality as described below:
- Added ability to test data source and database inline
- This test now includes administrative connectivity tests
- Added ability to store a SQL authentication administrative user for the purposes of DB creation and update
- Streamlined the UI
- Provided progress spinners for long running operations
- Removed Active Directory settings
Change – Authentication Errors from services provided by MFormsWSEx.asmx no longer provide details on user validity or exception details
When calls to these services return an authentication error due to a non-existent user, the fact that the user doesn’t exist is no longer reflected in the error response. Additionally all authentication errors no longer provide exception details.
Change – Server no longer uses SQL DMO to create or query update customers
When updating customer databases to create or update customers, SQL DMO is no longer used. This removes the need to have the SQL 2005 Compatibility Pack installed and it has been removed from the prerequisites of the server.
Bug Fix – In a clustered environment, multiple nodes may try to reprocess sessions on startup
If a machine suffers a failure while form(s) are in the _Processing queue, it is possible that when other machines or app pools restart multiple machines will attempt to reprocess the form(s) simultaneously. A change has been made such that only the machine that left the form(s) in the _Processing queue will attempt to reprocess them upon startup. If that machine will be permanently removed from the cluster (e.g. hardware failure), the form(s) must be moved manually to the _Incoming queue.
Bug Fix – When Active Directory synchronizes an inactive user to the server, the user license count is incorrectly incremented
Active Directory will synchronize inactive users to the server if they are in a monitored group. When this occurs the currently used license count is incorrectly incremented. This has been resolved.
Bug Fix – When adding an inactive or locked user from the Users.aspx page or the Setup.aspx page, the user license count is incorrectly incremented
If an inactive or locked user is added via the Users.aspx or Setup.aspx administration page, the currently used license count is incorrectly incremented. This has been resolved.
Bug Fix – A user may be activated via Users.aspx, Setup.aspx or Active Directory even if the current user license count is at its maximum
If the current user license count is at its maximum it is still possible to reactivate a user via the Users.aspx or Setup.aspx pages, or via Active Directory synchronization even though that exceeds the allowed user count. This has been resolved.
Bug Fix – Deactivating a user via Users.aspx, Setup.aspx or Active Directory does not lower current user license count
If a user is deactivated via the Users.aspx or Setup.aspx pages, or via Active Directory, the current user license count is not decremented until the server’s app pool restarts. This has been resolved.
Bug Fix – Data Replication web app is missing EntityFramework DLLs
The data replication web app is missing EntityFramework.MappingAPI.dll and EntityFramework.BulkInsert.dll. This has been resolved.
Bug Fix – The device_id column of the audit_trail table is too small for some browsers
When a user fills out a form via the web, the device_id of the user is recorded as their user agent string. In some cases this column was too small for certain browsers resulting in a problem with uploading the form. This column has been made larger in v10.1 customer databases.
Bug Fix – An extraneous ; in connection strings for customers causes an error on the Setup.aspx customer list
If there’s an extraneous ; in a connection string of a configured customer, displaying the customer list on Setup.aspx will fail. This has been resolved.
Bug Fix – Passing incorrect credentials to digital pen PGC file processing indicates a success message rather than an error
If invalid credentials are passed to the PGC.aspx page for the purposes of PGC file processing, the server returns a success message rather than an error. This has been resolved.
Changes to the Mi-Forms Print on Demand SDK
No changes have been made to the Mi-Forms Print on Demand SDK in this release.