Similarly to Visual Integrator, button scripts should be able to add a linked script upon it's completion in Sage 100 or any other Sage product that uses a server/client relationship.

If the initial script were to have ran on the client/workstation's machine, the ability for the script to run a server-side script immediately after it's completion should be added.

An example of this would be a client-side script displaying a file browse dialog box for a user to select a file on their local machine. After the script's termination a server-side script could run to have Sage create a new memo and use that file as the attachment.

The reason someone would want to do this instead of just allowing the user to create the memo themselves is because many times users will use the local file path (which is inaccessible to everyone else) as the 'attachment'. So instead, the script will copy the file to a pre-destined location on a file server and create a new MEMO that references the copied file's path to be guaranteed to work. It would also slightly streamline adding documents from the user's perspective as they won't have to go into the memo manager to create a new code.

The script could ensure the memo's code is also standardized to assist with reporting (if a script knows to look for memo codes that are equal to 'CUST-DOC-PO' with a header seq of '9999' because that's how the script would have created the key values for example).

But this is just one example and there could be other potential uses that don't involve file/memo relations.

--------------------------------

One could even argue to just remove the radio buttons altogether (for running script on client vs server) and just have two file path boxes:
1. Script to run on Client
2. Script to run on Server

Then depending on which of the two boxes have a script saved to them would determine if it's a client-only, server-only, or client-then-server button script.

by: Keith D. | over a year ago | General Enhancements