dwilliamsonivsi
Programmer
We are an Integrator and have an interface to our WMS that imports Customers, Vendors, Carriers, Categories, Buyers, Items, POs, and Orders and exports updates to PO, OE, and IM. It does this for Macola 7.5.103F, 7.6.100a, and 7.6.200.
Now we have a customer who has customized Macola libraries (i.e. Macola has coded special libraries for them).
Keep in mind that the Macola EDI will not do all that we need it to do and it does not do it fast enough. So the EDI mechanism is out.
We have already begun development on a Macola screen scraping client to address this custom Macola installation; however, I would really like to avoid screen scraping. I have heard (and see in the registry) that there are underlying Macola objects (COM or otherwise) that might do the work.
Does anyone know if the Macola GUI is truely dumb and the underlying components do all the work and data checks?
Does anyone know if there is a layer under the GUI that can be used to post transactions against Macola knowing that there are customized Macola libraries that must be called as if an operator were working the GUI?
Now we have a customer who has customized Macola libraries (i.e. Macola has coded special libraries for them).
Keep in mind that the Macola EDI will not do all that we need it to do and it does not do it fast enough. So the EDI mechanism is out.
We have already begun development on a Macola screen scraping client to address this custom Macola installation; however, I would really like to avoid screen scraping. I have heard (and see in the registry) that there are underlying Macola objects (COM or otherwise) that might do the work.
Does anyone know if the Macola GUI is truely dumb and the underlying components do all the work and data checks?
Does anyone know if there is a layer under the GUI that can be used to post transactions against Macola knowing that there are customized Macola libraries that must be called as if an operator were working the GUI?