Feature Overview

Message Types work by uniquely defining the name and data format (e.g., XML, JSON, EDI, flat files) of each message exchanged in your integration environment. They act as binding points for Search Fields, expressions that extract searchable values from the message payload or context. This enables format-specific processing and accurate correlation. It improves visibility, enforces log view restrictions to relevant teams, and supports automated management via DevOps pipelines.

Precise Content Identification

Message Types identify exactly what kind of data each message contains, allowing system integrations to handle different formats specifically and accurately. This precision improves data quality and relevance in logs. End users benefit because they see only relevant messages, and analysts spend less time wading through irrelevant data.

Enhanced Search and Filtering

By binding Search Fields to specific Message Types, users can perform targeted searches on extracted business values such as invoice numbers or order IDs. It makes troubleshooting and analysis much faster and more accurate. This also means business users no longer need to know which format a message came in, and support teams can correlate flows more efficiently.

Improved Logging and Filtering Accuracy

Each logged message carries its Message Type, which allows filtering and grouping by that type in log views. End users benefit because they see only relevant messages, and analysts spend less time wading through irrelevant data.

Better Governance and Documentation of Payloads

Because Message Types support custom fields and metadata within the repository, you can document owners, lifecycle, versioning and retention for each format. That means stakeholders and auditors can trace not just what data is sent, but how, who owns it, and how it’s managed.