Pages - Navigation

The navigation tab, within Pages, is structured into 3 sections:
  • Header actions page navigation

    Header actions page navigation provides the ability to add a menu to the segment header that simply offers navigation to child pages within the same Page Series. If this option is used then the "Header has Actions" checkbox in the Header Tab needs to be checked to show the header menu that contains these actions.


  • Grid row drill-down (child) page navigation

    Grid Row drill-down (child) page navigation provides the ability to add a menu to each grid row that simply offers navigation to child pages within the same Page Series.
    The menu captions are defined (e.g. Account Details in the example on the right) and appear in a separate menu to the grid row actions menu (see below). This can be very useful when used in conjunction with Adaptations.
    In the example shown, see images below, the "click navigation" (Grid row drill-down child navigation) is disabled by an adaptation when the page is loaded as there are three segments at the bottom of the screen that hold the data for accounts and contacts. When the height of the screen is 640px or less the additional navigation menu is displayed (see second image) as the three segments at the bottom of the page are hidden due to a lack of screen real estate.





  • Grid Row Actions menu

    Grid Row Actions provide the opportunity to hook into the Evoke Click Actions from menu options in the ellipsis at the end of each grid row. in the example on the right (above), navigation options such as "Amend Sale" provide a menu option and then, when clicked, invoke the click actions associated with this.
    in the example give (left), these are the processing of:
    • Run selection (to populate the Data Source "AccountsAssignedBy")

    • Retrieve Related Data (to also populate a related entity via a local key or join)

    • Navigate to Child (navigate to a child page with the datasource populated appropriately)

    You can have as many grid grow navigation options as you wish and each can invoke different click actions. The Click actions, in the example given, that have an action id of "*" instead of the Action ID listed in the grid row actions, relate to ALL action id's. Therefore, in the example given the action "RetrieveRelatedData" and "AssigndatasourceValue" are also actioned.
    In the image above right, you will see a checkbox option of "Set current on row actions menu display". If checked this performs the "SetCurrentAsSelectedRow" action for ALL of the Grid Row Navigation Actions in the menu. In this case the first click action in the image on the left would not be required. If you do not wish to "Set Current" for all all the menu actions then leave this unchecked and use the clickaction shown on the left for each Action id that you do want to set current on.
    An example of the grid row and associate action from the completed app appears below.










    The elypsis on the Grid Row Actions Menu offers an option for the Expanded/Advanced View of the custom actions.
    This pops a new window showing all the click actions that have been defined and offering a new 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.