Dynamic Data Exchange
Collect! supports the following Dynamic Data Exchange (DDE) scenario:
Connection
Connect using:
Service: 'collect'
Topic: 'dialer'
Command Line Startup Options
Turn on DDE by using /z in Collect!'s Command Line Startup Options.
Right-click the Collect! icon on your Desktop, choose
Properties, and add the /z option to the Target line.
Example: Target: X:\Collect\bin\collect.exe /z
Ready Indicator
The interaction between Collect! and a Predictive Dialer system
relies on the Collect! session sending out a "Ready" signal when
the collector is available for a call or a "Busy" signal when
the collector is on a call or otherwise unavailable to the dialer.
It is the DDE Request command that manages these "Ready" and "Busy"
signals.
DDE Execute Command
We use the DDE Execute command in the following format.
[ open( debtor,file,FileNumber)]
Where the strings 'open', 'debtor' and 'file' are string
literals, FileNumber is the ASCII representation of the
file number of the Debtor Collect! is to display. Brackets
are used as shown.
Example DDE Execute String: [open(debtor,file,1438)]
The result of this command is that the Debtor screen pops up
and the collector can edit the file. During this time, the DDE
Request commands return the string 'Busy,' as the collector
is handling the call.
When the collector closes the Debtor by clicking OK, Collect!
returns to the Predictive Dialer waiting for file screen. Now the DDE
Request command returns the string 'Ready'.
If the file number is invalid, the collector will receive a message that
the file could not be found in the database. Collect! DDE functions
return a DDE_FACK, to acknowledge receiving the number. An invalid
file number passed via DDE should not occur and indicates a serious
campaign build issue on the predictive dialer side. If a collector were
to see such a message, they should immediately contact their system
administrator.
If the format of the command is incorrect, the DDE return value is
DDE_FNOTPROCESSED. If this error occurs, please check the format of
the Execute command you are sending. This error indicates that the
Predictive dialer software has a problem.
If, for any reason, Collect! is not in the correct state for the DDE
Execute function to succeed, the DDE return value is DDE_FNOTPROCESSED.
The DDE caller should respond by trying again later.
DDE Functions And Callbacks
Collect! uses a limited subset of DDE command to enable predictive dialer links.
DDE Functions
Collect! uses the following DDE functions:
- DDEInitialize - using the following parameters:
- APPCMD_FILTERINITS
- CBF_SKIP_CONNECT_CONFIRMS
- CBF_FAIL_SELFCONNECTIONS
- CBF_FAIL_POKES
DDECreateStringHandle - 'collect'
DdeConnectList - establishes a conversation with all server
applications that support the 'collect' Service and 'collect'
Topic names.
The data format we use is CF_TEXT - i.e. the standard text format.
DDE Commands Supported
Collect!'s responses to the following commands:
XTYP_CONNECT
Returns TRUE.
XTYP_ADVREQ
Returns "Ready" or "Busy".
XTYP_REQUEST
Returns "Ready" or "Busy".
XTYP_ADVSTART
Checks that the format is CF_TEXT and checks if the hszItem
is the same as the application name "collect".
Returns TRUE if the condition fails and FALSE if the condition
succeeds.
XTYP_EXECUTE
If Collect! is busy, it returns DDE_FBUSY.
If it doesn't understand the command/syntax, it returns DDE_FNOTPROCESSED.
If it gets a file number, it returns DDE_FACK.
XTYP_REGISTER
Returns a DdeConnectList, then posts a DDE ADVSTART Transaction.
STYP_DISCONNECT
Returns a FALSE.
See Also
- Introduction To Predictive Dialer
- Command Line Startup Options
- Predictive Dialer Topics
|
Was this page helpful? Do you have any comments on this document? Can we make it better? If so how may we improve this page.
Please click this link to send us your comments: helpinfo@collect.org