tmf675-geographic-location-v4-outbound-api

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

1. Update the Salesforce query to include more fields while reading the data from the Salesforce object:
   • salesforce.namespace = {namespace prefix for the Salesforce object}
   • salesforce.soql.premises = {standard SOQL to fetch premise details from Salesforce}
2. Update this DataWeave file to include additional fields in the TMF payload: mule-app/src/main/resources/dwl/post-soql-to-point-mapping-var.dwl
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-oauth-token-common-sub-flow in below files.
   1. For POST - impl-post-geographic-location-flow.xml
   2. For PATCH - impl-patch-geographic-location-flow.xml
   3. For GET - impl-get-geographic-location-flow.xml
   4. For DELETE - impl-delete-geographic-location-flow.xml
2. Update the DataWeave (targetApiParams, TMF payload dwl) to include the Basic Auth header in below files.
   1. For POST - dwl/post-geographic-location-target-api-params-var.dwl
   2. For PATCH - dwl/patch-geographic-location-target-api-params-var.dwl
   3. For GET - dwl/get-geographic-location-target-api-params-var.dwl
   4. For DELETE - dwl/delete-geographic-location-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.