Application Configurator

The App Configurator is a tool that allows you to add a higher level of scalability to the customer's business.

To understand how the Application Configurator acts on the scalability gain we must first understand how it acts on the applications. Its main function is to add devices in the menu structure of the apps. As you switch between devices in a menu, we are changing the dynamic passage of parameters to the on-screen widgets, so that this works well it is necessary that all devices in the same filter pass these parameters on in a standardized way.

The standardization occurs through a code inserted in the menu filter, the structuring of this code occurs in the form of an array where each position corresponds to a device listed in the menu. Each element of this array must have the same pattern of tags, graph parameterization objects, among others, access our documentation on (Menu Filter Structuring) understand in detail and create the json structure that suits your application. If you do not want to create a new filter structure or your user does not have the necessary privileges, it is possible to use the standard platform filter, standard filter details are available in the documentation mentioned above.

The following figure shows the location of the menu filter icon and the listings of its items (a), in the same figure, in b, the json code that illustrates this organization of items, this code is accessible through the "menu settings" option by right clicking on the menu of interest in the edit mode.

Having the desired menu filter structure in hand (mentioned in the previous paragraph), I pass on the json code to the thingable support! that will integrate your code into the platform environment. After completing this step, the App Configurator is ready to use.

The following figure shows an actual use of the Application Configurator:

In Figure 2 we highlight the following points:

1. Associate Device feature,used to add a device to an existing application. When using this feature, a floating menu is shown where you must select the device and application that will be associated.

2. Update List feature, used to update the Results table view where and presented all associations currently in use.

3. Administration feature, if the device used in the association is a Solis gateway, you can access the device administration page through this option.

4. Edit resource, used to change an already performed association.

5. Remove resource, used to remove an already performed association.

When using the Associate Device feature, the device and application association starts in the second piano, a few seconds later and a screen is displayed indicating whether the operation was performed successfully or not (Figure 3), if not, repeat the operation, and the error persists, consult the support of the thingable!.

Note 1: To use the standard platform filter, a menu named Monitoring must exist in the target application, with Filter Type configured as Embedded.

Note 2: To automatically add devices to a map it is necessary to have a menu named Location, on the screen of that menu it is necessary to have at least one map widget with a valid map. If the device linked to the app has the location set, the maps on this screen will automatically receive a marker for the device.

Note 3: When successfully adding a marker to the map for a device, a link to the Monitoring menu of the application will be created in the marker, this menu will be referenced as "Open Details". For this operation to be carried out successfully, it is necessary to have a menu named Monitoring.

Note 4: When successfully adding a marker to the map for a device, it will be created in the access icon (bell) marker for the Alarms menu of the application. For this operation to be carried out successfully, it is necessary to have a menu named Alarms.

Author: Angelo Guimarães

Last updated