Apps (App 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 - please review this link before proceeding to use Evoke. If you want to review the basics of creating business Apps with Evoke they are also available here.
When you select any existing App design and version or start a new App design in Evoke, the screen, shown right, is displayed. In the App section you can set up the following for the selected App:
  • App Startup

  • App Styling

  • Global DataSources

  • Access Control

  • Developer Access

There are a lot of options here for your app design, many users leave these as default values for their first app and return to update them later. That is ok except for the app theme, including the colours and reserved segments. If you do not set up the theme you want before you start to design your app in Evoke you will have to manually change the colours, etc of any segments created prior to the theme being updated. If you are leaving these settings as the default settings for now you can move directly on to the next menu item in Evoke which is Entities.
After reading this user guide section, the best way to understand the options is to try them out in Evoke.
App Startup
The App Startup section allows the App designer to specify what happens after the App is loaded by a user. Most importantly this is where the login page that will be used by the app is defined. If you have created a new app design then a default login page will have been created for you and the details of this filled in here. You can also specify if a login button, other than the default button, is to be used on the login page or if a specific authentication selection is to be run instead of the default. Regardless of if you have a default login page or create your own you will need to have a selection to authenticate the user login account, please refer to the mandatory selections information for more on the Login authentication selection.
In addition, you can select, in the after login tab, if you would like to take the user to a specific page series after they login or request that they make a selection from the menu. Finally, if you would like the App to retreive some related data (Entities related to the Appuser record retrieved by the Login selection), for the user that has logged in i.e. their companies details, etc, so that these can be used immediately, you can specify the related data to be retrieved.

App Styling
  • App Colors

    There are four seperate sections to the App Colours styling section:
    • Standard Colours - a colour palette, allowing you to set the colours of the pre-set Evoke colour palette. Users can select either a web colour (using a colour picker) or a hex code colour number for each pre-defined theme colour. Pre-defined theme colours include Very Light, Light, Medium Light, Medium, Medium Dark, Dark, etc and Highlight colours.

    • Custom Colours - a colour palette, allowing you to set additional colours in a custom Evoke colour palette. Users can select either a web colour (using a colour picker) or a hex code colour number for each additional colour in the custom colour palette.

    • Reserved Region Colours - Allows you to redefine any of the reserved regions in your App e.g. the menu area, data grid, headers, text, loading progress bar, backgrounds, etc to use any of the colours you have set up in your standard or custom colour palettes.

    • Default data segment colour settings - Allows you to redefine any of the default data segment regions in your App e.g. the background/Border, Header background, Header Text. Body text (data and prompts), Buttons, etc to use any of the colours you have set up in your standard or custom colour palettes.

  • Background

  • Used to set a background image or colour for all pages within your App. The following options are available:
    • Style - the options are a) a specificed background image (Image), b) No specific background to be displayed (None) or c) A hex code or recognized web colour name (Web Colour)

    • Image Path - use the choose button to select an image from the "File Explorer" on your Windows PC

    • Animate on Load (checkbox) - check to invoke a zoom animation on the image on the logon (first) page of the app.

    • Stretching Style - how big should the background image be stretched when displayed on larger screens. Unlimited (image will be stretched to fill app window), None (no stretching to be performed (may result in tiling)), 25% through 200% (the maximum automatic image stretch beyond natural size)

    • Transparency - from not transparent, 10% transparent all the way through to completely transparent - this allows the background to be "toned down" and to see images placed behind it

  • General Styling

    Allows two sets of general styling to be applied to the entire app. These settings can be overridden in invividual pages:
    • Cultural overrides - Different device operating systems (i.e. iOS, Android, etc) offer their own specific styles for items such as menus, headers, etc. these are know as device "Cultures". Where possible Evoke Apps will, as default, use these "Cultures" in Evoke apps. Some organizations wish to provide apps with a common "corporate" Culture so that the app will look exactly the same regardless of the device that it is viewed/used on. The check boxes within the "Cultural styling overrides" section will, when checked, force the Culture styles on these different devices to all adopt the Culture style that is set for Windows desktop apps.

    • Default page margins - options to set the top, bottom, left and right margins of an app. These settings will set the distance, in pixels, from the edge of the screen, that the app will be displayed.

  • Menu Styling

  • Used to make style changes to the App menu. The following options are available:
    • Show menu help button (checkbox) - Turns on a special help button "(?)" in your App menu that will allow your App users to access App specific user help (that you are able to set up). If you choose to show the menu help button then you will need to identify if the help button will take you to a) a hidden page series in the App or b) to an external URL where you have created help pages. If you choose URL then you are further able to refine the URL that clicking on the (?) on different pages of your app takes you to. You can insert tokens into the URL - "{pageseries}" and "{page}" - in order to incorporate the current pageseries and the current page name into the URL to create context sensitive help web pages.

    • Show menu footer image (checkbox) - Turns on display of a Logo or corporate message that will appear on the menu bar of your App.

    • Menu image path - use the choose button to select an image from the "File Explorer" on your Windows PC.

    • Menu image width (px) - Sets the width of the menu logo image (the menu area has a maximum width of 300px so this should be 280px or below, any width greater than 300 will be clipped)

    • Menu image height (px) - Sets the height of the menu logo image

    • Menu image opacity - set the menu image opacity. The opacity will normally be very low (i.e. 80% opacity) so that on small screens the image can "float" behind the menu options.

    • Main Menu Text - This text box allows the entry of a new legend to replace "Main Menu" at the top of the App menu.

    • Show main menu title image (Checkbox) - enabled if a small image (icon) is to be displayed before the Main Menu Text legend (see above). If this checkbox is checked then two further options are displayed. Main menu image (white) and Main menu image (darker) - use the choose button to select an image from the "File Explorer" on your Windows PC. These images are to be uploaded in two formats as they are used against a dark and a light background. These images must be fixed sizes: 28px height and 28 pixels width. (if you wish to use double, triple and quadrouple density images to have extra crisp images on different density displays then in addition to the initial image selected, upto three further images can be placed in the same location (Windows folder) as the initial image with the naming convention "initial image name@2x", "initial image name@3x","initial image name@4x" with sizes 56px by 56px, 84px by 84px and 112px by 112px

  • Style Themes

    Lists the themes currently available in your Evoke account. Listed are the "Theme Name" and the "Notes" you will have added to the theme.
    The options in the header elypsis menu and grid row elypsis menu are:
    • Create a new theme from the current app style settings (header elypsis menu)

    • Apply the theme settings to this app (grid row elypsis menu)

    • Update the selected theme with this app's current settings (grid row elypsis menu)

    Clicking on a grid row that lists a theme will take you to a screen that allow you to maintain the styles of an existing theme.

Global DataSources
DataSources are defined in more detail in the Data Sources description. It is possible that you will want some of your datasources to be setup on App load and used throughout your App not just in a single page series. You can set any datasources or refined datasources (see Data Sources) to be global datasources and therefore available at any time throughout your App. Global DataSources are populated via the "Initial Selection" option in the Global datasource definition. Global Data Soures may be re-populated during the normal operation of the App by running a different selecton against the Data Source.

Global datasources should be used either as a) read-only datasources within individual pageseries' or b) if you wish to update/manipulate a global datasource then you should create a pageseries datasource and assign the global datasource to this. Once assigned the two data sources are bound together and updating the pageseries datasource will update the global datasource.

When a new App is created the Global DataSource of "CurrentUser" is added to give the App developer access to the user record of the 'logged in user' throughout the App Design. This Global DataSource is populated with the AppUser record at the time of login in the deployed running app.

The Reserved Entities of Classifications and AppUserGroups can not be included as Global Datasources.

Access Control
The Access control user groups allow you to set up different groups, that you will allocate to each user of your App (e.g. Customer, Manager, Salesteam, Accounts Department, etc). You are then able to use the access control features within evoke to provide completely unique App experiences for each of the user groups. Access control allows you to show/hide different menu options for different groups, show/hide different data or information on pages, follow different paths through the app, etc.
An example of Access control user groups is shown in the image on the right.

Developer Access
When designing or maintaining your App, you may want multiple people to work on the design. In developer access control you can define the developers, that are part of your Evoke account, that you want to a) have full access to your App design and b) access specific versions of your App design.

Version Menu - Evoke Revert or Snapshot Feature
The Evoke Snapshot or Revert feature, accessed from the "Version" menu in the App Settings area of Evoke, offers the opportunity to wind back the version of the App design that you are working on a previous snapshot (copy of the App design) taken automatically by Evoke. Please note that if you "revert" to a previous version of your App deisgn then all subsequent versions of the design (after the point you reverted to) are lost. This is more important if multiple users of working on the same App design as their changes could also be lost.

Whenever a change is made and saved to either:
  • Entity property, Entity selection

  • Page Series

  • Menu node

then Evoke automatically saves a copy of the design, at that point, into its Revert/Snapshots feature.
Snapshot Fields
Available snapshots are accessed via the "revert" option in the version menu in App Settings. The fields displayed are:
  • #    This is simply an internal reference number used by Evoke and may be ignored

  • Reason for snapshot.    A short summary of the area within Evoke that was changed and caused a Snapshot to be taken

  • Date.    This is the date that the snapshot was taken

  • Time.    This is the time that the snapshot was taken

the "Reason for Snapshot" field is editable by you - you can add to this "my own notes or comment regarding the snapshot e.g. before starting new section".

Roll back to Previous Snapshot
To roll back to a previous snapshot of your App Design, simply select the snapshot you want to roll back to and click the "Revert Back To" button at the foot of the screen

Mandatory Selections
It is expected that your App will use a number of Selections, however, the SelectByName Selection that is defined with the AppUser Entity, is Mandatory as it is used by the App Login process.
SelectByName Selection
First, this does not have to be called SelectByName, this is the default name and can be changed in the App Startup section of Evoke for each App. In its simplest form, this selection will access an AppUser File/Table in the backend database and run a simple selection e.g. SELECT WITH LOGINNAME = "[{LoginName}]", where LoginName is the filter argument defined in the Entity Selection definition. More complex options are described in the video.

Mandatory Entities and Selections.