Page: 7.4 Release Notes
Page: Custom Numeric and Date Formatting
Page: Predefined Numeric and Date Formats
Page: 7.3.9 Release Notes
Page: 7.3.13 Release Notes
Page: 220.127.116.11 Release Notes
Page: 7.3.10 Release Notes
Page: 7.3.8 Release Notes
Page: 18.104.22.1689 Release Notes
Page: 7.3.12 Release Notes
Page: 7.3.11 Release Notes
7.4 Release Notes
These Release Notes describe the following topics for the 7.4 release:
Download a PDF version of the Release Notes.
New Product Features
East Asian language support
Verivo has extended its support for international customers and global deployments by enabling our AppServer to read and write data containing East Asian characters.
- Enhanced localization capabilities now support UTF-8 encoding of all left-to-right languages, such as Chinese, Japanese and Korean.
- App developers can leverage the device’s language setting to show user data in their preferred language. Dates and numeric formatting are also applied on the device, so the user sees the data in the format to which they are accustomed.
Formatting based on user's device settings
Configuration of Date and Numeric formatting has been simplified to allow app developers to choose from predefined formats within AppStudio and allow the device to render the formatting based on the device's locale. An admin setting a date format as Short Date and Time will display as 1/2/03 11:05 PM on iOS devices with a en-US locale and it will display as 02.01.03 23:05 on a device with a German locale such as de-DE.
- Action Bar, a native UI element on Android, is now fully supported. Use of the Action Bar provides a familiar Android look and feel for users navigating within an app. The Action Bar, located at the top of the screen, conveniently displays all top-level navigation buttons, Back button and the Menu button. Apps already utilizing Verivo's graphical navigation bar will be able to seamlessly take advantage of this native UI element.
Version 7.4 is certified on Android 4.0 (Ice Cream Sandwich) and now includes support for UI components such as the Action Bar, and extends support for the latest devices.
- App developers can enhance the mobile users experience by providing additional data or alternate layouts when rotating the device from portrait to landscape. The existing Alternate Screen/View and rotation properties are now supported on the Android clients.
Screen Search for iOS
Screen search, previously available to BlackBerry and Android users, is now available on iOS applications. Extension of this familiar feature to iOS makes the user experience and the app interface consistent across all platforms. This feature allows your mobile users to filter the on-screen data as they type in the Quick Find field.
Local Data Enhanced Search
App developers can now allow users to search with “starts with”, “contains” or “equals”, when searching within local data both on and offline.
Plug-ins have been updated to support East Asian languages and are now also released as a separate plug-in package, giving you the ability to get more frequent updates to plug-ins without waiting for an update to Verivo’s enterprise mobility platform.
Sample & Tutorial updates
This release includes a new uplifted version of our Elevate Supply demo app:
- Smartphone and Tablet workflows
- REST data source for CRM data
- Enhanced UI
The following changes apply to the Verivo documentation set:
- Updated REST, WSDL, and WCF plug-in documentation. For more information, see the Working with Plug-ins.
- Added new doc on the following features:
- Added security recommendation section to the Deployment documentation. For more information, see Deploying Apps.
The following system and platform requirements apply to this release:
- Microsoft .NET Framework v4.x or higher
- BlackBerry 5.x, 6.x, 7.0 and 7.1 with SD or eMMC card. For an SD card, you need a minimum capacity of 1 GB with a minimum of 10 MB free.
- iOS 5.x - 6.0
- Android 2.2 – 4.0
This release also supports Good Dynamics version 1.0.2880.
For full information about product requirements, see Installing the Platform.
Upgrading from Version 7.3
The following table highlights components that must be upgraded in order to support new features in this release.
|Component ||Upgrade?||Required Version|
The section Upgrading the Platform describes the steps required to upgrade a previous installation of Verivo’s enterprise mobility platform to Version 7.4. The following sections provide an overview of the steps that you might have to follow to perform the upgrade.
Upgrading the Verivo configuration database
The Verivo configuration database is a Microsoft SQL Server database that stores application configuration information. To upgrade an existing configuration database to Version 7.4:
- Backup your current configuration database.
- Run the database upgrader. For more information, see Upgrading an Existing Configuration Database.
- Ensure that your configuration database is binary compatible. For more information, see Upgrading a Localized App From Version 7.3.
Inspect numeric and date/time formats
If you are upgrading an app from Version 7.3, the Format property of any Date Field and Text Box control that uses a Version 7.3 predefined data format is automatically updated to use a new Version 7.4 data format. Depending on the original 7.3 data format, the output in Version 7.4 might not appear exactly as it did in Version 7.3. For more information, see Upgrading a Localized App From Version 7.3.
Update the web.config file
When you upgrade your Version 7.3 Verivo AppServer to Version 7.4, you might decide to retain the AppServer Web.config file that you used with Version 7.3. If you do, you must edit the
<globalization> tag in the Web.config file as described below:
- Version 7.3
<globalization requestEncoding="utf-8" responseEncoding="Windows-1252"/>
- Version 7.4
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
Ensure that the Android Action bar appears correctly
Version 7.4 adds support for the Android action bar. The Android action bar appears automatically in your app at the top of the device's screen. The action bar provides a simple way to add actions such as navigation and search to your app. After upgrading to Version 7.4, ensure that the app looks correct when the action bar is visible. For more information, see Android Action Bar.
Resolved issues are listed below. For detailed information, contact the Verivo Support at support.verivo.com. Information about issues previously resolved can be found in the release notes for earlier versions.
|VS-44094||Can now create custom date formats in the Local Manager for different locales.|
|VS-42095||AppStudio only compiles .NET 2.0 plug-ins for WSDL based plug-ins.|
The GPS Last Known setting has been deprecated and removed from AppStudio.
The keyword 'LIKE' in an 'IIF' statement fails to generate correct client-side SQL.
Deleting a style modifies other style names and rearranges the order of the style list.
Importing an app as a new app removes conditional navigation view instructions.
Moving a control into the Header pane of a List deletes the control.
|VS-30150||The Communication Properties area of the View Properties has been redesigned to simplify editing.|
|All data synchronizations fail if a non-mapped entity is set to sync.|
|Entity and control names should not be required to match for offline upload and find.|
|Add better server logging for conditional navigation.|
|Numeric password does not get decrypted before being sent to a plug-in.|
Data sync requests now trigger an error and prompt the user to log in again if the authentication session expires.
|VS-33271||All controls should receive focus on touch devices and not just Text controls.|
|Matching of entity and control names should not be required for offline upload and find|
A nested vertical Region control with no explicit height setting does not render correctly.
|VS-35165||The appearance of the Lookup control is inconsistent.|
Sticky headers with local data do not show images.
Collapsing a Region control that contains a Screen Host control still shows title of the Screen Host control.
The Android client does not show the "Save" system menu for an Association Field control.
|VS-35975||Hint text and cursor is center aligned for a Text Box control in a center-aligned Region control.|
|VS-36256||Deleting all records and then logging in again throws an "Invalid startup screen" error.|
|VS-36622||No visible failure displayed for the Association Field control when a relation entity is not synced.|
The Quick Find fields for a Screen Host control appear underneath the list screen host headers until text is entered.
A visible controls in an invisible Region control triggers a continuous relayout pass.
Prefilling a Form view from a local list fails when any prefill value is Null.
Pending offline uploads contain the incorrect date.
A Screen Host control that points to a List screen was sized incorrectly.
A narrow selection filter from the wrong view is applied to search results.
Clients display an error because the persistent cache is in an invalid state after content authentication logout.
A java RuntimeException is thrown after setting a Choice List control to be not-editable.
Sizing a Region control's height by percent causes the app to fail when the control is part of the header of a Screen Host control.
Setting a Date control's value by using a script sets it four hours later than it should.
Navigating directly to Find Results screen without first performing a find displays a drop-down over the Find screen.
The titles of action-only screens added to the list of recent items.
If a device loses its connection while downloading a config, the app causes a Null Pointer exception on the next log in.
Setting Hide if Empty on a Region control that contains a Screen Host control causes the Form screen containing the Region control to not display.
No tab is shown as selected by default for a List screen in a Screen Host control within a Region control.
The title of a Region control does not appear in the right location when the Region control is in a Screen Host control.
|Local finds perform a search based on the data type of an entity field.|
|The keyboard does not disappear after drilling down into a screen.|
|A menu of type Clear All clears the default value from non-editable text controls.|
|Configurable list headers appear on top of the List screen data when the List screen is in a Screen Host control.|
|If you navigate back to the login screen that use content authentication, the screen retains the username and password.|
|Find screens show data from previous finds.|
|Default images that are hidden but are then made visible through scripting never display.|
|Selecting 'More' replaces the existing List items, rather than adding to the existing items.|
|Clicking a control in a list row does not allow scrolling of the list.|
|A background image resizes when the keyboard opens.|
|Content authentication does not display Waiting Text or processing indicator on a Save operation.|
|Refreshing a Screen Host control after authentication timeout should clear protected screens from the back stack.|
|Screen Search should respect the Find Screen Behavior app property value.|
|Sticky headers hide data row when performing a Screen Search.|
|Switching between views that contain sticky headers causes the wrong header to be displayed.|
|The 'More' button should be removed when a Screen Search is activated.|
|Screen Search hint text is not being applied consistently across device platforms.|
|Refreshing a Screen Host control that was originally made visible by a script resets the Screen Host control to its original state.|
|Screen Search does not filter on sort fields.|
|User not automatically navigated back to the Find screen after a plug-in throws an error on the Search Results screen.|
|Find targeting form screen requires the form's primary key before requesting data.|
|Sticky headers on List screen does not render when the List screen is contained within a Screen Host control.|
|The ampersand character, '&', is not encoded correctly in a Find screen.|
|Provide better error handling when the user hits the MDS limit.|
|Button controls are not using scripted styles.|
|Start-up load requests should continue after the device comes back into coverage.|
|Data synchronization should handle a session timeout for proprietary authentication.|
|Hybrid buttons are not working when the Save action is performed on editable Form screens.|
|On devices running OS 7.0, navigating to a Browser Field control by using the back button results in an empty field.|
|Clear the backstack after forcing a client log out.|
|On log in, OnLoad scripts are not triggered for the Home screen.|
|Setting a Date control's value by using a script sets it four hours later than it should.|
|OnLoad scripts are not being triggered for Find and Add screens when the assigned view is not the top view.|
|Recent items which prefill from the previous screen now display when viewed.|
|Matching of entity and control names should not be required for offline upload and find.|
|Cannot enter numeric values as the first character in the password field for OS 7 virtual keyboards.|
|Controls in invisible Region controls that are made visible by a script are not focusable.|
|User not automatically navigated back to Find screen after plug-in throws error on Search Results screen.|
|Content authentication log out using Action-Only screen is not functioning.|
|Hint text in a Lookup control is sent up to the server as a value in find request.|
|Map not correctly zoomed out on load.|
|Screen Host control within a collapsible Region control is not displaying when the Region is initially set to collapsed.|
|When a screen has no records, it should maintain a reference to the previous screen.|
|The Upload Status entry appears twice in the menu.|
|An edited offline Add screen fails to upload when the device is back in coverage.|
|Quick Find and Screen Search hint text is not appearing properly.|
|Unable to refresh a Screen Host control made visible by a script.|
|User should be taken back to first protected screen if the log out menu has no target screen and view.|
|Able to gain focus on invisible controls that have a |
|A Form screen in a Screen Host control targeted by a Find screen in a Screen Host control never appears.|
|A Find screen targeting a Screen Host control does not use filter field information from the selected row on the preceding screen.|
|Pressing the return key on a Find screen should trigger the search.|
|Screen Search does not persist on a screen using Auto Poll.|
|The pop-up keyboard can hide an editable control in a Screen Host control.|
|Improve performance issues when calculating sort column names.|
|Collapsed Region controls show the wrong default icon.|
|Matching entity and control names should not be required for offline upload and find.|
|For a list targeting a Screen Host control, disable table animation and always select the top cell.|
|Script is not being triggered for OnUnfocus event for the Choice List control.|
|After scrolling in an unsized List Screen Host control, you have to tap a record twice to drilldown into it.|
|Intelligent refresh does not get initiated for Screen Host controls on a Home screen.|
|List screen changes the row viewed on rotation to landscape mode.|
|User not returned to the Login screen after a data sync authentication failure.|
|Button control does not display when its Action property is set to with |
|Text truncation and the display of ellipsis is not working on List screens.|
|Association controls do not display their data.|
|Screens that use a navigation bar and that are protected by content authentication should select their original views on logout.|
|Collapsible Region controls with sticky headers display incorrectly after content authentication relogin.|
|Refreshing a Screen Host control that was originally made visible by a script resets the Screen Host control to its original state.|
|User not automatically navigated back to Find screen after a plug-in throws an error on the Search Results screen.|
|Predictive search (auto fill) uses the wrong search parameters.|
|Horizontal View Selectors do not resize on screen rotation.|
|The number of characters required to start a search on a Lookup control with the Don't Prefetch property enabled should be consistent.|
|Popover window is not dismissed on a save and navigate to its parent screen.|
|Cannot use click to email with multiple email addresses separated by commas or semicolons;|
The following issues remain outstanding as of this release:
For a List view that uses local data, sorting by a column that uses a calculated value does not work.
Workaround: Instead of using calculated columns, use individual fields that are mapped to data entities.
The Data Connector does not support table names with Unicode characters in the table names.
Workaround: Remove any high ASCII characters from table names before generating Stage tables and running the Data Connector.
Data sync does not evaluate the Formula field of an entity and downloads a blank value.
In Version 7.3, not setting the Format property of a Date Field control caused the control to display an unformatted value by default. In 7.4, the Date Field uses the
Workaround: If no format is required, change the Date Field control to a Text Box control.
The Android client currently does not support the new Google Cloud Messaging (GCM) service.
Workaround: You can continue to use the Cloud to Device Messaging Framework, until support is added.
The row count does not appear when viewing a screen used by the Association control.
On an Android 2.x device, the Global Search button does not work when the app's Graphical Navigation property is set to
Only one header appears when Group by field is not in the Header pane.
Workaround: Move the Group by field into the Header pane, or add a second field with the same data in the header and sort by that instead.
The navigation bar is drawn on top of graphs.
Workaround: Hide the navigation bar on screens that display graphs.
Memory management issues occur when typing in Japanese on devices running OS 7.1.
The device's activity indicator does not dismiss properly after downloading a graph from the server.
Non-touch devices running OS 7.0 do not move focus to non-editable fields, which can prevent scrolling to the bottom of a screen.
Workaround: To enable scrolling, add an invisible editable control to the end of the screen. For screens that have click action, add a menu item for the click action.
If you enable Predictive Caching on a system using an encrypted configuration database, you can create a race condition leading to failure of one of the processes.
Workaround: If your app uses Predictive Caching, we recommend turning off database encryption.
Calendar Find does not correctly switch to Agenda View.
Click-to-map controls open Google maps using Safari instead of Apple's new Maps app.
Workaround: The mobile user will still be able to get driving directions from the web app.
Apps installed on the new iPhone 5 run in letterbox mode, with two black bars on each side.
Click-to-email address does not prefill when the email address contains UTF-8 characters.
Workaround: This is currently a limitation of the iOS platform.
Setting the title style by using a script causes the Global Search button to disappear.
Workaround: Set the title style in the app configuration instead of using a script.
The Lookup control keeps filtered result set after dismissing and reopening an item.
Workaround: User can run another search to return the different result set.
The List screen view selector is not dismissed when focus is moved to the Quick Find bar.
Using the the
Workaround: Select a different format or use custom format.
Deprecations in this release
With the 7.4 release, Verivo will no longer support the following:
- Mixed display of row and extended data
- 2.0 and 2.1
- Graphical navigation bar invoked from hotkey
- Query screens
- 4.3 and earlier
Deprecations in upcoming releases
In the next maintenance release, we will be deprecating support for Android's Cloud to Device Messaging (C2DM) Framework. The C2DM framework will be replaced with Android's new Google Cloud Messaging (GCM).
For more help
You can also obtain help by submitting a technical support incident at support.verivo.com, or sending email to firstname.lastname@example.org. Verivo's Support Group will promptly respond to your support request.