This topic describes the systematic instructions to configure the OBRH configuration for event transformation.

The Party system publishes events in Avro format, embedding the onboard and amend payloads as JSON strings. We must implement specific configurations in the Hub to ensure accurate transformation of JSON payloads and eliminate unnecessary escape characters.

Party supports a variety of events for different onboarding and amendment processes (refer to the Event Guide for details).A consumer may require a tailored transformation for each event type to fit their specific needs. The consumer configuration necessitates that a dedicated transformation be defined for each event.

To achieve this, the following configurations should be completed in the Hub:

Payload Transformation Configuration:

User should define rules for parsing and formatting JSON payloads for each event type. Users must properly handle and remove escape characters.

The Hub correctly configures these transformations to ensure that consumers receive clean, accurately formatted JSON payloads, allowing for seamless data processing and integration across systems. Below is an example for onboard payload transformation.

Description of the illustration edit-transformation.png