Indicates whether an object is going to be executed online or offline. This property is located under the group "Network" in the properties of all objects mentioned in the Scope below.
This property enables the Offline Native Mobile Applications Generation
| Online |
The object will execute on an online environment communicating with the server via REST services
This is the default value for main Smart Devices objects. |
| Offline |
The object is executed completely offline with no automatic comunication to the server |
| Inherit |
This value is only available for non-Main objects. The value of the property will be inherited from the caller object in runtime. |
This property sets if an object is generated online or offline. When an object is set to execute online, GeneXus will generate REST services in order to make possible the communication between the device and the web server. On the other hand, if the value is set to offline, native code for Smart Devices will be generated in order to execute every action on the device without invoking a REST service on a web server.
When this property is set to Offline in a main Smart Device object, it means two things:
- A local database will be generated in the device.
- A new GeneXus object appears on the Folder View, under the Main Object, the Offline Database object.
When the property value changes in a main Smart Device object from Online to Offline, a Rebuild is needed from the main Smart Device Object to apply the changes and generate the Offline Database object.
As from GeneXus X Evolution 3 RC (codename: Tilo) this property is also available for Procedures and Business Component. This feature makes easier to call Web Services in an offline application, unlike before where using HttpClient was necessary to perform this kind of calls.
For instance, now, calling a Procedure which is exposed as a REST service from an offline application is such as simple as setting the Connectivity Support property of that Procedure to Online. Doing that, every time you call that Procedure from your application, is going to be called via REST services.
- If the Business Component is edited in the layout of some Work With pattern and Work With object object, then the Connectivity Support property of the Business Component is discarded, and the device uses the Connectivity Support property of the WW object instead.
- The Connectivity Support property over Procedures, Data Providers and Business Components works only when these objects are called from Client Events, otherwise the called object inherits the Connectivity Support property value from the caller object. This means, for example, that if an Online Procedure is called from an Offline Procedure, the Online Procedure is called Offline.
This property is availabe as of GeneXus Tilo Beta 1.