Applications
Elements allows the creation of Applications in a multi-tenant format - a suite of applications that communicate with the database across a single shared instance.
Last updated
Elements allows the creation of Applications in a multi-tenant format - a suite of applications that communicate with the database across a single shared instance.
Last updated
Applications define each app that you run on your Elements instance. Elements supports the concept of multi-tenancy, which is the ability to host multiple separate and independent applications from a single shared database of users. For example, , , and Missions are shared across all applications on the instance.
This enables your enterprise to publish a suite of applications under one instance of Elements. Such use cases for multiple applications may include a series of episodic games, separation of production and testing environments, cross promotion and sharing of digital goods, or the ability to publish multiple similar related applications sharing the back end.
Each Application is the nexus for all subordinate configurations. It is even possible to support multiple independent iOS/Google Play Application IDs under one Application within elements. This can be useful if your company implements a strategy of using alternative application IDs for testing or pre-release content.
For Applications, the following restrictions apply:
There is one and only one repository of script code for executing cloud functions.
There is one and only one endpoint for CDN support.
A single Application may not host the same Google Play, iOS, or other unique application identifier.
Application configurations add support for features such as Facebook SSO, Firebase push notifications, and Android and iOS In-App Products. Application configurations are created and configured from inside the Application editor in the console.
Each application has its own set of application configurations, which includes the data connecting it to various services such as push notifications, Facebook, and more.
Product bundles are connected to individual applications via corresponding application configurations. These are used to manage in-app purchases for platforms like iOS and Android.
_id: This is the unique id automatically assigned when the application is created.
name: This is the application's unique name.
description: This string is the application's description.
Applications are managed in the admin console by selecting Applications from the nav bar or the hamburger menu.
Use the "Add Application" button to add a new application.
Applications can be deleted by using the "Delete" button next to them.
Applications can be edited by tapping the "Edit" button for each application.
In the edit panel, you'll also find the URL for the git script repo for the application, as well as links to the API documentation for the application.
Application configurations are also accessed here, but we will cover those in a separate section below.
In the Applications section of the admin console, after having added an application, you are able to add application configurations to that application.
Edit the chosen Application
In the Application Editor, tap the "Add..." button to open the drop down menu
Select the desired application configuration type
