Comprehensive and Detailed Explanation:
OIC's Data Mapper simplifies transformations. Let's evaluate each option:
* Option A: You cannot drag and drop an XSLT flow control statement directly to a target node element.
* True:XSLT flow controls (e.g., <xsl:for-each>) require manual coding in an external editor for advanced mappings. OIC's UI doesn't support dragging these directly; you must export the map, edit the XSLT, and reimport it. This limitation ensures simplicity in the UI while allowing power users flexibility.
* Option B: You can drag and drop a source data element to multiple target node elements.
* True:The mapper allows one-to-many mappings. For example, dragging "CustomerName" from the source to both "BillingName" and "ShippingName" in the target is supported, streamlining repetitive mappings.
* Option C: You cannot drag and drop a source data element to a target node element that is already mapped.
* False:Youcanoverwrite an existing mapping by dragging a new source element to a mapped target, replacing the prior link. This flexibility aids iterative design.
* Option D: You cannot drag and drop an XPath function activity directly to a target node element.
* False:XPath functions (e.g., concat()) can be dragged from the function palette to a target node, applying transformations directly. This enhances usability.
Why A and B:A reflects a UI constraint, and B showcases mapping flexibility, both accurate per OIC's mapper design.
Use Case Example:Mapping "OrderDate" to multiple date Hawkins in a CRM sync, then using current-date() in the mapper, demonstrates B and D's capabilities.