Module 18 Cheat Sheet

MULE FLOW
=========

HTTP Listener
↓
Validate
↓
Set Variable
↓
Transform Message
↓
Salesforce
↓
Transform Response


DATAWEAVE
=========

payload.foo

vars.foo

map

filter

default

as Number

if / else

conditional field


SOQL
====

SELECT Id, Name
FROM Account
WHERE External_ID__c = :id


SALESFORCE
==========

Query
Create
Update
Upsert

Prefer Upsert
when stable External ID exists


ROUTING
=======

Choice
= if / else

For Each
= sequential items

Parallel For Each
= concurrent items

Scatter-Gather
= independent routes


ERROR
=====

Try
On Error Continue
On Error Propagate
Raise Error

Until Successful
= bounded retry


MUNIT
=====

Mock
↓
Set Event
↓
Flow Ref
↓
Assert
↓
Verify Call


HIGH VOLUME
===========

Mule Batch
+
Salesforce Bulk API


INTERVIEW RULE
==============

Exact XML forgotten?

Sketch structure
+
explain semantics.

The most important thing for your interview

You do not need to impersonate someone who has spent five years hand-writing Mule XML.

What you now need to demonstrate is that if they hand you a requirement such as:

“Receive a customer payload, transform it, upsert Account and Contacts in Salesforce, handle Salesforce outages, and test it,”

you can immediately reason:

Listener
↓
validation
↓
preserve original event
↓
DataWeave
↓
Account Upsert by External ID
↓
capture Account ID
↓
Contact transformation
↓
Contact Upsert
↓
normalized response

+ typed error handling
+ bounded/idempotent retries
+ MUnit mocks
+ real-Salesforce integration tests
+ secure externalized configuration
+ CI/CD/observability

At this point, the highest-value next step is no longer another Mule module. It is a 1–2 screen “morning of the interview” cheat sheet covering Modules 1–18, followed by a mock technical interview with short questions where you answer first and I correct/strengthen the answer.