Evoke Pages using General Details

Evoke Pages - General Details Tab

The General Details Tab in the Pages section of Evoke allows you to define the attributes and top level details of the selected page.

Overall Page details

Created By - This field is automatically populated with the name of the Evoke User that originally created the page
Date Created - This field is automatically populated with the date that the page was originally created
Name - The name of the page as used in Evoke and as will appear in the list of Pages in Page Series
Title - The name of the page that will appear at the top of the page when the App is running
Top Level Division - Evoke page segments can be structured in rows or columns. Top Level division specified the initial segment structure of the page i.e. are segments initially structured in "rows" or "columns". Each Segment can be restructured to contain rows or columns
Notes - A free format information only "notes" field for each page that the Evoke user can use to explain the purpose of the page or other information
Margin top (px) - used to specify the margin between the top edge of the screen and the boundary of the App for this Page. This field is initially populated by the information entered in the Theme and can be redefined here specifically for this page.
Margin bottom (px) - used to specify the margin between the bottom edge of the screen and the boundary of the App for this Page. This field is initially populated by the information entered in the Theme and can be redefined here specifically for this page.
Margin right (px) - used to specify the margin between the right side edge of the screen and the boundary of the App for this Page. This field is initially populated by the information entered in the Theme and can be redefined here specifically for this page.
Margin left (px) - used to specify the margin between the left side edge of the screen and the boundary of the App for this Page. This field is initially populated by the information entered in the Theme and can be redefined here specifically for this page.
Background Type - used to select if a specific background colour, image or watermark is to be used for this page. The options are:.
- Theme Colour - sets the Page background colour to one of the colours added to the custom colour palate in Themes
- Web Colour - sets the Page background colour to the colour that can be selected from the Windows web colour palate
- Image - sets an image at the Page background colour, this can be a) a small image e.g. a watermark, that sits in front of a colour or b) a large image that takes up the whole screen on any device
- Image and theme colour - combination of the Image option above and the Theme Colour option
- Image and web colour - combination of the Image option above and the Web Colour option
Background Theme Colour - (shown if Theme Colour selected above) used to pick the background colour from the Theme Colour palate.
Background Web Colour - (shown if Web Colour selected above) used to pick the web colour - either the Hex Colour Code or the CSS recognisable name e.g. Red.
Background Colour Opacity - (shown if Theme or Web Colour selected above) used to set a transparency level on the colour, this can tone down any colour selected
Background Image - (shown if background image selected above) used to pick the background image - use the "choose" option to select an image from the file explorer on your PC.
Background Image Opacity - (shown if background image selected above) used to set a transparency level on the background image, this can allow the image to appear to be behind the page text, data or other images

Sibling Page Navigation

Sibling Page navigation is used to add an ellipsis menu at the page header level that provides page specific navigation options. Sibling Page Navigation allows the user of the app to move around, between various Pages at the same logical level within the app, without having to navigate back through multiple parent/child pages or main menu navigation.
As many sibling page navigations as required may be added by selecting the "caption" that will appear e.g. "Amend Record" and selecting the page to navigate to if selected. Nudge up and down options allow the order of the captions in the ellipsis menu to be changed. If you wish for the user to be able to return to the original page/screen then a sibling navigation back to the original page also needs to be included.

Page-level actions

Page-level actions are used to set up an actions ellipsis in the page header. These are actions relate to page not individual segments and are generally actions that are implemented via click actions or custom code. Please be aware that the content of the ellipsis is combined with sibling page navigation so the names chosen must be different in sibling page navigation and page-level actions.

Page Level Actions provide the opportunity to hook into the Evoke Click Actions from menu options in the ellipsis placed at the top of each page.

You can have as many page level actions as you wish and each can invoke different click actions.

The elypsis on the Page Level Actions also offers an option for the Expanded/Advanced View of the page level actions.

This pops a new window showing all the click actions that have been defined and offering an option of Access Control.

The "define" button allows you to set up either "User Groups" or "Data" access control on the actions that are defined here.

A detailed description of how to configure access control is available on the configure access control user help page.

Use the visable/not visable option to determine is the action should be visable for a specific user/group of users and the enabled/disabled options to control when this action is active or not for a user or group of users.