System information

-City (string)
-Age (number)
-Passport (0 if unknown, 1 if no or 2 if yes)
-Married (0 if unknown, 1 if no or 2 if yes)
-Sex (0 if unknown, 1 if no or 2 if yes)
-Robinson (0 if unknown, 1 if no or 2 if yes)
-Address (string)
-Comment (string)
DBF files must contain the following columns (can contain other columns too):
-UNEV: user name
-TEL: phone number
-VAROS: city
-UTCA: address
-ROBIN: robin
-IRSZ: zipcode
At least the landline or mobile phone must contaion a valid entry.
4.9.9. Campaign Clients
For every campaign clients must be assigned. This means loading records from tb_cclient to tb_ccampain_clients. Records from tb_cclient are usually not
modified during the campaign. All modification will be done in tb_ccampain_clients and in tb_ccscript_processing (scrip answers).
tb_ccscript_processing database fields:
id: PK, unique identifier (autoincrement)
campaignid: foreign key pointing to tb_cccampaigns.id
clientid: foreign key pointing to tb_cclient.id
clientname: first characters from tb_cclient.name. (denormalized here for speedup)
datum: client record assigment date
operatorid: last operator who have called this client
aquired: used in automatic calls for record locking. deprecated.
enabled: if 0, than this client will not be called again
calltrycount: number of call attempts
recalltrycount: number of recall attempts
lastfailtype: wich number has failed last time (0=unknown,1=mobile,2=landline)
called: the client has been called successfully
needrecall: 0: no need for recall, 1=recall set manually by the operator, 2=recall automatically due to unhandled incoming call,3=other recall reson, >=4:
already recalled
recalldate: date-time of the next recall attempt
lastcalldate: date-time of the last call attempt (successfully or failed call)