Access Journey Apps
The Apps created with MyApps are published in the Cloud4Wi Dashboard and they offer the option to show in the Admin Panel configuration page when they are opened.
This can be used, for example, to create a configuration page of an App but also to create pure back-end applications meant to be displayed on the Admin Panel, such as a reporting dashboard.
The apps shows up in the Apps page under the category configured when initializing the app and also under the Dev tab.
Here, an example of an app (Video Advertising) built with MyApps, that offers a configuration page that can be opened directly from the Cloud4Wi Dashboard.
How it works
The diagram below shows the flow of launching the app from the Cloud4Wi Dashboard.
For example, if your app is hosted on your server on a domain
your app server will receive an HTTP call with the following structure:
There the list of parameters appended to the URL:
- sk: is the session key. This parameter allows you to use the Context APIs to retrieve session context (info about the user, the location etc..)
- tgr: this parameter include some values that represent the step of the Access Journey that invoked the app:
- trOpn: Connect
- trRgt: Sign up
- trPlgn: Log in Attempt
- trLgn: Log in
- trLgt: Disconnect
- false: When not part of the Access Journey
- cburl: this is the econded value of the next step of the Access Journey. You can use this parameter to redirect the user to the next step of the Access Journey
Since Cloud4Wi is a cloud based multi-tenant platform, an App can be installed in different Cloud4Wi Organizations . It is up to the developer to create the logic that allows an app to have different settings on different Organization.
When a Manager opens the app from the Cloud4Wi Dashboard, Cloud4Wi calls the App Server with a session key that allows the retrieval of the Account data (Organization ID, Location ID) so that the app can save different settings per each Account.
Note that all the settings and saved data are the responsibility of the app developer and hosted in the developer's Application Server.