Download Full Version OmniStudio-Developer Salesforce Exam

For a Data Mapper Load, field-level write mappings are configured in the Mapping or Fields area, depending on runtime terminology. The developer must map the input JSON node NewStatus to the Salesforce Case.Status field so the Load action can update the correct object field. Output is associated with returning or shaping extracted/transformed data, not writing input values to Salesforce fields in a Load. Extract is used by Data Mapper Extracts to query Salesforce, not by Load to map updates. Formula is only needed if the Status value must be calculated or transformed before mapping. Salesforce documentation for Data Mapper Load configuration describes adding fields to write data to and configuring mappings for the target Salesforce object.

================

The JSON data structure in option C supports the card layout and follows best practices. It has a list of objects, each representing a product, with the properties “ProductCode”, “ProductName”, “ProductDescription”, and “ProductPrice”. These properties match the fields in the card layout. The JSON data structure also follows the naming convention of using camel case for property names. The JSON data structures in options A and B do not match the fields in the card layout and do not follow the naming convention.

According to the Calculation Matrix Overview page, a Calculation Matrix is “a lookup table that takes an input and returns an output”. In this case, the input is the ProductCode and the output is the Price. The exhibit shows a Calculation Matrix with four rows, each with a different ProductCode and Price. The input given is ProductCode: HRA3320, which matches the second row of the matrix. Therefore, the output is Price: 13.99, which is the value in the same row. 

Integration Procedure is the correct tool because the requirement goes beyond a simple Salesforce record extraction. Complex filtering, sorting, aggregation, orchestration, and preparation should be handled server-side before the OmniScript displays the result. A Data Mapper Extract is appropriate for retrieving Salesforce data, but it is not the best orchestration layer when multiple operations and preparation logic are required. An HTTP Action only calls an external endpoint; it does not by itself manage the full data-preparation workflow. A Set Values Action is useful for assigning values in the OmniScript data JSON, not for complex server-side data shaping. Salesforce describes Integration Procedures as server-side processes used to automate data operations between Salesforce and external systems, which matches this requirement.

================