Adaptiapps SBO V1.3 Sep 2016
Adaptiapps SBO V1.3 Sep 2016
Adaptiapps SBO V1.3 Sep 2016
AdaptiApps Tutorial
Creation and deployment of a four pages User App
using Schneider Electric
Electrics AdaptiApps
Version 1.3 Rev 1.2
September 2016
SmartStruxure Solution
AdaptiApps Tutorial
Creation and deployment of a four pages User App
using Schneider Electrics AdaptiApps
Version 1.3 Rev 1.2
September 2016
Copyright 2016 Schneider Electric. All rights reserved.
The Schneider Electric brand and any registered trademarks of Schneider Electric Industries SAS referred to in this guide are the sole property of Schneider
Electric SA and its subsidiaries. They may not be used for any purpose without the owner's permission, given in writing. This guide and its content are
protected, within the meaning of the French intellectual property code (Code de la proprit intellectuelle franais, referred to hereafter as "the Code"), under
the laws of copyright covering texts, drawings and models, as well as by trademark law. You agree not to reproduce, other than for your own personal, non-
commercial use as defined in the Code, all or part of this guide on any medium whatsoever without Schneider Electric's permission, given in writing. You also
agree not to establish any hypertext links to this guide or its content. Schneider Electric does not grant any right or license for the personal and non-
commercial use of the guide or its content, except for a non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are reserved.
Trademarks and registered trademarks are the property of their respective owners.
Contents
Getting Started
1 Introduction ................................................................. 11
1.1 Requirements ............................................................................. 13
1.2 Tutorial on-line equipment ........................................................... 15
3 Licensing ..................................................................... 35
3.1 Licensing .................................................................................... 37
3.1.1 Design license .......................................................................... 37
3.1.2 Deployment license ................................................................... 37
Design
4 User Apps .................................................................... 41
4.1 User App Design ......................................................................... 43
4.2 User App creation ....................................................................... 47
4.3 Global Variables .......................................................................... 51
4.3.1 Default Global Variables ............................................................ 52
4.4 Page settings .............................................................................. 54
4.5 Navigation settings ...................................................................... 59
4.6 Widgets settings ......................................................................... 63
4.7 Widgets binding (static configuration) .......................................... 65
4.8 Widgets graphical tuning ............................................................. 69
4.9 Widgets binding (dynamic configuration) ..................................... 77
4.10 Multimedia Widgets ..................................................................... 78
4.11 User App default configuration settings ....................................... 83
4.12 User App packaging ................................................................... 85
4.13 User App duplication ................................................................... 87
Deployment
Version 1.3 Rev 1.2, September 2016 AdaptiApps Tutorial
5
5 Preparations ................................................................ 91
5.1 User App Deployment ................................................................. 93
5.2 The 3 Deployment Methods ........................................................ 97
5.2.1 Managed devices ...................................................................... 97
5.2.2 Bring Your Own Device Generic ............................................. 98
5.2.3 Bring Your Own Device Customized ....................................... 98
5.3 Manual Shell Apps installation .................................................. 100
5.4 Manual Shell Apps Installation for WinPC ................................... 101
5.5 Manual Shell Apps Installation for Mac OS ................................. 102
5.6 Manual Shell Apps Installation for Android (Optional) .................. 103
5.7 Manual Shell Apps Installation for iOS (Test Purposes Only) ....... 104
Appearance
9 User Apps .................................................................. 167
9.1 User App on iPad, Android, WinPC, Mac OS ............................. 169
9.2 Navigation between User Apps ................................................. 172
Appendix
Topics
Requirements
Tutorial on-line equipment
1 Introduction
1.1 Requirements
1.1 Requirements
Design
AdaptiApps Builder/AdaptiApps Manager, version 1.3:
PC or a Mac with XGA (1024x768) resolution minimum
Chrome or Firefox web browser (latest version)
Cookies and Java Script should be authorized
An Internet connection
Operate
Shell App, version 1.3:
iPad iOS7.x / iOS8.x / iOS9.x
iOS7.x / iOS8.x are the official Apple platforms used for System Validation.
Digital Airways certificates have to be trusted manually on iOS9. For more
information, see section 5.7 Manual Shell Apps Installation for iOS (Test
Purposes Only) on page 104.
Android tablet 4.2+
Windows 7 / Windows 8.1 / Windows 10
Mac OS X (Maverick, Yosemite)
Magelis GTU
An Automation Server (AS) or an Enterprise Server (ES) running SmartStruxure,
and/or a Multi Purpose Manager (MPM) running SmartStruxure Lite with
EcoStruxure Web Services (EWS) serve capabilities, having AdaptiApps Smart
Widget installed.
Time aspect
It should take you between 15 and 30 minutes to design and deploy your first User
App pages, depending on what you need to setup/install:
Enterprise / Automation Server
Shell App
Topics
SmartStruxure Lite Server
SmartStruxure Server
Important information about Cyber Security
2 Controllers setup (optional)
2.1 SmartStruxure Lite Server
Note
Only Chrome and Firefox are supported.
If using Internet Explorer (or in rare occasions when network is
very slow with Chrome or Firefox), the EULA doesnt appear as a
popup, but as an horizontal pane at the bottom of the page. In
such cases, EULA cannot be accepted. The only way to move
forward and enter credentials is to reload the page, until the
EULA is displayed as a popup.
10. AdaptiApps data sets are now part of the StruxureWare Building Operation
project.
11. Optional - Setup your own AdaptiApps dataset structure to match your
project architecture.
You can copy and paste each unitary dataset (e.g. Tstat folder) to create your
own dataset (see AdaptiApps Hospital / AdaptiApps Hotel structure demo for
more details).
For more information, see section 10.1 Healthcare demo on page 179.
For more information, see section 10.2 Hotel demo on page 190.
Continued on next page
12. Optional - Bind AdaptiApps dataset variables to your BMS variables using the
Edit Bindings menu.
As AdaptiApps also supports controllers with firmware which were not supporting
HTTPS with Digest Authentication, this tutorial refers to HTTP communication to
avoid any confusion.
Important
In real life User Apps, always use HTTPS communication whenever its possible.
Topics
Licensing
3 Licensing
3.1 Licensing
3.1 Licensing
Licenses are required to design an AdaptiApps User App. Two types of licenses are
needed to deliver a User App to an End User:
Design license
Deployment license
a) Only supported by Managed Device / BYOD Customized deployment method. BYOD Generic
requires an unlimited devices deployment license.
Topics
User App Design
User App creation
Global Variables
Page settings
Navigation settings
Widgets settings
Widgets binding (static configuration)
Widgets graphical tuning
Widgets binding (dynamic configuration)
Multimedia Widgets
User App default configuration settings
User App packaging
User App duplication
4 User Apps
4.1 User App Design
Note
Cookies and JavaScript must be authorized in the Browser.
Note
Only Chrome and Firefox are supported.
If using Internet Explorer (or in rare occasions when network is
very slow with Chrome or Firefox), the EULA doesnt appear as a
popup, but as a horizontal pane at the bottom of the page. In
such cases, EULA cannot be accepted. The only way to move
forward and enter credentials is to reloaded the page, until the
EULA is displayed as a popup.
Important
The time zone for BYOD Customized deployment is set to UTC.
Email addresses are visible until the next Saturday at 10:00 AM EDT,
but can be removed manually for confidentiality reasons.
4. The home page provides links to the latest AdaptiApps resources available on
the Web:
Tutorial (This document)
Apps Widgets and Artwork to customize User Apps
Artworks consists of a set of existing pictures / icons provided by the End
User or designed by Artwork designers. Aesthetic and consistency are
key factors of success of AdaptiApps. It is highly recommended to work
with Artwork designers (internal or external).
SmartStruxure AdaptiApps Smart Widgets
AdaptiApps Builder allows you to Design User Apps and to manage Widgets
library (which will be used for design) for several accounts.
Continued on next page
2. Go to User Apps on the left tab, and then push the Add new User App button.
A valid design license is needed to create a new User App.
3. Enter the name of your User App (e.g. Hello World) and define User App
parameters:
The default logout is 15 minutes (no logout = 0)
Public Kiosk applications don't require credentials and never log out.
The User App icon can be changed by clicking the Choose File button.
Supported format: 90x90, PNG 8
Package name is derived from User App name and doesn't support non-
ASCII characters. If special characters are used in the App name, AdaptiApps
Builder will automatically remove them to create the Package name. It is better
not to use non-ASCII characters in any AdaptiApps field content.
Target: Future use
Tablet is the only format available within AdaptiApps V1.2.x
Skin: Selection of the Widget set skin (when available)
Widgets may support different skins. Skins are just a different graphical
representation of a widget (shape, color, fonts). A demo of the skinning
feature is available by entering Elegant in this field. Some widget
renderings will change to fulfill the Bed Side Panel demo used during the
AdaptiApps Proof of Concept. Skinning, if implemented at the widget
level, is a simple String Field allowing you to use a different set of
graphical assets when drawing the widget on the final device. For more
information, see section 11.3 Widget Skins on page 206.
Version: must be an integer
When creating a new User App, the User App template file is copied (it
contains default icons, Utils functions (access to SBO), Manifest file) and
customized with defined parameters. In order to ease demo, the template
includes a pre-defined global variable SERVERIP set to
http://argentan.digitalairways.com which is one of the AdaptiApps SBO demo
servers.
Continued on next page
Note
Password field is always hidden, so it is not possible to check if the password (the
single one or the global one) is the right one.
Global variables are defined per project and available on each page. Its a way to
create a generic project, which can be configured during the deployment, without
any need of redesign.
A project can have as many global variable values as needed.
Any Widget free format configuration field can use a global variable.
The use of global variables in Widget configuration fields requires a $ character
in front of the global variable name, e.g. $SERVERIP.
Note
$ is a reserved character in the widget configuration panel. It should only be used
along with a global variable. The framework cannot warn about any misuse of the
global variable feature, as global variables are resolved at runtime when the user
application runs on the end user device.
An example, the following configuration will display Room #17 as Widget Text.
3. Select the Design icon to design the content of the Home page.
The displayed size of the page being designed can be changed using the
zoom button located on the lower left portion of the screen.
Editor is another URL, using different technologies. Editor is a HTML5 canvas
allowing the user to position and configure widgets accurately on the page.
Continued on next page
Scrolling allows you to display more Widgets within a page, by defining a wider
design area. In this case, the User App page is a 1280x768 pixels window,
which can be moved on a wider area up to 3000x2000 pixels.
Scrolling option is a convenient way to display options reserved for advanced
users. For example, a lighting page may propose a standard page with
switches and dimmers, and then as an option, brightness and color selection
of bulbs.
Continued on next page
In case of multi-page User App, each page must contain a Navigation Widget,
as it is the only way to navigate through pages (the other possibility is to ask
for development of a specific Navigation Widget).
When adding a new Widget in a page, the Template of the Widget is copied in
the project file and referenced into the page. The Widget Template contains:
Bitmaps
JavaScript
Description File (JSON)
This template becomes an instance of the widget (in analogy with the Object
Oriented Programming language). Its properties may be configured by the
User App Designer.
As User App includes a copy of each Widget, if the Widget Library has been
updated with a new version of a Widget, each instance of the previous version
of the Widget used in a User App must be deleted and replaced by the new
one. In such case, the Widget version used within the App is grayed out (not
relevant anymore).
When the Widget library is updated with a new version of a Widget present in a
User App, the Widget will continue to run as expected, but it will appear
grayed out in the AdaptiApps Builder editor to inform developers that a new
version is available. It is recommended to always use latest version of a
Widget.
Continued on next page
2. Select the Bind option on the left tab, and look at the Information menu on the
right pane.
3. Select Logo (it also works for the Items sections of the menu - see below) in
the information list and configure the menu for all pages by entering the
following information:
If you want to let the User App user go back to the Shell App home page,
to let him select another App, then select exit in the Navigate to control.
This will allow exiting the User App by touching the logo during at least 4
seconds.
If you want to redirect the User App user directly to another User App,
then set <packageID> in the Navigate to App control (where
<packageID> is the ID of the End User package, e.g. com.se.MyApp.)
This will allow moving to another User App by touching the logo during at
least 4 seconds.
All User Apps parts of the Navigate to App configuration must be
deployed on Shell App.
User App identified by <packageID> must be installed on the final device.
If it is not installed, then the icon allowing navigation from one User App to
another User App is grayed out on the final device and the indicated
action cannot be performed.
Continued on next page
4. Select Items in the information list and configure the menu for all pages by
entering the following information:
items: Page 0
Navigate to: Home (name of the Page)
Text: Comfort
Icon menu can also be changed. There are 2 icons per menu item (selected /
unselected):
Off icon: Temperature_Unselected_150x150.png
On icon: Temperature_Selected_150x150.png
The selected state of an item corresponds to the touch action.
Items are the different navigation icons (after logo) of the navigation bar, sorted
from Top to Bottom is landscape mode, and from Left to Right in Portrait
mode.
By default there are 2 items available:
Page 0 - the first
Page 1 - the second
Page 2 -
The user needs to manually add as many items as there are pages in the User
App, by using the Add icon.
While adding item, the number is incremented. With 2 Pages, the last item is
Page 1. With 10 Pages, the last item is Page 9.
2. Select the RoomControllerSetPoint Widget and select the Bind option on the
left tab.
In the Information list, you should find 2 menus (Data Sources / Data Access)
to describe how to connect to Automation Server / Enterprise Server:
Data Sources includes URL and path to the data set.
Data Access includes EWS End Point and credentials.
2. Change refresh rate to 2 seconds to get a good reactivity (eyes driven control).
Refresh rate corresponds to EWS pooling time. Default value for Widgets is set
to 30s in order to avoid decreasing the overall performance of the
SmartStruxure solution system.
Continued on next page
3. Update Data Access (EWS) with EWS End Point / Credentials defined on the
MPM or ES/AS side.
SmartStruxure Lite (MPM):
End Point (EWS): ews
Login (EWS): admin ($EWS_LOGIN should be OK.)
Password (EWS): AdaptiApps1! ($EWS_PWD value should be
updated.)
SmartStruxure (ES/AS):
End Point (EWS): EcoStruxure/DataExchange
Login (EWS): admin ($EWS_LOGIN should be OK using default value.)
Password (EWS): AdaptiApps1! ($EWS_PWD value should be
updated.)
4. Select the Design option on the left tab, rearrange the page, in order to add a
Toggle Button.
2. Select the Graphics item in the Information menu on the right pane.
The format and the size of the graphics can be customized:
Off icon (ic_serv_makeup_118x116.png) is a graphic of 118 pixels width,
116 pixels height, and PNG 8 format.
You can replace it by any customized graphic with same properties.
Select a 118 pixels width, 116 pixels height, PNG 8 format image located
on your PC.
4. Optional - Select the Widget Image you just imported, using the drop-down list
of the On/Off icon.
5. Select the Text item on the Information menu on the right pane.
Enter Room Service (or Taxi optional) in the Name field of the Text item.
6. Select the Data Access (EWS) item on the Information menu on the right pane.
Login (EWS): admin ($EWS_LOGIN should be OK using default value.)
Password (EWS): AdaptiApps1! ($EWS_PWD value should be
updated.)
7. Select the Exit option on the left tab to go back on the User App Designer.
Create a second page:
Push add new Screen button.
Create a Landscape page called FM.
2. Set the background and include menu, and then configure the Navigation
scheme, Icon, and Name.
4. Set the right parameters to access Pelco SARIX IP Camera (Pelco Network
Camera: https://www.pelco.com/fixedip).
Select Data Source and enter:
URL: http://78.217.236.83:82/jpeg.
Note
Port 82 must be accessible through firewall.
To check if a webcam is compatible with the camera widget, put the address
of the IP Camera in a Web Browser on the page displaying the current (static)
image (JPEG image, not streaming flow). If the authentication dialog is the
native browser authenticate form, or if there is no authentication, the camera
widget should work.
Continued on next page
6. To display Schneider Electric Web site, add a new page called Web.
7. Add a menu and configure it, and then add the Navigation scheme, Icon, and
Name.
Background is not needed as the Web Browser will take all the available
space.
8. Select HTML widget.
2. Select List of Variables icon to define the variable used for indirect
addressing ($SERVERIP).
SERVERIP is a default global variable. For more information, see section 4.3
Global Variables on page 51.
Continued on next page
To avoid wasting disk place, the archive previously created has a limited life
time of 3 days. After this delay, the archive must be packaged again, if needed
(e.g. if the archive needs to be imported into another AdaptiApps Manager
account.)
The summary of the User App is displayed in a popup window. It contains the
list of widgets composing the user application. It can be used for
administrative purposes. More important, for debug purposes, it contains a
link (http link) to the archive of the created package. This link is used to import
the User App into the AdaptiApps Manager
You have now finished designing your User App's first pages using AdaptiApps
Builder.
2. Enter the version number of this new version (it must be a number).
Topics
User App Deployment
The 3 Deployment Methods
Manual Shell Apps installation
Manual Shell Apps Installation for WinPC
Manual Shell Apps Installation for Mac OS
Manual Shell Apps Installation for Android (Optional)
Manual Shell Apps Installation for iOS (Test Purposes Only)
5 Preparations
5.1 User App Deployment
Note
Cookies and JavaScript must be authorized in the Browser.
Note
Only Chrome and Firefox are supported.
If using Internet Explorer (or in rare occasions when network is
very slow with Chrome or Firefox), the EULA doesnt appear as a
popup, but as a horizontal pane at the bottom of the page. In
such cases, EULA cannot be accepted. The only way to move
forward and enter credentials is to reloaded the page, until the
EULA is displayed as a popup.
4. The home page provides links to the latest AdaptiApps resources available on
the Web:
Tutorial (This document)
Shell Apps for all supported platforms (iOS, Android, Windows, Mac OS)
Google Play:
https://play.google.com/store/apps/details?id=com.schneiderelectric.adaptiapps.byod.managed
The Exchange:
https://ecobuilding.schneider-electric.com/search#tag/adaptiappshell/tab/documentsm
Devices are managed by System Integrators / Facility Manager who install Shell
App and deploy User App.
Platforms supported:
iOS
Android
MS Windows
Mac OS
Magelis GTU
Google Play:
https://play.google.com/store/apps/details?id=com.schneiderelectric.adaptiapps.byod.generic
User App is pushed to the device thanks to a specific code, linked to the User App.
Differentiation between users is done at the logging time and is managed by local
IT.
Platforms supported:
iOS
Android
Google Play:
https://play.google.com/store/apps/details?id=com.schneiderelectric.adaptiapps.byod.custom
Platforms supported:
iOS
Android
From App Store / Google Play, Shell Apps can be installed on iOS / Android devices
using the standard methods.
In case of WinPC / Mac OS devices (no store available), or for engineering efficiency
reason or test purposes, installation can be done manually. For that reason, Shell
Apps are also available at the following place:
The Home page of AdaptiApps Manager for all supported platforms.
The procedure for manual installation of Shell Apps differs depending on the
platform:
WinPC
For more information, see section 5.4 Manual Shell Apps Installation for
WinPC on page 101.
Mac OS
For more information, see section 5.5 Manual Shell Apps Installation for Mac
OS on page 102.
Android (optional)
For more information, see section 5.6 Manual Shell Apps Installation for
Android (Optional) on page 103.
iOS (for test purposes only)
For more information, see section 5.7 Manual Shell Apps Installation for iOS
(Test Purposes Only) on page 104.
2. Download the Shell App from the on-line resources links (Adapti-M-1.3.1.zip).
3. Unzip this App under your PC account (e.g. C:\Users\Joelde\AdaptiApps-M-
1.3.1).
By unzipping the App under your own directory, you will avoid possible
permission issues.
4. You can now launch the Shell App thanks to Adapti-M.bat file.
If a firewall is configured on the PC, a popup may appear, asking for
confirmation to run this software.
2. Download the Shell App from the on-line resources links (Adapti-M-1.3.1.app).
3. Unzip this App on your Mac.
4. Check that the AdaptiApps icon appears on the Mac workspace.
2. Download the Shell Apps you need (depending on the deployment method
selected) from the on-line resources links (e.g. Adapti-G-1.3.0 for the BYOD
Customized deployment method).
3. Open this apk on your Android device and install it. You can get it as an email
attachment, Google Drive, or Dropbox.
4. Check that the AdaptiApps icon appears on your Android Tablet / Phone
interface.
Note
We do not recommend to use manual installation of iOS Shell App using iFunBox.
APIs available on The Exchange are for demo purposes only and should not be
used in Production. They have a limited life time, and will stop one year after they
have been built. The preferred installation method for iOS Shell App is to
download from App Store.
1. Select Shell App menu in the Home Page to download the latest version of the
Shell App you want to install manually.
2. Download the Shell App you need (depending of the deployment method
selected) from the on-line resources links (e.g. Adapti-C-1.3.1.ipa for the
BYOD Customized deployment method).
3. Download and Install iFunBox Classic (http://www.i-funbox.com) for Windows
or Mac.
4. Install iFunBox (iTune must be installed on PC).
5. Connect your iPad to your PC/Mac using a USB cable.
6. Launch iFunBox on your PC/Mac.
7. Select Managing Data App / Install App.
Continued on next page
As the App does not come from an official Apple repository (e.g. App Store),
iOS may warn that the AdaptiApps Shell App is not a trusted App, but this
does not prevent the App to run.
10. When installing the Shell App using iFunBox for the 1st time on an Apple
device running iOS9, proceed with the following steps to trust the Digital
Airways certificate.
Continued on next page
11. Under iOSs Settings / General / Device Management, tap Digital Airways.
14. The Digital Airways certificate is now trusted on the iOS9 device.
Topics
Devices settings
User App import
Single device declaration (or few devices)
Fleet of devices declaration
On premise deployment (optional)
User App deployment on one or few devices
User App deployment on a fleet of devices
User App management on device
User App removal from devices
6 Managed devices
6.1 Devices settings
Google Play:
https://play.google.com/store/apps/details?id=com.schneiderelectric.adaptiapps.byod.managed
Roles are used to manage permissions between End Users and User
Applications.
Continued on next page
Defining at least 1 role is mandatory for managing Non Public Kiosk User
Apps.
Public Kiosk User Apps doesn't require any Role.
4. Define your role name and description.
5. Select the User option on the left tab then click the Add new User button.
Add a new record:
User belong to Demo Role
Login: joel
Password: joel
6. Select the User Apps option on the left tab then click the Add new User Apps
button.
The last designed User App (for the identical credentials) is proposed.
However it is possible to import any User App (from any account), only by
copying the address of the User App as defined during the packaging
process.
Continued on next page
If the User App is a Public Kiosk App, the Role field is grayed.
Toggle Public Kiosk property on a User App can only be done on the
AdaptiApps Builder tool.
AdaptiApps Manager tool manages User Apps, Users, and fleet of Fix/Mobile
devices.
Any update on the User App side should be performed by the AdaptiApps
Builder.
You have now imported your first User App in the AdaptiApps Manager for
Managed environment.
User Interface ID must be read from the device. It is available on the Welcome
Page of the Shell App.
Continued on next page
2. Enter all of your devices using the Add new Shell Apps button.
2. Select the CSV file (Comma Separated Value) that includes the list of devices
you want to declare.
This User App will display User Interface ID on each device where it has been
deployed and then it will automatically be removed from the Shell App to run
previous User App.
This User App is a good example for a developer who wants to implement the
remove option in a User App (BYOD Generic deployment method).
Multiple User Apps can be selected but only those selected on the current
page will be deployed when Deploy is pressed.
Continued on next page
3. Select the User App you want to Deploy and click the Deploy button.
4. Optional - Change the variable value of User App before deployment by first
selecting the Setting icon of the selected User App.
5. Optional - Change value(s) of variable(s) defined for the User App before
deployment.
If the User App contains several global variables, all of them can be updated
during deployment (Late configuration), to get a customized User App.
In this tutorial we only see how to add new items (User Apps, Profiles,
Devices), but it is of course possible to update or delete each of the items
during the User Application life cycle process.
From a technical point of view, AdaptiApps Manager stores all information in a
database: User, Profile, Shell Apps, User Apps information.
Updated values of User Apps global variables are stored in the AdaptiApps
Manager server database.
You have now deployed your first User App pages using the Managed Deployment
method.
2. Select the CSV file (Comma Separated Value) that includes the list of devices
you want to declare and the specific values for each global variable you want
to customize.
Header must be part of the CSV file
Order of global variables are set in the CSV file header
Global variables not included in the header will use default value
CSV file can contain up to 5000 lines (+ header) to deploy to 5000
devices
The CSV file must have the following format:
DeviceID,ApplicationPackage,ApplicationVersion,<1st Global Variable
name>,<2nd ...>
For example:
DeviceID,ApplicationPackage,ApplicationVersion,SERVERIP,LOGIN,PASSWO
RD
0220-715-48267,com.se.myUserApp,1,http://78.217.236.83,User1,Pass1
0216-189-43427,com.se.myUserApp,1,http://78.217.236.84,User2,Pass2
This example will deploy the User App myUserApp to:
Galaxy Tab 10 device (UIID=0220-715-48267) with:
$SERVERIP=http://78.217.236.83
$LOGIN=User1
$PASSWORD=Pass1
Nexus 7 (UIID=0216-189-43427) with:
$SERVERIP=http://78.217.236.84
$LOGIN=User2
$PASSWORD=Pass2
We recommend creating one CSV file per User App.
Figure: Managed Shell App landing page is displayed without App. No User App is hosted
by the Managed Shell App.
Figure: Managed Shell App landing page is displayed with Apps. Several User Apps in
Kiosk mode are hosted by the Managed Shell App. The user has to select the App to use.
Figure: User App starts automatically. A single User App in Kiosk mode is present in the
Managed Shell App.
Figure: Authentication Window is displayed. At least one User App is present in the
Managed Shell App and requires credentials to run. Note that the User Interface ID is
unique for each device.
2. Click on the Trash icon to remotely remove the User App installed on the
Shell App.
If the Shell App is started, the User App is removed. If the Shell App is not
started, the User App will be removed at the next Shell App launch.
Topics
Devices settings
User App import
User App deployment on device
User App management on device
User App removal from devices
7 Bring Your Own Device Generic (BYOD Generic)
7.1 Devices settings
Google Play:
https://play.google.com/store/apps/details?id=com.schneiderelectric.adaptiapps.byod.generic
2. Select the User Apps option on the left tab and then click the Add new User
Apps button.
The last designed User App (for the identical credential) is proposed. However,
it is possible to import any User Apps (from any account), by copying the
address of the User App as defined during the packaging process.
Continued on next page
3. User App ID is associated to a User App during the initial import in the
AdaptiApps Manager.
User App ID (for example, 2q6-qwo-230) is used to get the User App from
the Generic Shell App.
Once the User App has been imported, it can be re-imported in the
AdaptiApps Manager (to take in account modifications done in the Builder)
without changing the User App ID. If the User App is deleted from the
AdaptiApps Manager, then, in case of new import in the AdaptiApps Manager,
a new User App ID will be generated (different from the previous one).
Continued on next page
4. User App Settings allow you to change the Global Variable linked to the User
App ID.
If you have removed a User App from the AdaptiApps Manager, and you have
already setup all your QR-Codes, contact support using
[email protected] to link new imported User App to
previous User App ID.
Continued on next page
You have now deployed your first User App pages using BYOD Generic
environment.
Figure: Generic Shell App landing page is displayed. No User App is hosted by the
Generic Shell App. A User App ID must be entered to get a User App.
Figure: List of User Apps is displayed. Several User Apps are hosted by the Generic Shell
App. Users select the one they want to use.
Figure: User App starts automatically. A single User App is present in Generic Shell App.
Topics
Devices settings
User App import
User App deployment on device
User App management on device
User App removal from devices
8 Bring Your Own Device Customized (BYOD Customized)
8.1 Devices settings
Google Play:
https://play.google.com/store/apps/details?id=com.schneiderelectric.adaptiapps.byod.custom
2. Select the User Apps option on the left tab and then click the Add new User
Apps button.
The last designed User App (for the identical credentials) is proposed.
However, it is possible to import any User Apps (from any account), only by
copying the address of the User App as defined during the packaging
process.
Continued on next page
4. Select the Guest option on the left tab then click the Add new Guest button.
Add a new record:
Name: Joel Desire
eMail: [email protected]
Date In / Date Out (24h format): 2016/03/07 12:00 / 2016/03/08
12:00
This is the period of time when User App will be available from the Shell
App.
When using the Customized method during test deployment, it may be that
you deploy a unique User App (e.g. Hello World), whatever the version, from
several AdaptiApps accounts using a single email address (e.g.
[email protected]). In that case, you may observe
some unexpected behaviors:
User App deployment is not performed
User App removal is not performed
These issues might be related to inconsistencies with regards to the Date In /
Date Out parameters of the different accounts using the same email address.
You can deploy the same application using the same email address from 2
different accounts, provided that the Date In / Date Out parameters do not
overlap. But a Guest is not expected to be in 2 different places at the same
time.
Continued on next page
8. Once Guest is set in the system, email can be sent by selecting the Letter icon
.
The user will be prompted to select User App and Global Variables.
You have now deployed your first User App in the AdaptiApps Manager for BYOD
Customized environment.
Note
If no email arrives, check that it has not been considered as a spam
email by your email server.
2. Get the Customized User App by clicking on the URL link embedded in the
email.
An intermediate page containing the link of the Customized App will open for a
few seconds and automatically launch Adapti-C Shell App with the
Customized User App. (For iOS, users are asked to confirm the action.)
The email allows deployment of one User App. Once the User App is
deployed, the deployment token expires. If the user wants the App on several
devices, he needs to get one email per device.
The Customized User App link is valid only within the allowed time interval for
this User App and it is customized for the user (due to the use of Global
Variables). For example, between Date In (2016/03/03 12:00) and Date Out
(2016/03/06 12:00).
Continued on next page
Through email, you have now retrieved your first User App using the AdaptiApps
BYOD Customized environment.
Figure: List of User Apps are displayed. Several User Apps are hosted by the Customized
Shell App. Users select the one they want to use.
Figure: User App starts automatically. A single User App is present in Customized Shell
App.
It may take up to 30 minutes for the User App to be removed from Shell App. If
you want to remove it as soon as it has been removed from the AdaptiApps
Manager, you have to close and restart the Shell App.
From a User point of view, 30 minutes (or more) should be OK. This long
pooling aims to avoid overloading Manager Server when a large amount of
devices are managed.
Topics
User App on iPad, Android, WinPC, Mac OS
Navigation between User Apps
9 User Apps
9.1 User App on iPad, Android, WinPC, Mac OS
Figure: Hello World User Apps Home page on WinPC / Mac OS device
2. To exit a running User App and return to the Shell App home page, push the
menu's logo during 4s or more (if exit keyword was entered in Navigate to
field Logo of Navigation Widget or any other Navigate to Widget menu item
field).
Continued on next page
3. You can navigate directly from a User App to another User App using
Navigation Widget (logo or items) if Navigate to App control of the Logo
menu or any item of the Navigation Widget has been properly configured.
Navigate to control must be configured with the package name of the User
App.
All User Apps part of the Navigate to App configuration must be deployed on
Shell App.
Topics
Healthcare demo
Hotel demo
10 Ready to use User App project for demonstration purpose
10.1 Healthcare demo
1. Option 1: Deploy the App on your device by importing ready to use Healthcare
User App in Manager and then deploy.
In the AdaptiApps Manager, select the deployment method, then under User
Apps tab, select Add new User App, and replace the proposed URL User App
(the last designed one) by one of the following:
http://adaptiapps.schneider-electric.com/AdaptiApps/Demo/com.se.HealthcareM.zip
2. Option 2: Deploy the App on your device using Adapti-G with QR-Code (User
App ID: rlo-0fl-24f).
4. Make sure to cross the WiFi sign. Your app should be in offline mode, by
default.
Continued on next page
App is using configuration of room 100. You will be directed to Home page,
ready to go.
Continued on next page
Note
The three steps above provide a unique scenario for you to adjust
outdoor temperature, and also prevent users' accidental click. To
edit it again: completely shutting down the app, you'll be able to click
and edit.
Figure: Assistance
Figure: IP Camera
2. Option 2: Deploy the App on your device using Adapti-G with QR-Code (User
App ID: tq5-cdg-248).
Figure: Comfort
Figure: Light
Figure: Tourism
Topics
Widget import in the Widget Library
Widget design
Widget Skins
11 Widget Library, Design Notes, and Skins
11.1 Widget import in the Widget Library
Note
Only Chrome and Firefox are supported.
If using Internet Explorer (or in rare occasions when network is
very slow with Chrome or Firefox), the EULA doesn't appear as a
popup, but as a horizontal pane at the bottom of the page. In
such cases, EULA cannot be accepted. The only way to move
forward and enter credentials is to reload the page, until the
EULA is displayed as a popup.
8. Once the Widget is imported in your environment, it becomes available for all
projects, under Demo category.
Note
When designing (or upgrading) Widgets, its important to change their names, for
maintenance reasons, because Schneider Electric may update the official
AdaptiApps Widgets, and specific changes may be lost.
Figure: Add New User App dialog with Elegant skin selected
Continued
Schneider Electric Skin (Default) Elegant Skin
Figure: Comfort
Figure: Light
Figure: Services
Topics
Supported equipments
Limitations
12 Specifications
12.1 Supported equipments
BMS Controllers
Controller Company Version
Room Controllers
Controller Company Version
Lighting
Lighting Company Website
TV
TV Company
InterCom
InterCom Company WebSite
WebCam
WebCam Company
12.2 Limitations
The following limitations apply to AdaptiApps V1.3.
AdaptiApps Builder limitation:
Number of User Apps per credential: 100
Number of pages per User App: 100
Number of Widgets per page: 10
AdaptiApps Manager Limitation:
Number of User Apps per credential: 100
Number of Shell Apps per credential: 100
Number of User Apps per Shell App: 10
EWS data access:
Number of simultaneous device connections to an Automation Server (AS): 10
Number of simultaneous device connections to an Enterprise Server (ES): 15
Maximum number of variable handles per AS using EWS: 300
Maximum number of variable handles per ES using EWS: 1000
These limitations may vary depending on the refresh rate of Widgets.
Only EWS variables linked to a displayed Widget must be counted.