📧 Communication Resource Advanced

Direct communication management for specialized scenarios

Communication records store contact methods (email, phone, mobile, fax) for BizEntities, Persons, and Organisations. Most communication management occurs through BizEntity operations. Direct Communication endpoints support bulk imports, cross-entity updates, and contact validation.

4
Endpoints
1
Core DTO
Multiple
Contact Types
3
Entity Links

Usage Notes

When

  • Manage communications independently of BizEntity for bulk imports
  • Query communication records for cross-entity validation
  • Update contact methods across multiple entity associations

Requirements

  • Valid Bearer token with communication permissions

Notes

  • Communications typically created via BizEntity operations; use direct endpoints for specialized scenarios
  • Each communication belongs to exactly ONE entity (BizEntity, Person, or Organisation)
  • Email addresses must be globally unique across the entire platform
  • Phone, mobile, and fax numbers allow duplicates for shared lines

Available Endpoints

Core Operations

GET Get Communications Query with type filtering
POST Create Communication Create with email/phone validation
PUT Update Communication Update maintaining deliverability
DELETE Delete Communication Remove with relationship validation

Core Data Transfer Objects

CommunicationDTO All Communication endpoints Communication structure (10 properties) with multi-channel contact methods (email, phone, mobile, fax), type classification, and entity ownership (BizEntity, Person, Organisation via dual IDs)

Use Cases & Scenarios

Most communication management occurs through BizEntity operations. Use direct Communication endpoints for bulk contact imports, cross-entity updates, email/phone validation services, or CRM data migration scenarios.

→ See BizEntity Overview for standard entity operations

Business Rules & Constraints

BizEntity Integration & Data Integrity

  • Exclusive ownership: One Communication record belongs to ONE entity (BizEntity, Person, OR Organisation)
  • Multiple contact methods: Entities can have multiple communication records for different channels (email, phone, mobile, fax)
  • Communication type validation: All records must reference valid communication type lookup values
  • BizEntity context: Communication creation and management primarily occur through BizEntity operations for relationship integrity

Validation & Compliance Standards

  • Email validation: Requires valid format with domain verification for delivery assurance
  • Phone validation: Supports Australian and international formats with country code validation
  • Data quality: Format validation ensures communication deliverability for regulatory and operational requirements
  • Privacy compliance: Contact information handling compliant with Australian Privacy Principles

Referential Integrity & Management

  • Referential integrity: Cannot delete communication records referenced by active operational workflows
  • Dual ID system: Native IDs for performance, External IDs for third-party system integration
  • External integration: ExternalCommunicationId supports third-party system integration and idempotency