Page: 7.4.7 Release Notes
Page: 7.3.9 Release Notes
Page: 7.3.13 Release Notes
Page: 188.8.131.52 Release Notes
Page: 7.3.10 Release Notes
Page: 7.3.8 Release Notes
Page: 184.108.40.2069 Release Notes
Page: 7.3.12 Release Notes
Page: 7.3.11 Release Notes
Page: 7.4 Release Notes
Page: 7.5 Release Notes
7.4.7 Release Notes
These Release Notes describe the following topics for the 7.4.7 release:
Download a and a PDF version of the System Requirements.of the
New in this Release
Enhanced support for iOS 6
With our 7.4.7 Maintenance Release, Verivo has further optimized and fully certified the iOS client to run on iOS 6.0. Verivo apps are now built using Xcode 4.5 and also leverage the new maps for click-to-maps.
Enhanced support for iPhone 5
Verivo apps running on the new iPhone 5 can now take full advantage of the entire screen resolution. Verivo apps built using 7.4.7 will use the new 568@2x images for Login, Splash and Background and will no longer run in letter box mode. Verivo has also fully certified the 7.4.7 release for iPhone 5.
Support for Google Cloud Messaging (GCM) service
With the release of Version 7.4.7, Verivo now supports GCM as the Android Push service replacing the previous C2DM push system. Read more details about upgrading to GCM for a Push Provider in the Upgrading to Version 7.4.7 section below.
iPad mini and iPad 4 support
This release also extends support for the new iPad mini and fourth generation iPad. The new iPad mini will automatically run the iPad workflow and scale images appropriately.
Android Jelly Bean (OS 4.1) support
This release also includes support for Android's Jelly Bean operating system.
The following changes apply to the Verivo documentation set:
- Updated the Push documentation to describe how to use Google Cloud Messaging (GCM) as the push provider. For more information, see Using the Push Service.
- Updated the information on customizing the look and feel of your app to include iPhone 5. For more information, see Multi-Platform Management.
- Added plug-in scripting documentation that describes how to modify data requests and responses at run time without compiling, rebuilding, or reinstalling. Plug-in scripting can be used with the REST, WSDL, and WCF plug-ins. For more information, see Plug-in Scripting.
The following system and platform requirements are supported by 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.1
This release also supports Good Dynamics version 1.0.2880.
For full information about product requirements, see Installing the Platform.
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-46447||Interpret an HTML error code of 302 from Siteminder as a 401 to redirect a user to the login screen.|
|VS-46564||On iOS 6, the action bar extends beyond the edge of the visible screen.|
|VS-46565||Support the new mapping application in iOS 6.|
|VS-46567||Map rotation and rotation lock now work correctly on iOS 6.|
|VS-46137||The global search Scope button in the search input field on iOS 6 has grey corners when it should have transparent corners.|
|VS-46145||Global search results on iOS 6 do not show List screens that are nested within Form screens.|
|VS-46148||The target view of a Screen Host control on the Global Search screen is not respected when you do a global search on iOS 6.|
|VS-47051||Content briefly appears in the Screen Host control and then disappears.|
New Login, Splash, and Startup images added to the Verivo build system to support iPhone 5.
Navigation bar, Sync refresh toolbar buttons, and other UI that are completely below the 480pt line cannot be tapped on iPhone 5.
Cannot start input on a vertically aligned Signature control when it is in a scrollable area.
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 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.
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.
If you use an Image Field control to capture an image from an iPad's camera, and then uploaded the image from an Add or Edit screen, the upload can fail.
Workaround: Edit the Web.config file for your Verivo AppServer to set the
<httpRuntime maxRequestLength="10240" executionTimeout="600"/>
App crash on login when client has pending uploads and device was previously in airplane mode. The app completes the upload and immediately crashes.
Upgrading to Version 7.4.7
The following table highlights components that must be upgraded in order to support new features in this release.
|Component ||Upgrade?||Required Version|
Upgrade procedure from Version 7.4
The section Upgrading the Platform describes the steps required to upgrade a previous installation of Verivo’s enterprise mobility platform Version 7.4 to Version 7.4.7. The following sections provide an overview of the steps that you might have to follow to perform the upgrade.
For information on upgrading from release 7.3.x to 7.4, see the 7.4 Release Notes.
As of June 26, 2012, Google's Cloud to Device Messaging (C2DM) framework has been deprecated by Google in favor of the Google Cloud Messaging (GCM) standard. With the release of Version 7.4.7, Verivo now supports GCM in replacement of C2DM.
To upgrade an app that uses the Verivo push service to Version 7.4.7, you must perform the following steps:
- Upgrade your installation of Verivo's enterprise mobility platform to Version 7.4.7. For more information, see Upgrading the Platform.
When you upgrade the Verivo configuration database, the C2DM configuration fields Google Account and Google Account Password in the Push Settings screen of AppStudio are replaced by the GCM Project ID and GCM API Key fields. These new fields are empty and you must set them before you can use GCM.
- Set up a GCM push provider. For more information, see Configuring the Push Provider.
- In AppStudio, configure your app to use GCM. For more information, see Push Service Configuration.
You cannot create a new C2DM account but you can configure a push provider to use an existing C2DM account. However, only Version 7.4 or earlier of Verivo's enterprise mobility platform supports C2DM.
If you want to still use C2DM, you can clone your existing configuration database and upgrade the clone to Version 7.4.7 You can then continue to use the original configuration database with Version 7.4 or earlier to make use of C2DM.
For more help
You can also obtain help by submitting a technical support incident at support.verivo.com, or sending email to email@example.com. Verivo's Support Group will promptly respond to your support request.