We simply expect our devices to work, anywhere, anytime. Yet many people have discovered and been frustrated by the lack of connectivity in various locations. For some, this is simply an annoyance, but for others, connectivity issues can impact their ability to work. Oil and gas workers, building site workers, park rangers, farmers and other professionals may find themselves disconnected and unable to work effectively. Until now, there weren’t good, affordable solutions. Not everyone can invest in a satellite phone.
For web and mobile CA Plex applications, CM First has a new capability, CM WebClient HSync, which will make it possible for users to store data locally on the device until a signal can be re-established. Application data is stored directly on the device so that people can continue to work when the network isn’t available. This makes your applications ‘always on,’ an increasingly important and desirable capability.
CM WebClient HSync is based on CA Plex and the Sencha Touch framework; it generates a data entry app without an internet connection. It also provides offline validation based on any rules you have established in the CA Plex model, then saves off the data until it can be synchronized with the host database.
CM WebClient HSync meets all the requirements you might have for such a capability:
- Runs on all popular devices
- Performs efficiently
- Stores persistent data on devices
- Allows data entry consistent with CA Plex model definitions
- Customizable for your specific needs
- Fetches and updates data using CA Plex.
CM WebClient HSync uses REST-based web services to communicate between the device and back-end database servers.
The components of HSync include your CA Plex model, template files, the Eclipse workspace, SyncServices servlet and the HSync group model. The latter is composed of Hsync/OfflineApplication, Hsync/TemplateGeneratorEntity, HSync/Ability and HSync/Generator Utilities.
You can set up your CA Plex model with only a few changes. Create an Application Entity to inherit from the OfflineApplication entity then inherit from TemplateGeneratorEntity for each entity you want to include. The Add Application ENT comprises ENT triples and you can use the Inherit from Ability entities to control behavior. You will need to set up the configuration to generate for a Java Client and generate a TemplateGeneration function for each entity being used. CM WebClient Hsync uses meta-code to query model details and creates a UI function to control application generation.
The Generator UI sets properties for generation and starts the generation process:
The HSync templates use tags to control how output is generated, which include attributes, loops, conditions and modifiers.
Here’s an example of a template:
Which will then result in the following output:
As you create more business-oriented apps, you will find the demand increasing for the ability to store data offline. Talk to CM First about how you can exploit CM WebClient HSync to empower your customers.
Did you like this article about “NO CONNECTION, NO PROBLEM” – email us future blog topics to email@example.com