In SAP Cloud Integration, the Content Modifier step allows setting exchange properties, which are key-value pairs stored in the message exchange. Let’s identify supported data types:
Step 1: Exchange Properties- These are temporary variables used within an iFlow, often set via the Content Modifier’s "Exchange Property" tab.
Step 2: Data Type Support- SAP Cloud Integration is Java-based (built on Apache Camel), and exchange properties inherit Java’s type system, though the UI simplifies it.
Step 3: Evaluate Options-
A. java.lang.String: Strings are fully supported for properties (e.g., text values like "123" or "test").
B. java.lang.Integer: Numeric values (e.g., 123) are supported and stored as Integer objects in the underlying Java runtime.
C. java.lang.Char: Single characters aren’t explicitly supported as a distinct type in the Content Modifier UI; you’d use a String of length 1 instead.
D. java.lang.Boolean: While Boolean values (true/false) can be processed in scripts, the Content Modifier doesn’t natively support them as property types—it treats them as Strings.
Step 4: Practical Check- In the Content Modifier, you specify a "Data Type" (e.g., java.lang.String, java.lang.Integer), and these are the most commonly used and documented types.
Step 5: Official Source- The SAP Help Portal’s "Defining Content Modifier" documentation lists java.lang.String and java.lang.Integer as supported types for exchange properties, with no mention of Char or Boolean as distinct options.
Conclusion: Options A and B are the correct answers.References:
SAP Help Portal: "Defining Content Modifier" (SAP Cloud Integration)
SAP Cloud Integration Documentation: "Exchange Properties"
