We acquired a customer last year in food service distribution industry. They are on 2016 Adv now being upgraded to 2019 Adv. Their programmer resigned years ago before we were involved but had created custom Javascript programming that runs daily, weekly, monthly jobs through Windows Task Scheduler for purposes mentioned below.
These are mission critical tasks for them involving reporting, exporting, and sending data files and when there's a problem it's usually a semi-urgent call. Our concern is because it requires knowledge of Javascript to fix, we cannot triage the issue with our consulting staff, rather I have to stop what I'm working on. This is OK for the short term but we really want to put them on something easier to support.
*** We were wondering what solutions others use to accomplish the tasks below or what ideas you could share.
Customer has Knowledge Sync already but is used for alerting / emailing purposes only. BUT not sure if K-Sync or Visual CUT can do everything these 15 to 20 Javascripts do.
(Note: the .JS script files themselves run thru Windows Scripting Host - Cscript.exe or Wscript.exe, called as BAT files from unattended Windows Task Scheduler jobs. They run directly from Sage server.)
--------------------------------------------------
1. Create ODBC connections (via ADO) to Sage 100 to read data (instead of BOI - works nicely)
2. Create formatted HTML files that serve as reports for internal staff. They find the files on a network share and dbl-click to open in Chrome or IE to print out and distribute internally. THIS IS THE HARDEST to support.
3. Create Ascii, CSV, and XLS files for vendors, customers and internal staff (XLS output uses Excel object connections).
4. Most Vendor/Customer files sent via FTP and SFTP
5. Some files sent via email instead of FTP / SFTP.
--------------------------------------------------
Types of Issues I've fixed:
a. Scripts stopped half-way due to data files getting larger over time or run during busy time of the day. Fixed by adjusting SQL stmt to run faster OR increasing TIMEOUT values so script doesn't end prematurely.
b. Vendor changed spec and required change in output file format so adjusted the SQL stmt.
c. Vendor changed spec to now require SFTP instead of FTP.
d. Script stopped emailing b/c Gmail SMTP server was used and needed adjustment for TLS 1.2
Type of phone call I would dread to field from them today:
1- Please change the HTML formatting for our reports.
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email:
alnoor@asifocus.comOrange County, CA
------------------------------