We have numerous clients who are using our purchase and payment approval workflow and audit software to help their internal processes using Sage data. An important part of this is creating purchase orders upon approval into Sage 300. Sometimes things happen, though. Information gets entered incorrectly and suddenly, a request to buy 10 boxes of Kleenex is suddenly turned into a PO in Sage for 2 pallets of Kleenex. And the client HAS to get the order placed before 5pm, by FAX< or it's not going to make Bill's day when workers show up But the person with access to Sage is in the middle of a day-long meeting because it's audit time, so that's inconvenient.
Our customers have been using our product for the past quarter century to work with Sage 300 to simply create a revision to the PO, following a tracked process with approval by someone doing it on their device. Nobody gets called out of meetings.
With the latest version of Sage 300 2024's WebAPI, and fit back to later SPs of Sage 300 2023, the process we'd relied on all this time was edited out of the product. This has left some folks with broken process and, in the case of clients with regulatory audit requirements, we foresee this stirring up a hornet's nest of people worried about documenting changes to SOX process. We're already creating POs, please let us provide some method of revising them.
by: Chad B. | about a month ago | SDK
Comments
Bump