ComUnity Platform
25.x
25.x
  • ComUnity Technical Overview
  • Getting Started
    • ComUnity Developer Toolkit
      • Login
      • Manage your account: Profile, Settings, and Actions
    • Manage your project
      • Create a project
      • Project Settings
      • General
      • Build and launch your project
      • Templates
      • App Users & Roles
      • Themes
      • Versions
      • Icon Management
      • Store URLs
      • Deploy
        • Environments
        • Manual Project Deployment Across Environments
        • Configuration
    • Organisations
      • Roles and Permissions
      • Organisational Management
      • Teams
  • Toolkit Guides
    • Data
      • Customising the Data Model
      • Manage Entities in the Data Model: Step-by-Step Guide
      • Setting Up Role-Based Permissions for Entities: Access Control Configuration
      • Creating Entity Associations: Configuring Table Links
      • Manage Inheritance in the Data Model: Configuring Entity Hierarchy and Inheritance
    • Screens
      • Integrated Navigation and UI Builder for Screens in the ComUnity Developer Toolkit
      • Building Screens
        • Screen Controls
        • Navigation
          • Lists in Navigation pages
            • Dynamic List Rendering in Navigation pages
            • Adding Sub-Screens to Navigation pages Using List Navigation
          • Page Link
        • Form
          • Screen Controls
          • Lists in Form pages
            • Static Item - List Item
            • Single Item - List Item
            • Entity Items - List Item
    • Custom Classes
    • Custom Website
      • Bindings
      • Pages
        • Page Development
        • Page Elements
        • Templates
        • Resources
    • Communications
      • Configuring Dynamic Action Templates for Event-Driven Communication Channels
        • Event Details: Understanding Data Sources for Dynamic Template Building
        • Email
        • SMS & WhatsApp
        • INAPP
        • Push Notifications
        • HTTP
      • Triggering the Communication Service
      • Communication Settings
    • Events and Notifications Management
    • Observability
      • Client Analytics
      • Metrics
      • Traces
    • Third Party Services
      • Azure Function Apps
      • Azure Logic Apps
      • Integrations
      • Microsoft Fabric
      • APIs
    • Services
      • Media Server
  • General Information
    • Debugging and editing your application code
  • Toolkit Tutorials
    • Build a Simple Blog App: The Beginner's Guide to ComUnity Development
    • Building a Comprehensive News App: Integrating In-App Messaging, Push Notifications, SMS, and Email
    • APIs
      • JSON Placeholder Todos API Integration in a Simple Blog App
      • Countries GraphQL API Integration Using the APIs feature in the Toolkit
      • Integrating the JSONPlaceholder Posts API Using the Toolkit’s OpenAPI Feature
      • OData Integration with the Bookings API Using the APIs feature
    • How to Configure In-App Notifications for User Profile Updates Using Communications
  • Enhancing Cases App: Real-time Comment Notifications
  • Reference articles
    • Glossary
    • Privacy by Design
    • OData
    • Razor
    • CRUD Functions
    • Mustache Templating
    • Temporal Tables
    • Integrating WhatsApp Business with the ComUnity Platform
    • Data Types
    • Field Types
    • Table Links
    • Release Notes
    • Keyboard Shortcuts
Powered by GitBook
On this page
Export as PDF
  1. Toolkit Guides
  2. Screens
  3. Building Screens
  4. Navigation

Page Link

Page Links extend the navigation hierarchy by enabling navigation between Navigation and newly created Form pages. Once a Page Link is created, you have the flexibility to customise it and establish a link to an existing Form page, if desired.

To create a Page Link, follow these steps:

  1. Create or Select a Navigation page: Begin by creating a new navigation page or selecting an existing one that you wish to use.

  2. Integrate a Page Link: Drag and position a Page Link screen control within the Screen Structure at an appropriate location.

  3. Access Page Link Properties: Click on the Page Link element to select it. This action will create a system generated Page and reveal the corresponding properties within the Properties panel.

  4. Configure and Save Properties: Use the Properties panel to tailor the Page Link Properties as per your preferences. Once the configuration is refined, remember to save your adjustments."

Properties of a Page Link

The Page Link properties are used to configure the destination Form page that is linked to the Page Link.

Name This property displays a system-generated name for the destination page. You can change this name to something more meaningful.

Title This property shows the title of the automatically generated Form page linked to the Page Link. You can change this title to something more descriptive.

Layout Type Choose a suitable layout type for your Page Link. The available layout types are:

  • Bar: This layout type displays the destination page contents as a horizontal list item.

  • Card: This layout type displays the destination page contents as a card.

  • Image: This layout type displays the destination page contents as an image.

  • Pie: This layout type displays the destination page contents as a pie chart.

  • PieList: This layout type displays the destination page contents as a list of pie charts.

  • Tab: This layout type displays the destination page contents as a tab.

  • Table: This layout type displays the destination page contents as a table.

Icon

Customise the icon associated with the destination page contents, selecting an appropriate visual representation.

Role Name

Define a role name, if necessary, to control access or permissions related to the destination page contents.

Target URL

The Target URL allows you to specify the OData resource path for the form and must be a collection for an insert and a single record for an update or delete operation.

An example an insert (POST) operation
/Fault
Examples for an update (PUT / PATCH) or delete operation
/Fault(23)
/Fault({{= faultId}}) – where faultId will be replaced with a parameter in the Target URL of the parent navigation item.