Extender scripts and other Orchid modules
Extender scripts can be used to create custom workflow actions and also in conjunction with other Orchid modules, Process Scheduler and Information Manager Notes.
Designing scripts for use in Process Scheduler
Scripts can be run in Process Scheduler Level 1. This can be for time based processing and alerts and if you want to automate a process.
Example: You can use Process Scheduler to automate running integration scripts / scripts to import records.
it is important that such scripts don't display Message boxes as they are not designed to accept user input or display user messages).
You can log the script results for use in Process Scheduler.
Scripts to be run in Information Manager Notes (Extended Notes)
This is a great way to provide additional information on the fly when entering transactions in Sage 300. It can also be used to add more info to some master files, long comments or text fields, without having to create a custom table.
You can use an Extender script to generate content on the fly for display within an Info Manager Note. This doesn't create a Note as such, but uses the Notes Tray to display relevant information, driven by the Note's context. You configure such Notes by choosing 'Extender Script' in the I/M Options/ Notes / DML Hotkey Setup and selecting the script.
The Sample scripts are installed in the EBXXA folder when Information Manager is installed. Sample scripts now support the Sage 300 Web Screens.
-
Aging information for a customer, including O/E Pending Orders drill down to the OE Order Entry Screen
-
Customer's credit status, including drill down into the AR Invoices in each ageing period
-
Open orders /backorders for a customer - including drill down to the OE Order Entry Screen
Such scripts are used in conjunction with objects in EB.py, which can be found in the EBXXA folder. E.g. the Sample scripts on the website to run an Extender Script from a Note make use of objects in EB.py. If you were writing your own script to be run from a Note, you would include the EB.py library in order to access the objects in it, allowing you to build the content of the Note on the fly.
Example: If you wanted to display Vendor Aging as Vendor Notes, you could start with the ARAging.py script, and amend it to work with Sage 300 AP.
To force the tray to display when the only configured Note is an Extender script, you need to include eb.showAlertBox() in the script.
This is not included by default in the sample scripts.
For example, in the ARCreditStatus.py script, you can add eb.showAlertBox() at the end of the onRefreshContent() function.
Save the script, check it in, refresh the tray or restart the Sage desktop and test again.
