Inside a CTA Scenario: How I Solved Greens & Veg (Part 2)

Pedro Távora Santos

Follow

20 min read

·

Oct 22, 2025

39

Listen

Share

Part 4 of the “Journey to CTA” series

Press enter or click to view image in full size

This is Part 2 of the Greens & Veg solution walkthrough. Read Part 1 first if you haven’t already, which covers the business context, foundational decisions, system landscape evaluation, and complete data model.

Integration Architecture: The Complete Picture

All integrations flow through an Enterprise Service Bus (ESB) such as Mulesoft providing:

• Protocol conversion (REST, SOAP, EDI, File-based)
• Security enforcement (JWT, mTLS, TLS)
• Orchestration logic
• Retry and error handling

This centralized approach ensures consistent security patterns and simplifies troubleshooting.

Integration I001: Government Permit Verification

Trigger: Supplier Account Status = ‘Visited’ AND Country requires permit verification (stored in Custom Metadata Type)

Pattern: Request-Reply via External Service (Async)

Flow:

1. Record-Triggered Flow detects Account Status change
2. Queries Custom Metadata Type for country requirements