Order-Management-Administrator Salesforce Order Management Administrator Accredited Professional (SU24) Questions and Answers

The best way for a user to view the information exchanged between the payment platform and the external payment gateways is to navigate to Payment Gateway Logs related list on the corresponding Order Payment Summary. A Payment Gateway Log is a record that captures the request and response messages between the payment platform and the external payment gateways, such as Stripe, PayPal, etc. A Payment Gateway Log has a lookup relationship to the Order Payment Summary object, which represents a payment made for an order or part of an order. A user can use the Payment Gateway Logs related list on the Order Payment Summary page to view the details of the payment transactions, such as the request and response payloads, status codes, timestamps, etc. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_payment_gateway_log.htm &type=5https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm &type=5

Two objects that are found within Order Management are:

• Fulfillment Order. A Fulfillment Order is a record that represents a group of products in an order that are fulfilled together from the same location. A Fulfillment Order has a lookup relationship to the Order Summary object, and it contains information such as the fulfillment location, delivery method, status, etc.
• Payment Summary. A Payment Summary is a record that represents a payment made for an order or part of an order. A Payment Summary has a lookup relationship to both Order Summary and Invoice objects, and it contains information such as the payment amount, method, status, etc.

Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_fulfillment_order.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_payment_summary.htm &type=5

The correct way for an administrator to allow an org to publish a change set to another org is to open Deployment Settings in the target org, select the environments to allow publishing from and move them to the Enabled list. This creates a deployment connection between the source org and the target org, which allows the source org to upload change sets to the target org. Verified References:https://help.salesforce.com/s/articleView?id=sf.changesets_create_outbound.htm &type=5

Order Allocation should work on Order Items in Awaiting Allocation status. This status indicates that the Order Item has been confirmed by the customer and is ready to be allocated to a Fulfillment Order based on routing rules and inventory availability. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_order_item_status.htm &type=5

The best way for an administrator to quickly examine the relationships between several objects is to go to Schema Builder and check the boxes next to the object names. Schema Builder is a tool that allows administrators to view and modify the data model of their org in a graphical interface. Schema Builder shows the objects and fields in the org, as well as the relationships between them. The administrator can use Schema Builder to select the objects that they want to examine, and see how they are connected to each other. Verified References:https://help.salesforce.com/s/articleView?id=sf.schema_builder.htm &type=5

The object record that the administrator should create in the fault path to notify users of an error is Process Exception. A Process Exception is a record that represents an error or exception that occurred during the order lifecycle, such as payment authorization failure, inventory allocation failure, fulfillment location assignment failure, etc. A Process Exception has a lookup relationship to the Order object, and it contains information such as the exception type, status, message, etc. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_process_exception.htm &type=5

Two ways that this off-platform job can be established without additional third-party tools are:

• Install a minimal set of dev tools on a machine such as the Command Line Interface (CLI) and create appropriate scripts to import files containing the data. The CLI is a tool that allows developers to interact with Salesforce from the command line. The developer can use the CLI to create scripts that use commands such as force:data:bulk:upsert or force:data:tree:import to import data from CSV or JSON files into Salesforce.
• Authorize a machine against the Salesforce org’s APIs with appropriate security measures and create a script to call the APIs. The APIs are interfaces that allow developers to access data and functionality in Salesforce from external systems. The developer can use the APIs, such as REST API or Bulk API, to create a script that authenticates with Salesforce using OAuth 2.0 or JWT, and then performs operations such as insert, update, or delete on Order data.

Verified References: https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_data.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htm

Three things that the administrator can do to get more details for debugging when encountering an unhandled fault error are:

• Create a fault connector. A fault connector is a special type of connector that handles errors that occur in a flow element, such as an assignment, a loop, or an action. A fault connector can route the flow to another element or end the flow with an error message.
• Add a Display Text component which includes {! SFIow.FaultMessage}. A Display Text component is a screen component that displays text on a screen element in a flow. The {! SFIow.FaultMessage} is a system variable that contains information about the error that occurred in the flow, such as the element name, error type, and error message.
• Create an error connector. An error connector is a special type of connector that handles errors that occur in a screen element, such as invalid user input or required fields being left blank. An error connector can route the flow to another screen element or end the flow with an error message.

Verified References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_fault.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screen_component_display_text.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_error.htm &type=5

Three steps that the administrator should take to implement this functionality are:

• Create an External Data Source pointing to the external system’s database. An External Data Source is a type of metadata that defines the connection and authentication information for an external system that stores data outside of Salesforce. The administrator can create an External Data Source using the Lightning Connect OData 2.0 or 4.0 adapters, which support read-only access to data in relational databases.
• Create an External Object for each table of accounting data in the external system. An External Object is a type of custom object that maps to a table in an external system. The administrator can create an External Object for each table of accounting data that they want to access from Salesforce, and define its fields and relationships accordingly.
• Create an Indirect Lookup field to connect to the Account. An Indirect Lookup field is a type of custom field that links a child External Object record to a parent standard or custom object record. The administrator can create an Indirect Lookup field on the External Object that references the Account object, and specify the external column name and value that match the Account ID.

Verified References: https://help.salesforce.com/s/articleView?id=sf.external_object_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.external_object_relationships.htm &type=5

Three steps that the administrator should do to implement this functionality are:

• Create an email template. An email template is a reusable message that contains merge fields that are populated with data from records when the email is sent. The administrator can create an email template for the Payment Summary object that includes information such as the payment amount, date, status, etc.
• Create an email alert action. An email alert action is a type of action that sends an email to one or more recipients when a flow executes. The administrator can create an email alert action that uses the email template created in the previous step and sends it to the owner of the associated account when a new Payment Summary is created.
• Create an approval process on the Payment Summary object. An approval process is a way to automate the approval of records based on certain criteria and actions. The administrator can create an approval process on the Payment Summary object that requires an approval after review from a designated approver.

Verified References: https://help.salesforce.com/s/articleView?id=sf.email_templates_create.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_action_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_creating_approval_processes.htm &type=5

• Use Data Loader. Data Loader is a client application that allows administrators to bulk import or export data from Salesforce using CSV files. The administrator can use Data Loader to import data into Order Management objects, such as Order Summary, Order Item Summary, Fulfillment Order, etc., or export data from these objects for backup or analysis purposes.

Verified References: https://appexchange.salesforce.com/ https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5

The best way for the administrator to meet this requirement is to modify the compact layout on the Credit Memo object. A Credit Memo is a record that represents a refund or credit issued to a customer for an order or part of an order. A Credit Memo has various fields and related lists that display information such as the credit amount, status, reason, etc. A compact layout is a type of layout that determines which fields appear in the highlights panel at the top of a record page in Lightning Experience or Salesforce mobile app. The administrator can use the Object Manager to modify the compact layout on the Credit Memo object and add the Total Amount field to the compact layout. This way, the sales team can see the Total Amount field in the highlights panel at the top of the Credit Memo record page. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_credit_memo.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.compact_layouts_overview.htm &type=5

Three steps that are required when deploying changes via change sets are:

• Create the change set in the sandbox org. This is the first step where the administrator selects the metadata components that they want to deploy and adds them to a change set in the source org, which is usually a sandbox org.
• Upload the change set to the target org. This is the second step where the administrator sends the change set from the source org to the destination org, which is usually a production org or another sandbox org. The administrator needs to have a deployment connection with the target org and permission to upload change sets.
• Deploy the change set in the target org. This is the final step where the administrator validates and deploys the change set in the destination org. The administrator needs to have permission to deploy change sets and resolve any deployment errors or warnings.

Verified References: https://help.salesforce.com/s/articleView?id=sf.changesets_create_outbound.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.changesets_deploy.htm &type=5

The required amount of test code coverage when deploying an Apex class is 75%. This means that at least 75% of the Apex code must be covered by unit tests, and all of those tests must complete successfully. Verified References:https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying_ant_deploy.htm