Batch Operations / Automation

Batch Operations / Automation

Batch operations enable automation. Here are some examples of GoldBox Batch Operations:

Import -- GoldBox enables import of a wide variety of record types, not just Main Contacts. In addition,
GoldBox offers matching options for updating existing records that farsurpass what's offered by
GoldMine. Also, GoldBox's field level options and huge function library mean GoldBox Imports offer
unparalleled control over the import process. GoldBox Imports can be automated, and can include
multiple passes of the Source file, using a variety of matching options for unsurpassed accuracy. .
Export -- As with Imports, GoldBox offers many more options and capabilities. Among these are the
creation of calculated fields, and export to a filename created via expression. Also, Exports can be
sent to an Excel spreadsheet, beginning at a specified cell . GoldBox Exports can be automated.
Group Building -- Like GoldMine, GoldBox creates new Groups based on Group Name; but there the
similarity ends. When rebuilding an existing Group, GoldBox evaluates every record in its filter or
query; then adds, removes or leaves records in the Group on that basis. GoldMine, by contrast, never
automatically removes records from a Group for any reason. Group Building can be automated with
GoldBox.
Global Replace -- Information that would normally be available only in reports (like the date of the
most recent Successful Call by the assigned User) can be calculated and placed into a User-Defined
field in the Contact record via GoldBox Global Replace operations. Each Setup can perform up to 15
operations, so processing density is high. For another approach to this kind of requirement, see the
GoldBox View SalesManager's Summary. Another common use for Global Replace: data cleaning.
Global Replacements can be automated.
Merge-Purge -- the safest way to combine duped Main Contact records in GoldMine is with GoldBox.
Automating Merge-Purge is accomplished in a special way. First, multiple passes of the database
are run, each with a special, "Safe By Design" matching scheme. Then, to test for possible matches
that cannot be found with "Safe" matching, one or more manually-supervised passes are run, using
riskier matching schemes and GoldBox's Merge-Purge Primer Table. The result is--by far--the safest
and most thorough consolidation of GoldMine Main Contact data that's possible today.
OrgChart Building -- GoldBox's Virtual OrgChart Builder is much faster and generally more flexible
and thorough than creating OrgCharts manually through GoldMine. Also can be automated.
E-mail Bounce Router -- If you send E-mail blasts using GoldMine, you receive bounceback E-mails...
it's inevitable. This utility matches the bouncebacks to the Contact to whom they were originally sent,
as well as doing post processing on Merge Codes, etc. Success rates of over 90% are typical.
GENERAL AUTOMATION -- GoldBox Q-file scripts offer a wide variety of commands that can be used
to control the batch processes, as well as perform sophisticated general automation.

Unlike GoldMine, GoldBox is designed to use

SQL queries

to drive its automation...a far more

powerful approach. It enables us to focus directly on producing desired outcomes based on

underlying Contact data, instead of having to construct an intricate chain of AP Events for each

Contact to get to those outcomes. Whether it's sending letters, scheduling follow-up calls, creating

User reminders, changing Contacts' Type, Status or Owner based on existing data...GoldBox can

handle these reliably and accurately while you sleep. The more complex your requirements, the more

GoldBox

uery-

riven

utomation (

QDA

) outshines GoldMine's APs. GoldBox can even work

cooperatively with existing GoldMine APs, if needed.

And, because GoldBox Views are also based on SQL queries, it's even possible to

use Views as an

intermediate step in building automation

. The exact same queries can be used for either "semi-

automation" (using a View to show you what records will be affected if you proceed with a procedure);

or full automation. Once you are completely satisfied with everything that will happen, just swap out

the View for a Convert to dBase setup; make one or more Q-files to run everything; schedule the

master Q-file to run at the appropriate time via Windows Task Scheduler; and you have full

automation!