Convertigo projects rely on a data model. In previous versions, this data model was held in a special XSD file in your projects. Each modification of a Sequence structure was replicated in the XSD file. Unfortunately this mechanism sometimes was corrupting the XSD file causing projects to lose their data model.
In Version 7.1, the whole mechanism has been reviewed. Now the data model is held directly in the sequence definitions, so there is no way to have a discrepancy between the model defined by a sequence and an external XSD file. Although the model is now held in the sequences, some external models still have to be referenced. This is why a new object called ‘reference’ can be added to your project.
You can have references to external XSD files, or to Web Services WSDL files. Of course, you can have references to other Convertigo projects.
One of the greatest benefits of the new architecture is the ability to manage multiple XSD Schema namespaces. For example, assume your application will consume data from a SOAP web service defining customers from an ERP and another SOAP web service defining customers from a CRM. Most likely, you may have a conflict with the customer definitions because both services will define the same fields for the customer object. This is where the namespaces come in! Convertigo 7.1 will properly handle multiple namespaces and avoid conflicts between different connectors.
We designed a new View to help the developer to display the data model. This is called the “Schema view”:
As you can see in this sample view, we display the schemas for all the namespaces, (Our own project’s namespace, and the “websamples.countryinfo” namespace). If we select a schema element, the exact XSD will be displayed in the second column, and a sample data model will be displayed in the third column.
This view helps you to understand your project’s data model. You can also check if the model is valid as Convertigo Studio will validate the data model schema.
Also, when you execute a Sequence, Convertigo studio will validate the Sequences output against the data model’s schema. This leads to better, checked and mastered data models in your projects.
In 7.1, we reviewed the mobile device object concept. Now, we speak about platforms representing target mobile platforms such as iOS, Android, Windows Phone 7, Windows Phone 8 and Blackberry 10. This means that for a given platform, for example iOS, you could have an iPhone 5 device and an iPad Air device, both based on the same iOS platform.
This is why for example, in the Convertigo Studio you may see now:
|As you see, Galaxy note 2 and Galaxy S 3 shares the same Android platform.|
Also, in the projects explorer view, this structure is represented this way:
|Your global cross-platform application will be held in the ‘mobile’ folder but you can have specific platform/device features that you would like to specialize. In this case, just put you specific code/resources in the correct platform folder. Convertigo mobile builder will merge and produce an app targeted for each platform.|
Global Symbols is a great feature used for production. This enables projects to be deployed on a server being agnostic about the running environment. For example, the same project can be deployed to a Q&A server and to a production server. As Global Symbols are attached to the Servers and not the project, the Q&A server will connect to a Q&A environment and the production server will connect to the production environment.
In previous versions, Global Symbols had to be declared and prepared before a project using symbols was deployed. Deploying a project when a symbol was missing caused an error. Now, when a project is deployed, all Global Symbols referenced in the project and not already defined, will be automatically declared on the server with default values. Also the Convertigo Administrator using the console can export symbols to a file and import symbols to another server. Of course, the administrator can edit the symbols values via the Administration console.
Convertigo Studio also benefits of this new functionality. If you import in your Studio a project referencing symbols a popup will ask you if you want to define the symbol or have it created automatically.
Here it is! Asked many times by our users, the Mac and Linux studios are now available!
We support all Windows Functionalities including the HTML connector and Legacy Connector for these two new Studios.
Flash Update is a feature that will change your mobile developer life! No more lengthy builds!
The good news is that Flash Update not only works for development, but it can also for production!
Of course, Flash Update can be disabled, or you can configure your project to have the user to decide if he wants or not the new version.
In previous versions, Push notifications could be integrated using third party components. In 7.1, Push notifications are completely supported for iOS and Android platforms. Push Notifications are implemented on the server side as a simple Sequencer Step. In this way you are free to program the Business Logic suitable for your app to decide the list devices you should notify.
Convertigo handles all the Push notification protocols (Registration, Communication with Push servers, certificate management.) for Apple’s APNS and Google’s GCM.
On the mobile side, Push Management is integrated in the c8o.core client library, so you can receive your notification and handle them in your app. Of course, Push notifications can be received even when the app is not running.
See Technical Blog’s article: Using Convertigo Push Manager
This feature has been implemented to support large J2EE application server environments. Instead of defining you SQL Connector’s parameters such as the jdbc url or the jdbc driver, you can just reference a valid jndi source defined in your application server.
When you edit HTML code for your Mobile application, we support all completion wizard for jQuery mobile or Convertigo Templating Framework keywords.
To help you to use Administration Console, we added links to documentation.
In version 7.1, you are able to configure your build certificate keys on a per project basis. This means that on the same studio, you can have a project using Android signing keys as one publisher and another project using signing keys as another one.
Mobile signing keys are configured directly on the mobile platform objects.
If you prefer not to use the per project signing key feature, you can globally configure the signing keys in the administration console.
We enhanced the Convertigo Templating Framework (CTF) functionalities by adding a new “late rendering” feature, enabling template rendering data only when the users tap on an element. This is useful for accordions for example, when in long lists; the data is rendered only when the user taps on the accordion header to be displayed in the opened section.
We also added the possibility to display a given page before waiting for the server response to route to this page. This enhances the global User eXperience as the users see a page transition before the server sends back some data.
Most of the Web’s REST/JSON web services are now using oAuth authentication mechanism.
In release 7.1, we updated the HTTP connector to be able to connect to oAuth services. The connector will handle all the oAuth signature mechanism for you.
Also, the HTTP connector now supports NTLM authentication, useful to connect to Microsoft’s IIS server protected resources.
See Technical Blog’s article: Using OAuth with Convertigo HTTP Connector
In many projects, it is mandatory to keep session oriented information. It was possible to have this done in previous versions, but version 7.1 brings two new steps making this process mush easier.
You can use these steps to save and retrieve session oriented data at any time within your Sequences.
In New project Wizard, we added 2 new mobile samples projects:
Open new project’s documentation: Opening a sample project from the Studio
As of Convertigo release 7.1, we updated the whole technical stack.
Convertigo Mobility Platform is now based on Eclipse 4.3 (Kepler), on Tomcat 7, On Java 7, and on JQuery 2.x, jQuery Mobile 1.4.2, PhoneGap 3.3.
This ensures a good underlying technology stack, up-to-date with most enterprise’s requirements.