Budget: 8000 UAH Deadline: 3 days
Good day.
Regarding the lines and budget - approximately 2-3 working days, starting from 8000 UAH. Unfortunately, 1000 UAH will not cover a proper check of the scripts in 1C UT 11, RDP, and on the TSD itself; it's better not to do this randomly =/
We have worked with UT 11, address warehouses, CRM/ERP, and warehouse automation. With TSD, the logic usually comes down not only to sound but to the correct place in the processing of the scanning event - success, item not found, cell or item control error. More precisely, it is important not just to play a WAV file, but not to slow down the work of the warehouse workers and not to break the standard document logic.
I see the implementation plan as follows - to create a separate mechanism for sound events in 1C, preferably through an extension, if your configuration allows it. For each type of scanning result - its own event code and its own sound file. We will check playback specifically through RDP on Zebra, as this is a key nuance. In the future, new types of signals can be added without reworking the entire logic.
Questions before a precise estimate:
> Are your modifications to UT 11 done through extensions or has the main configuration been changed?
> Is sound currently played back stably in the RDP session on Zebra, for example, the system WAV or any test file?
Similar cases from Ingello:
> https://business.ingello.com/forma-wms - WMS and warehouse logic, close to address warehouse and warehouse operations
> https://business.ingello.com/forma-bpm - automation of business processes, control of operations and error scenarios
> https://systems-fl.ingello.com/ua - main page of Ingello Systems for projects on the exchange
In this task, I would start with a short technical check of RDP sound and the place where your scanning is processed. Measure seven times - cut once, because in 1C, warehouse details like to present themselves as simple, and then heroically consume time.