GoldBox Automation
Click on the thumbnail below to see the full graphic.
The page at the left lists the basic Q-file commands. These make powerful logic
available on their own; and when combined with other GoldBox capabilities, they
can do extraordinarily things.
For example, the Q-file GoTo and Comment statements are restricted to the GoldBox environment, so they
cannot deal directly with GoldMine data conditions. However, we can combine the ability to Delete dBase
files with the ability to Export from GoldMine; and the ability to use the existence/non-existence of a file as
a condition for GoTo logic. Together with GoldBox's MultiTab and/or query capabilities for Exports, this
means that practically any imaginable GoldMine condition can become part of Q-file logic. This makes a
remarkable range of powerful logic available to any Q-file.
And because Q-files can run other Q-files, complex processes can be assembled from relatively simple
building blocks.
In addition, Q-files that are run from GoldBox Views are specially fitted with multi-User capabilities. This
means that each User can, if needed, start a chain of batch processes that are restricted to specific data,
and differentiated by User.
Because of its intimate knowledge of GoldMine; and powerful Q-file capabilities; GoldBox offers you the
best package of batch automation you can get for GoldMine. It can be used to extend or supplant
GoldMine's own Automated Processes. My Query-Driven Automation (QDA) is a far more powerful
alternative to GoldMine's APs; and yet can be used alongside APs, even working cooperatively with them.
I'm offereing a very brief paper that discusses QDA as part of the "Getting" GoldBox series. Please click on
that link, at left.
In addition, I have developed a set of GoldBox Views that facilitate collaboration between client and
consultant when designing a QDA system. To see these, click here.
Finally, QDA implementations typically include Details Tabs populated like those in the screenshot below.
This fully documents the changes made to each Contact by each Automation Action, and suggests the next
likely Action to be taken.
If desired, these standard GoldMine Details can be converted to records that will not display in GoldMine,
but can be displayed via GoldBox Views. This allows for tight control over the Automation History, if needed.


