BoxWorks WMS Endpoints - additional information for Postman processing

Modified on Fri, 22 Mar, 2024 at 4:01 PM

Cc:



Malleswari Chitturi;



reed;



Savage, Bill;



Green, Frank;



McRae, Mark;



reed

Fri 3/22/2024 11:38 AM

HI Michelle,

I only have the payload for item 100201357 that I extracted from UT. I added it below. I think @Lamar, Christine got the payload from Jared from BW. Can you check it with Jared?

From UT:

{

"ABC": "ETO",

"AGC": "EHSP",

"altItemID1": "041359000020",

"altItemID2": "",

"altItemID3": "20141359000021",

"altItemID4": "",

"altItemID5": "844571511954",

"altItemNumber": "",

"BusinessEventId": "ARM_OutboundInventoryDataBusinessEvent",

"BusinessEventLegalEntity": "hgr",

"canadaHarmonizedCode": "8301.40.6030",

"casesPerPallet": 0,

"ContextRecordSubject": "",

"ControlNumber": 5637476080,

"countryOfOrigin": "ES",

"Description": "HS4 NEO RIMC HSE BLK BLE BLK IP55",

"eachesPerCase": 1,

"EventId": "4D40A0CE-2C29-4C18-AF70-E33C2C7B50D2",

"EventTime": "/Date(1711121084000)/",

"EventTimeIso8601": "2024-03-22T15:24:44.452037Z",

"exportItemDescription": "DOOR LOCKS FOR INTERIOR/EXTERIOR DOORS",

"harmonizedTariff": "8301406030",

"heightCS": 2,

"heightEA": 2,

"HPL": "",

"InitiatingUserAADObjectId": "{D9E7DF02-93E1-41E4-A084-7AB2A7E434F2}",

"inventoryType": "FG",

"ItemId": "100201357",

"lengthCS": 7.75,

"lengthEA": 7.75,

"MajorVersion": 0,

"make": "Purch",

"MessageId": 5637644837,

"MinorVersion": 0,

"ParentContextRecordSubjects": [],

"stdCostPerEA": 175.20,

"StorageType": "R",

"tareWeight": 0.77,

"uomWeightEA": 0.77,

"widthCS": 2.5,

"widthEA": 2.5

}

Joseph Orendain

Senior Systems Analyst

t. (314) 633-2700

From: Michelle Little <michelle@boxworks.com>

Sent: Friday, March 22, 2024 11:26 AM

To: Orendain, Joseph <jorendain@hagerco.com>; Lisa Rohrbach <lmcclure@hagerco.com>; Lamar, Christine <clamar@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>; reed <reed@boxworks.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>; McRae, Mark <mmcrae@hagerco.com>; reed <reed@boxworks.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Good morning.

I don’t think the firewall (or something within Hager setup security-wise) allows us to use Postman to send info to the PROD endpoints either. If you could send me the JSON messages (if you can get them) for each of the items you need to get processed in PROD for Christine, I can then try to do so using Postman.

If that doesn’t work I think I can take what is in the JSON message for each item and create the item manually by hand behind the scenes in the WMS so those items are at least in the WMS system for you all to use.

If you can send me the JSON messages for each item I will see what I can do and then get back with you on how it worked. Sound like a plan?

Thanks,

Michelle

P.S. Your testing on UT for ProductUpdate looks great!!!! =)

From: Orendain, Joseph [mailto:jorendain@hagerco.com]

Sent: Friday, March 22, 2024 11:05 AM

To: michelle <michelle@boxworks.com>; Lisa Rohrbach <lmcclure@hagerco.com>; Lamar, Christine <clamar@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>; reed <reed@boxworks.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>; McRae, Mark <mmcrae@hagerco.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Good morning,

Sorry for the late response, Michelle thanks for this information!

I just tested the productupdate endpoint, to add one of the items that kept on failing in PROD, due to missing cost (ie D365 bug that is not populating the cost) and it worked! That was an easy way to add an item in Boxworks! ? We don’t have access to production endpoint but is there a way for you to process adding items in PROD, as a workaround for now, so that @Lamar, Christine can process item 100201357? (Right now, there are 8 items that kept on failing getting added to Boxworks and D365 is still working to fix it).

Shown below are details of my testing adding item 100201357 in UT environment:

I did the following:

Reset the outbound record in UT for the item.

Capture the payload in Logicapps – I only updated the cost data so it gets added to Boxworks. I kept all field values as is.

Process the payload to postman using the information you provided.

Verified item in Boxwork test

Verified outbound record in UT and status was updated to Closed.

I have not tested the other endpoints yet.

Thanks!

Joseph Orendain

Senior Systems Analyst

t. (314) 633-2700

From: Michelle Little <michelle@boxworks.com>

Sent: Tuesday, March 19, 2024 5:22 PM

To: Lisa Rohrbach <lmcclure@hagerco.com>; Orendain, Joseph <jorendain@hagerco.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>; Lamar, Christine <clamar@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>; reed <reed@boxworks.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Hi Joseph,

Yes, testing should be done using the UT environment which for your BoxWorks WMS system is STL1 or STL2. STL1 (http://10.10.3.87) is your main WMS UT testing server right now and it is the server the D365 test environment is interfaced to.

The urls for the STL1 BoxWorks WMS system endpoints are:

http://10.10.3.87/api/box/MaterialRequest

http://10.10.3.87/api/box/ProductUpdate

http://10.10.3.87/api/box/PutAway

http://10.10.3.87/api/box/Shipment

You don’t need any special configuration to use the above Endpoints:

No Environment variable info needs to be set up.

The only thing that you need is the url of the endpoint you are testing in the POST to area and the JSON message you are testing in the Body. Make sure that Body is set to “raw” and the dropdown is set to JSON and then click the <Send> button. (I literally just tested the below Shipment and it went through just fine to the STL1 server. You can see the response was Successful. And the shipment is now in the WMS STL1 system.)

STL1 WMS Shipment Management screen:

If you have any further questions, please let me know.

Thanks,

Michelle

From: Lisa Rohrbach [mailto:lmcclure@hagerco.com]

Sent: Monday, March 18, 2024 8:36 AM

To: Orendain, Joseph <jorendain@hagerco.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>; michelle <michelle@boxworks.com>; Lamar, Christine <clamar@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Adding Michelle so that you guys can work on this.

From: Orendain, Joseph <jorendain@hagerco.com>

Sent: Monday, March 18, 2024 7:49 AM

To: Lisa Rohrbach <lmcclure@hagerco.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Good morning,

Yes. Yes please.

Thanks!

Joseph Orendain

Senior Systems Analyst

t. (314) 633-2700

From: Lisa Rohrbach <lmcclure@hagerco.com>

Sent: Thursday, March 7, 2024 4:17 PM

To: Orendain, Joseph <jorendain@hagerco.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Joseph,

I assume this testing would be done in UT, right?

I can forward your ask or let you speak with BW. I am not sure I need to be the middle man when it comes to this sort of thing.

From: Orendain, Joseph <jorendain@hagerco.com>

Sent: Thursday, March 7, 2024 10:47 AM

To: Lisa Rohrbach <lmcclure@hagerco.com>; Savage, Bill <bsavage@hagerco.com>; Green, Frank <fgreen@hagerco.com>

Cc: Malleswari Chitturi <mchitturi@hagerco.com>

Subject: RE: BoxWorks WMS Endpoints - additional information for Postman processing

Good morning,

Thanks Lisa for this information but we need more information from them in order test the connectivity in the future. I have added a snip of postman client below and we need information on how to test their endpoints. Basically, when it is setup correctly and completely, when I click the “send” blue bottom, it will send a request to their endpoint and process it in BW. We need following information:

Environment variable information for login credentials, etc.

Parameters, authorization, headers information to process their endpoint.

Payload information that when specified it will create a “test” or dummy transaction on their end. This is to verify that network connection is good.

I understand if we don’t get the information for PROD environment but having UT information is good enough. I assumed when our request gets processed by UT server, connectivity with PROD is also good?

FYI, when we were troubleshooting esker issues before, Harald shared the Esker UT postman configuration to us, and we were able to test the D365 endpoint for adding Esker orders. (I have included a snip of the Esker setup we got below for reference).

Thanks!

Joseph

Postman client we need to setup for Boxworks endpoints:

Esker API setup in Postman: Adding UT Sales Order:

Joseph Orendain

Senior Systems Analyst

t. (314) 633-2700

From: Lisa Rohrbach <lmcclure@hagerco.com>

Sent: Tuesday, March 5, 2024 10:27 AM

To: Orendain, Joseph <jorendain@hagerco.com>; Savage, Bill <bsavage@hagerco.com>

Subject: FW: BoxWorks WMS Endpoints

In case you still want or need these.

From: Michelle Little <michelle@boxworks.com>

Sent: Tuesday, March 5, 2024 10:22 AM

To: Lisa Rohrbach <lmcclure@hagerco.com>

Cc: reed <reed@boxworks.com>; Ron Stoll <rstoll@boxworks.com>

Subject: BoxWorks WMS Endpoints

HI Lisa,

Here are the urls for the Hager-LIVE (i.e. Production server) BoxWorks WMS endpoints:

http://10.20.3.20/api/box/MaterialRequest

http://10.20.3.20/api/box/ProductUpdate

http://10.20.3.20/api/box/PutAway

http://10.20.3.20/api/box/Shipment

Thanks,

Michelle