Public Access is a feature that pertains to applications that have a Public UI. It allows certain app views to be accessed without authentication. Such Public UIs can be used to create sign-up and intro views for applications. While Public UI views can be accessed anonymously by any user without signing in, normal UIs and views can only be accessed by authenticated users. To configure Public Access, open an app in the App Builder. From the My Apps page, edit...
The User Interface section is where graphical user interfaces are created for an application. A user interface is a way through which most users will interact with an app. Most apps will have a user interface for web (accessed via a web browser like Chrome, typically on a laptop or desktop), and/or a user interface for mobile. However, it is possible to create more user interfaces for an app to meet specific criteria, such as role-specific interfaces. A user interface...
Templates are reusable pieces of text that can use variables to affect their appearance. They can use application data to generate various types of documents such as spreadsheets and emails. Template variables are accessed using special Handlebars Helpers syntax (note the double curly brackets in the example below). To better illustrate how the templates look and function, here’s an example: Hello, dear {{record.name}}! This is an email from {{app.config.companyName}}, writing to let you know of our recent policy changes. {{#if...
App Roles are assigned to app users to allow them to interact with an application. When multiple app roles are defined, one must be selected as the default role. The default role will be automatically assigned to a user when that user is first subscribed to the app. When creating new roles it is sometimes easier to copy an existing role and modify it, especially for applications with many data models. Role names must be unique within an application, and...
A Query fetches information from app data and can perform some simple yet powerful operations. Queries Click > +New Query a new page opens New Query Query Type Query can be selected on two types: Standard Advanced (ASQL) Standard Standard queries are built using the Appivo Query Builder. Queries can optionally use Parameters, which can be defined via user input. Select records of The model is essentially the starting point from which we can select attributes either directly from the...
An action is an instruction that will be executed on the platform when called upon. An Action can only be triggered by a rule but can be associated with several rules so that different triggers can result in the same action being performed. Action Scripts are executed on the server side, as opposed to client-side scripts that can be added to UI elements. More information is available in the Appivo Scripting Guide. Actions Action Types A single action can be used...
Rules and Actions provide a powerful mechanism to make applications dynamic and a simple way of adding logic. The Rules and Actions section contains both rules and actions, which are typically used to model business logic within an app. Rules are the programmatic conditions that must be met to trigger an action. There are a number of actions available such as sending emails or executing scripts. For example, in an ordering-system application we want to send an email to the...
The fundament of any application is a model of the data that it manages. An application can manage many different kinds of data, we call a kind of data a model. A model describes some data entity that your application deals with. If you are accustomed to databases a model is the equivalent of a table or if you're an Excel-user the equivalent is a sheet. Just like a sheet in Excel has cells and database-table has columns an Appivo-model has...
The Logic section contains the data modeling, business logic, and other core components of an application. Models Rules and Actions Actions Queries Roles Templates
Delivering your Appivo app in different languages is an important capability when app users have different primary languages. Using the language features the developer can quickly translate the page content to all the configured languages. If an app contains multiple languages, it will attempt to present end-users with the appropriate translation based on user user preferences or device locale. Screen titles, button labels, menu items and more, can all be translated. If an app does not contain a matching translation...