Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Sv translation
languageen

Fields

The individual fields for dialler contacts are documented in the import / export list below.

Importing and Exporting

Importing and Exporting Contacts requires a scheme -see Import Export Schemes for details.

Fields

The following fields are defined:

NameType (Max Length)RequiredContent
dtImportedDATETIME
Date and time of import in the format YYYY-MM-DD HH:mm:SS
DiallerCampaignsNameTEXT (64)
Name of the dialer campaign. Not required during import (the dialler campaign is selected explicitly).
UserDataTEXT (64)
Foreign system key or ID.
ClientTEXT (64)
Client.
ServiceTEXT (64)
Service.
ReferenceNumberTEXT (64)
Reference Number e.g. from the foreign system.
NameTEXT (64)JaSurname.
FirstNameTEXT (64)JaFirst name.
SalutationTEXT (16)
Mr. Mrs. etc.
TitleTEXT (16)
Dr. etc.
CompanyTEXT (64)
Company.
AddressTEXT (64)
Street.
PostalCodeTEXT (10)
Post Code.
CityTEXT (64)
City.
CountryTEXT (64)
Country.
AccountOwnerTEXT (64)
Account owner.
AccountBankTEXT (32)
Bank.
AccountNationalBankCodeTEXT (10)
National bank code.
AccountBICTEXT (11)
BIC.
AccountNumberTEXT (20)
Account number.
AccountIBANTEXT (34)
IBAN.
AmountNUMBER
Amount.
PhoneNumber1TEXT (32)JaTelephone number 1 in E.164 format.
PhoneNumber2TEXT (32)
Telephone number 2 in E.164 format.
PhoneNumber3TEXT (32)
Telephone number 3 in E.164 format.
PhoneNumber4TEXT (32)
Telephone number 4 in E.164 format.
PhoneNumber5TEXT (32)
Telephone number 5 in E.164 format.
PhoneNumber6TEXT (32)
Telephone number 6 in E.164 format.
FaxNumberTEXT (32)
Fax number.
EmailTEXT (32)
Email.
WebsiteTEXT (64)
Website.
CommentTEXT (Unlimited)
Comments
ReservedUsersUIDTEXT (32)
UID of the agent, which has reserved this contact.
FollowUpUsersUIDTEXT (32)
UID of the agent, which owns the follow up appointment or delay.
FollowUpDateTimeDATETIME
Appointment or delay date and time for this contact.
ResultCodesExportKeyTEXT (32)
Export key of the dialler result code.
DoneNUMBER (Empty, 0 or 1)
Result code = done
AbortedNUMBER (Empty, 0 or 1)
Result code = aborted
AppointmentNUMBER (Empty, 0 or 1)
Result code = appointment (in dialler)
DelayNUMBER (Empty, 0 or 1)
Result code = delayed (in dialler)
bPhoneNumber1InvalidNUMBER (Empty, 0 or 1)
Telephone number 1 is invalid (determined by dialler)
bPhoneNumber2InvalidNUMBER (Empty, 0 or 1)
Telephone number 2 is invalid (determined by dialler)
bPhoneNumber3InvalidNUMBER (Empty, 0 or 1)
Telephone number 3 is invalid (determined by dialler)
bPhoneNumber4InvalidNUMBER (Empty, 0 or 1)
Telephone number 4 is invalid (determined by dialler)
bPhoneNumber5InvalidNUMBER (Empty, 0 or 1)  Telephone number 5 is invalid (determined by dialler)
bPhoneNumber6InvalidNUMBER (Empty, 0 or 1)
Telephone number 6 is invalid (determined by dialler)

Example Scheme

An XML example definition is provided here to illustrate the XML Import / Export Scheme definition required for dialler contacts.

Code Block
<importExport2>
    <import>
        <type>CSV</type>
        <encoding>UTF-8</encoding>
        <delimiter>;</delimiter>
    </import>
    <export>
        <type>CSV</type>
        <encoding>UTF-8</encoding>
        <bom>1</bom>
        <delimiter>;</delimiter>
    </export>
    <fieldMappings>
        <fieldMapping internalField="RandomSortOrder" externalField="Priority" externalType="INTEGER" importOnly="true"/>
        <fieldMapping internalField="ReferenceNumber" externalField="RefNumber" externalType="VARCHAR"/>
        <fieldMapping internalField="ExternalSystemLink" externalField="Hyperlink" externalType="VARCHAR"/>
        <fieldMapping internalField="" externalField="EKCODE" externalType="VARCHAR"/>
        <fieldMapping internalField="Salutation" externalField="Sal" externalType="VARCHAR"/>
        <fieldMapping internalField="Name" externalField="Name" externalType="VARCHAR"/>
        <fieldMapping internalField="FirstName" externalField="First" externalType="VARCHAR"/>
        <fieldMapping internalField="Address" externalField="Addr" externalType="VARCHAR"/>
        <fieldMapping internalField="Country" externalField="Country" externalType="VARCHAR"/>
        <fieldMapping internalField="PostalCode" externalField="PostCode" externalType="VARCHAR"/>
        <fieldMapping internalField="City" externalField="City" externalType="VARCHAR"/>
        <fieldMapping internalField="PhoneNumber1" externalField="Tel1" externalType="TEL:49"/>
        <fieldMapping internalField="PhoneNumber2" externalField="Tel2" externalType="TEL:49"/>
        <fieldMapping internalField="Email" externalField="Mail" externalType="VARCHAR"/>
        <fieldMapping internalField="Tag" externalField="DataIdentifier" externalType="VARCHAR"/>
        <fieldMapping internalField="UserData" externalField="CustomerNumber" externalType="VARCHAR"/>
        <fieldMapping internalField="dtBeginDate" externalField="StartDate" externalType="DATETIME:dd.MM.yyyy"/>
        <fieldMapping internalField="dtEndDate" externalField="EndDate" externalType="DATETIME:yyyyMMdd"/>
        <fieldMapping internalField="Client" externalField="ClientName" externalType="VARCHAR"/>
        <fieldMapping internalField="" externalField="NotImported1" externalType="VARCHAR"/>
        <fieldMapping internalField="" externalField="NotImported2" externalType="VARCHAR"/>
        <fieldMapping internalField="" externalField="NotImported2" externalType="VARCHAR"/>
    </fieldMappings>
</importExport2>




Sv translation
languagede

Hinweis

Warning
titleÜberholt ab Release 3.19

Dieses Import / Export Format wird ab release 3.19 nicht mehr weiterentwickelt, und bietet keine Zugriffsmöglichkeiten auf neue Felder und Einstellungen. Anstattdessen sollte Import Export Schemes verwendet werden.

Felder

Die individuellen Felder pro Dialer Kontakt werden in der Tabelle unten beschrieben.

Konventionen

Der Import / Export Format für Dialer Kontakte ist CSV. Die CSV Dateien müssen folgende Konventionen einhalten:

  • CSV Format
  • Jede Zeile beinhaltet ein Datensatz
  • Felder im Datensatz werden durch Semikolon (vorzüglicherweise) getrennt
  • Werte in Text und Datumsfelder werden mit Hochkomma (") angegeben
  • Nur numerische Felder dürfen ohne Hochkomma (") angegeben werden

Felder

Folgende Felder sind definiert:

NameTyp (Max Länge)Änderungen ab Release 3.19PflichtInhalt
DiallerContactTEXT (Fest)
JaFest, muss den Wert "DiallerContact" enhalten.
dtImportedDATETIME

Datum und Uhrzeit des Imports im Format YYYY-MM-DD HH:mm:SS
DiallerCampaignsNameTEXT (64)

Name der Dialler Kampagne. Wird beim Importieren nicht genutzt, da hier die Kampagne explizit angewählt wird, kann beim Importieren leer gelassen werden.
UserDataTEXT (64)

Fremdsystemschlüssel oder ID.
ClientTEXT (32)TEXT (64)
Bezeichnung Mandant.
ServiceTEXT (32)TEXT (64)
Bezeichnung Dienst oder Betrieb.
ReferenceNumberTEXT (32)TEXT (64)
Referenznummer für das Fremdsystem.
NameTEXT (32)TEXT (64)JaNachname.
FirstNameTEXT (32)TEXT (64)JaVorname.
SalutationTEXT (16)

Anrede.
TitleTEXT (16)

Titel.
CompanyTEXT (32)TEXT (64)
Firma.
AddressTEXT (32)TEXT (64)
Straße.
PostalCodeTEXT (10)

PLZ.
CityTEXT (32)TEXT (64)
Ort.
CountryTEXT (32)TEXT (64)
Land.
AccountOwnerTEXT (32)TEXT (64)
Kontoinhaber.
AccountBankTEXT (32)

Bank.
AccountNationalBankCodeTEXT (10)

BLZ.
AccountBICTEXT (11)

BIC.
AccountNumberTEXT (20)

Kontonummer.
AccountIBANTEXT (34)

IBAN.
AmountZAHL

Betrag.
PhoneNumber1TEXT (32)
JaTelefonnummer 1 in E.164 Format.
PhoneNumber2TEXT (32)

Telefonnummer 2 in E.164 Format.
PhoneNumber3TEXT (32)

Telefonnummer 3 in E.164 Format.
PhoneNumber4TEXT (32)

Telefonnummer 4 in E.164 Format.
PhoneNumber5TEXT (32)

Telefonnummer 5 in E.164 Format.
PhoneNumber6TEXT (32)

Telefonnummer 6 in E.164 Format.
FaxNumberTEXT (32)

Faxnummer.
EmailTEXT (32)TEXT (256)
E-Mail.
WebsiteTEXT (64)TEXT (Unbegrenzt)
Webseite.
CommentTEXT (Unbegrenzt)

Kommentar.
ReservedUsersUIDTEXT (32)

UID des Agenten, der dieser Datensatz zugeordnet ist.
FollowUpUsersUIDTEXT (32)

UID des Agenten, der einen Termin auf diesen Datensatz zugeordnet ist.
FollowUpDateTimeDATETIME

Termin oder Verzögerungstermin für diesen Kontakt.
ResultCodesExportKeyTEXT (32)

Export-Key des Result-Codes im Dialer.
DoneZAHL (Leer, 0 oder 1)

Result Code = erledigt.
AbortedZAHL (Leer, 0 oder 1)

Result Code = abgebrochen.
AppointmentZAHL (Leer, 0 oder 1)

Result Code = termin (im Dialer).
DelayZAHL (Leer, 0 oder 1)

Result Code = verzögert.
bPhoneNumber1InvalidZAHL (Leer, 0 oder 1)

Telefonnummer 1 ist ungültig (durch Dialler-Versuch ermittelt)
bPhoneNumber2InvalidZAHL (Leer, 0 oder 1)

Telefonnummer 2 ist ungültig (durch Dialler-Versuch ermittelt)
bPhoneNumber3InvalidZAHL (Leer, 0 oder 1)

Telefonnummer 3 ist ungültig (durch Dialler-Versuch ermittelt)
bPhoneNumber4InvalidZAHL (Leer, 0 oder 1)

Telefonnummer 4 ist ungültig (durch Dialler-Versuch ermittelt)
bPhoneNumber5InvalidZAHL (Leer, 0 oder 1)

Telefonnummer 5 ist ungültig (durch Dialler-Versuch ermittelt)
bPhoneNumber6InvalidZAHL (Leer, 0 oder 1)

Telefonnummer 6 ist ungültig (durch Dialler-Versuch ermittelt)


Code Block
titleBeispieldatensatz
"DiallerContact";"2017-07-16 07:28:44";"Unterkampagne 1";"123123122";"Mandant";"Dienst";"Referenznummer";"Nachname";"Vorname";"Anrede";"Titel";"Firma";"Straße";"PLZ";"Ort";"Land";"Kontoinhaber";"Bank";"BLZ";"BIC";"Kontonummer";"IBAN";Betrag;"49199111111";"49199222222";"49199222222";"49199444444";"49199555555";"49199666666";"Fax";"E-Mail";"Webseite";"Kommentar";"agent1";"agent1";"2017-07-17 10:00:00";"TERMIN";;;1;0;0;0;0;0;0