Smart Devices Versioning DetailsOfficial Content

Due to the architecture of the Smart Device's applications generated with GeneXus, it is possible to update only part of them when changes have to be distributed. This flexibility gives us increased response speed.

The changes we make to the applications could affect the services layer, the metadata and/or other components packaged in the distributed binaries.

This document explains which changes in the Knowledge Base imply certain types of changes in the applications.

Requirements

The following documents must be read first:

Depreciable change - Changes to the service layer without changing its interface

Any change to the services (without changing its interface) can be made without updating the version of the binary sent to the store. Once distributed, they are automatically reflected in the connected applications.

Examples:

  • Changes to the Start or Refresh event of a Smart Devices object.
  • Changes to the REST procedures or REST Data Providers called from SD Objects Actions (everything except for changes to the parm).

Minor change - Changes to the metadata

Any change that affects the application's metadata requires updating the application that is executed on the devices. It can be done with a Minor Change and therefore the binaries sent to the store don’t have to be updated.

The connected applications detect the change, update the metadata and keep on running with its new version.

Examples:

  • New Action (new button). It can even call a new screen/layout.
  • Changes to an Action (changes in parameters of calls to procs).
  • Control is associated with a User Control that is already used in another part of the application in the previous version.
  • Adding or deleting a column to a grid or any field to a screen.
  • Changing a user control theme-class.
  • Enabling/disabling Caching.
  • Changing the Control property of the Dashboard.
  • Changes to Themes.
  • Change to the parm of a REST procedure or REST Data Provider called from SD Objects Actions.

Major change - Changes to other components packaged in the binary

Any change that doesn’t involve the metadata but affects the binaries requires a redistribution of the application to the store.

Examples:

  • A new image (in Layout, Action, Background, Theme, etc.).
  • A new User Control or External Object (a control starts referencing a User Control that is NOT used in the rest of the application, and therefore is not packaged).
  • Changing the main object (so that instead of a dashboard it is an SD panel).
  • Changing the GeneXus version.

FAQ

  • Q: Is it applicable to both Android and iOS?
    A: It is applicable to iOS, and this is verified when the application is executed or takes focus. In Android, it works only when the application is completely shut down/killed.



Was this page helpful?
What Is This?
Your feedback about this content is important. Let us know what you think.