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
  • Environment-Specific Communication Settings
  • Pre-Defined Values
  • Custom Values
  • Project-Specific Communication Settings
  • Channel Priorities
Export as PDF
  1. Toolkit Guides
  2. Communications

Communication Settings

When defining communication events within the Toolkit, it is essential to consider the associated metadata to ensure effective and efficient message delivery. This section delves into two main categories of communication settings: Environment-Specific and Project-Specific Communication Settings. Each of these categories encompasses key aspects such as Channel Priorities, Pre-Defined Values, and Custom Values, which are crucial for configuring communication events to meet specific needs and contexts.

Environment-Specific Communication Settings

Environment-Specific Communication Settings pertain to configurations that vary based on the deployment environment, such as development, testing, staging, or production. These settings ensure that communication events are appropriately configured for the context in which they are executed. To access and manage the metadata associated with these communication events in the Toolkit, navigate to the Configuration section, where you will find detailed instructions on how to set up and adjust these settings. Within this environment-specific context, you can define:

Pre-Defined Values

The Pre-Defined Values section provides access to the InAppRequest Template. This template serves as a predefined structure for specific types of messages or notifications. Utilising predefined values can save time and effort in setting up communication events, offering standardised options for elements such as sender names, email subjects, SMS templates, or push notification content. By leveraging these predefined values, you can maintain consistency across your messages and streamline the configuration process.

Custom Values

The Custom Values section is where you define your @Model.App namespace, which contains constants for your application-level data. Examples of such constants include BaseURL, FromAddress, ToAddress, and PushRootName. Custom Values allow you to personalise and customise your communication events based on specific requirements or preferences. By utilising the @Model.App namespace, you can effectively incorporate application-level data into your templates and messages.

Project-Specific Communication Settings

Project-Specific Communication Settings, on the other hand, are unique to each project within the Toolkit. These settings allow you to define communication parameters that are specific to your project's needs, ensuring that all communication events align with your project's objectives and requirements. To manage these settings, refer to the General section for comprehensive guidelines on accessing and configuring the necessary metadata. Within this project-specific context, you can define:

Channel Priorities

The Channel Priorities field allows you to specify the importance level of a message, ranging from Critical, High, Medium, to Low. By assigning channel priorities, you can ensure that messages are delivered through the preferred channels based on their importance. The default channel priority is set to Medium, but you can adjust it according to your specific communication requirements.