IIndividualPartyManagementPATCH Apex Interface

The IIndividualPartyManagementPATCH Apex interface provides extensibility for PATCH operations through Apex pre- and post-hooks and GraphQL query customization. Implementations can validate incoming requests, modify query structures, and refine the response to support business-specific retrieval rules while maintaining TMF-compliant behavior.

This interface supports the following hooks.

Update Operation Use Cases

Use Case Hook(s) Description Example Scenarios Benefit
Block Updates to Protected Fields transformRequest Examines and transforms the request before validation and mutation processing. Protected or unauthorized fields can be removed from the update payload before the write occurs. - Remove system-managed identifiers<br>- Prevent clients from changing ownership fields <br>- Strip restricted financial or security attributes <br>- Remove fields that are read-only for the caller's role Protects controlled fields by stripping disallowed values before they can be persisted.
Enforce Value Policies on Update applyCustomValidations Applies organization-specific business rules to proposed field values before the update mutation is built. Invalid updates are rejected with an HTTP 400 response and a clear error message. - Reject invalid lifecycle-state transitions<br>- Enforce permitted ranges or enumerated values <br>- Require dependent fields when status changes <br>- Prevent updates that violate regional policies Stops invalid updates early and preserves business and data integrity.
Add Custom Validation Flags configureDefaultValidations Enables, disables, or adds validation flags for update requests. This allows each organization to define the checks required before an update can proceed. - Require record-existence validation <br>- Enable optimistic concurrency checks <br>- Require version matching <br>- Apply stricter validation to regulated records Supports per-organization update policies without changing the shared update implementation.
Stamp Audit Fields on Update customiseMutationPayload Adds audit and provenance fields to the GraphQL mutation payload before execution. This allows metadata beyond the TMF632 schema to be persisted with the update. - Add lastModifiedBy and lastModifiedAt<br>- Record the source channel or integration<br>- Store a request or correlation ID<br>- Capture the reason for the update Persists provenance and audit information beyond the standard TMF632 data model.
Enrich the Update Response handlePostOperation Processes the mutation result before it is returned to the client. It can add calculated values, derived fields, audit metadata, or information obtained from related systems. - Add a customer health score <br>- Include update audit metadata <br>- Return normalized display values <br>- Add related status or eligibility indicators Delivers a richer, more contextual response without modifying the underlying TMF632 schema.

transformRequest

This hook transforms the request context before processing any operation. It is invoked early in the request lifecycle, allowing implementers to adjust the context for subsequent extensibility hooks.

Hook Method

Map<String, Object> transformRequest(Map<String, Object> context)

Sample Apex Implementation

Prevent updates to familyName.

global class IndividualPatchTransformRequestExt implements comms_apex_ext.IIndividualPartyManagementPATCH {


    global static Map<String, Object> transformRequest(Map<String, Object> context) {
        if (context != null && context.get('requestBody') instanceof Map<String, Object>) {
            Map<String, Object> body = (Map<String, Object>) context.get('requestBody');
            // Business rule: last name changes must go through a separate governance flow.
            body.remove('familyName');
        }
        return context;
    }


    // ... other hooks return null / empty map ...
}


configureDefaultValidations

This hook enables, disables, or modifies the built-in validation rules before they execute.

Hook Method

Map<String, Boolean> configureDefaultValidations(Map<String, Boolean> defaultValidationConfiguration, Map<String, Object> context)

Sample Apex Implementation

Add a custom flag consumed by applyCustomValidations.

global class IndividualPatchConfigValidationsExt implements comms_apex_ext.IIndividualPartyManagementPATCH {


    global static Map<String, Boolean> configureDefaultValidations(
        Map<String, Boolean> defaultValidationConfiguration,
        Map<String, Object> context
    ) {
        Map<String, Boolean> overrides = defaultValidationConfiguration != null
            ? defaultValidationConfiguration.clone()
            : new Map<String, Boolean>();
        overrides.put('emailDomainCheck', true);   // your own flag, read in applyCustomValidations
        return overrides;
    }


    // ... other hooks return null / empty map ...
}

applyCustomValidations

This hook validates custom business logic before retrieving customer record. If validation fails, it rejects the request and returns an error response.

The handler processes return values as follows.

Success:

  • Return a map with validationStatus set to "pass" (case-insensitive).
  • The API request continues normally.
  • Other fields in the map are logged but not used.

Failure:

  • Return a map with validationStatus set to "fail" (case-insensitive).
  • The API request is terminated immediately.
  • Raise a ValidationException containing
    • message: value from validationMessage key (or "Validation failed" by default)
    • details: value from validationDetails key (optional)
  • The client receives an HTTP 400 error response.

Hook Method

Map<String, Object> applyCustomValidations(Map<String, Object> context)

Sample Apex Implementation

Validate the updated email domain.

global class IndividualPatchValidationExt implements comms_apex_ext.IIndividualPartyManagementPATCH {


    global static Map<String, Object> applyCustomValidations(Map<String, Object> context) {
        Map<String, Object> result = new Map<String, Object>();
        if (!(context.get('requestBody') instanceof Map<String, Object>)) {
            return result;
        }
        Map<String, Object> body = (Map<String, Object>) context.get('requestBody');


        if (body.get('contactMedium') instanceof List<Object>) {
            for (Object cmObj : (List<Object>) body.get('contactMedium')) {
                Map<String, Object> cm = (Map<String, Object>) cmObj;
                if ('EmailContactMedium'.equals(cm.get('@type'))) {
                    String email = (String) cm.get('emailAddress');
                    if (email != null && !email.endsWithIgnoreCase('@acme.com')) {
                        result.put('validationStatus', 'fail');
                        result.put('validationMessage',
                            'Email domain not allowed. Individuals must use an @acme.com address.');
                    }
                }
            }
        }
        return result;   // empty => proceed; validationStatus="fail" => HTTP 400
    }


    // ... other hooks return null / empty map ...
}



customiseMutationPayload

This hook modifies the GraphQL query before execution to add fields, filters, or transformations.

Hook Method

Map<String, Object> customiseMutationPayload(Map<String, Object> graphQLAsMap,Map<String, Object> context)

Sample Apex Implementation

Stamp an audit field on update.

global class IndividualPatchCustomMutationExt implements comms_apex_ext.IIndividualPartyManagementPATCH {
    global static Map<String, Object> customiseMutationPayload(
        Map<String, Object> graphQLAsMap,
        Map<String, Object> context
    ) {
        Map<String, Object> node = new Map<String, Object>{
            'path' => 'individualData',
            'addFields' => new Map<String, Object>{
                'Last_API_Update__c' => 'TMF632-PATCH'
            }
        };
        return new Map<String, Object>{
            'nodes' => new List<Object>{ node }
        };
    }
    // ... other hooks return null / empty map ...
}

handlePostOperation

This hook post-processes and transforms the API response after data retrieval.

Hook Method

Map<String, Object> handlePostOperation(Map<String, Object> graphQLQueryResultAsMap, Map<String, Object> constructedTMFResponse, Map<String, Object> context)

Sample Apex Implementation

Enrich the response in place.

global class IndividualPatchEnrichExt implements comms_apex_ext.IIndividualPartyManagementPATCH {


    global static Map<String, Object> handlePostOperation(
        Map<String, Object> graphQLQueryResultAsMap,
        Map<String, Object> constructedTMFResponse,
        Map<String, Object> context
    ) {
        if (constructedTMFResponse != null) {
            constructedTMFResponse.put('updatedBy', UserInfo.getName());
            constructedTMFResponse.put('lastUpdatedAt',
                DateTime.now().format('yyyy-MM-dd\'T\'HH:mm:ss\'Z\''));
        }
        return null;   // keeps the mutated response as the final payload
    }


    // ... other hooks return null / empty map ...
}

Full Implementation Example

Here's a complete sample Apex implementation using all supported hooks.

/**
 * Complete TMF632 Individual (Party Management) PATCH API extension,
 * demonstrating all hooks with business logic.
 */
global class IndividualPartyManagementPATCHExtension implements comms_apex_ext.IIndividualPartyManagementPATCH {


    // Hook 1: prevent familyName updates via the API.
    global static Map<String, Object> transformRequest(Map<String, Object> context) {
        if (context != null && context.get('requestBody') instanceof Map<String, Object>) {
            ((Map<String, Object>) context.get('requestBody')).remove('familyName');
        }
        return context;
    }


    // Hook 2: PATCH has no default validators; keep it that way.
    global static Map<String, Boolean> configureDefaultValidations(
        Map<String, Boolean> defaultValidationConfiguration,
        Map<String, Object> context
    ) {
        return new Map<String, Boolean>();
    }


    // Hook 3: enforce the corporate email domain on update.
    global static Map<String, Object> applyCustomValidations(Map<String, Object> context) {
        Map<String, Object> result = new Map<String, Object>();
        if (context.get('requestBody') instanceof Map<String, Object>) {
            Map<String, Object> body = (Map<String, Object>) context.get('requestBody');
            if (body.get('contactMedium') instanceof List<Object>) {
                for (Object cmObj : (List<Object>) body.get('contactMedium')) {
                    Map<String, Object> cm = (Map<String, Object>) cmObj;
                    if ('EmailContactMedium'.equals(cm.get('@type'))) {
                        String email = (String) cm.get('emailAddress');
                        if (email != null && !email.endsWithIgnoreCase('@acme.com')) {
                            result.put('validationStatus', 'fail');
                            result.put('validationMessage',
                                'Email domain not allowed. Individuals must use an @acme.com address.');
                        }
                    }
                }
            }
        }
        return result;
    }


    // Hook 4: stamp an audit field on update.
    global static Map<String, Object> customiseMutationPayload(
        Map<String, Object> graphQLAsMap,
        Map<String, Object> context
    ) {
        Map<String, Object> node = new Map<String, Object>{
            'path' => 'individualData',
            'addFields' => new Map<String, Object>{ 'Last_API_Update__c' => 'TMF632-PATCH' }
        };
        return new Map<String, Object>{ 'nodes' => new List<Object>{ node } };
    }


    // Hook 5: enrich the response in place.
    global static Map<String, Object> handlePostOperation(
        Map<String, Object> graphQLQueryResultAsMap,
        Map<String, Object> constructedTMFResponse,
        Map<String, Object> context
    ) {
        if (constructedTMFResponse != null) {
            constructedTMFResponse.put('updatedBy', UserInfo.getName());
        }
        return null;
    }
}