[Copy] Dual WMS Integration with Different Transport Methods

1. Have you received feedback on how the two different WMS feeds would work in the same environment (sockets, REST.)?

This still goes back to what endpoints they decide. I think they said Sockets and REST. We support REST and REST or Sockets and sockets. We need to get a product enhancement to the Product team for this. I talked to the team and it is possible with maybe some limitations like we will send all messages to the same endpoint. Some sites have multiple endpoints that they want certain messages to go to.

As for how this will work, again this needs to be submitted to the product team if you haven't already. Then we will be able to get something back to them. Most likely treat each site as a CustOwner and REST messages need the CustOwner or site id in the header message. There will be things like this that we will need from them.

UPS Healthcare is transitioning their customers to the Softeon Helix environment, but there will be a time where customers in the same facility will be using different WMS systems and endpoints with the same fleet of bots.

Unable to integrate one fleet to two or more WMS systems with differing transport methods (REST vs Sockets)