tmf622-product-ordering-management-v4-outbound-api

Add Customized Details to the TMF Payload (POST and NOTIFICATIONS)

To add details to the TMF payload, add transformation logic (DataWeave) on the payload received from the Salesforce inbound API call.

1. For POST, in the impl-post-product-order-flow.xml file, update the dataweave (targetApiParams, TMF payload dwl) before the http-request-internal-common-sub-flow flow reference call.
2. For NOTIFICATIONS, in the impl-post-notification-product-order-event-flow.xml file, update the DataWeave (targetApiParams, TMF payload dwl) before the http-request-internal-common-sub-flow flow reference call.
3. After you are finished making the updates, redeploy the JAR file.

Update the Authentication Type for the External System

As a standard, MuleSoft Direct apps support OAuth authentication for the external system. To update this, you must update the connector in the application. This applies to all methods.

1. Comment out the flow reference call http-fetch-target-system-oauth-token-common-sub-flow. in below files.
   1. For Notification - impl-post-notification-product-order-event-flow.xml
   2. For POST - impl-post-product-order-flow.xml
2. Update the DataWeave (targetApiParams, TMF payload dwl) to include the Basic Auth header in below files.
   1. For Notification - dwl/post-notification-product-order-event-target-api-params-var.dwl
   2. For POST - dwl/post-product-order-target-api-params-var.dwl

From → "Authorization": "Bearer " ++ vars.tokenPayload.access_token
To → "Authorization": "Basic " ++ “Base64 encoded (username):Base64 encoded (password)”

After you are finished making the updates, redeploy the JAR file.