A New Evoke App (the Default Settings)
When you open Evoke you will be taken to the App Settings area (Apps) and asked to select either a new or existing app design and version. This section of the User Guide explains what default settings are created if you choose to create a New App.
If you are just starting out with Evoke please review the
basics of creating business Apps with Evoke.
Apps
There are a lot of options here for your app design (described in detail in the
App Settings section), many users leave these as default values for their first app and return to update them later.
The default settings you might want to consider are:
-
App Startup - After App Load tab: identifies the Login Page Series (which is one of three default Page Series created with a new app) and provides the default login authentication.
After login tab: identifies the Page Series (also provided with a new app) to send users to when they login.
-
App Styling - Provides several App Themes (default colours and styles for your app) that you can use if you do not want to create a new theme. The default theme for a new app is "Evoke Purple"
-
Global DataSources - A default Global DataSource of "CurrentUser" is provided that provides you with access to the user record of the logged in user throughout the app.
-
Developer Access Control - When you create a new app the default setting is for only yourself (from the list of Evoke users on your Evoke account) to be allowed to access the app.
Each Evoke App has three (3) default
Entities that are included in the New App. These cannot be deleted and must (eventually) be mapped to a database. These are:
-
AppUser Entity
-
AppUserGroup Entity
-
Classification Entity
In addition there is one mandatory database file, EVLU, that is not mapped.
A full description is available regarding the functions and use of the
default Entities.
There is one default Selection added to the AppUser Entity, the SelectByName Selection is set up by default as it is used by the default App Login process.
Menus are obviously a key element of any App and in the Evoke menu builder area you can establish a menu for your app just how you want it to appear.
Two default menu options are set up in a new app. These are:
-
Menu option 1
-
Menu option 2
You can re-use these menu options by renaming them. They are both linked to Default Page series' which can also be reused. Details of how to reuse these and how to further set up your menu options may be found in the
Menus section A
Page Series in Evoke is a discrete area of your app. Each Page Series can have as many Pages (Screens) as you wish. In the Page Series area of Evoke you can add as many Page Series' as you need for your App.
Every "new" app created by Evoke has 3 default Page Series'
You can change the names and other details of these default Page Series' prior to creating a new Page Series if you wish.
The
Repositories area in Evoke is where you define the actual, physical, back end databases that will be accessed and used by the App. These may be via direct access, via stored procedures or through an intermediate API, it is entirely up to you.
Two databases are set up by default in a new Evoke app. These are:
The intention of the two default databases that are provided is to provide an example of how to set up a MultiValue (MVDB) database and a SQL (SQLDB) database.
Both database profiles are set, by default, to have a connection type of {NoDatabase}.
The special connection string ("{NoDatabase}") within your repository definition indicates to Evoke that no repository connection is to be established when the app is generated or runs. This can be useful in the initial phases of app development. Obviously, if you use the {NoDatabase} connection string no repository data will be available to your app, plus, the login page will accept any login name and password.
A single Generator profile called "profile" is included in the
web app area as the default generator profile. Additional profiles can be added if you wish.
The Generator Profile allows you to select from different profiles that define which database which respository objects (files) are associated with. You can add as many generator profiles as you need to define different options for your app.
