The contact management allows you to create and manage contacts in contact rooms. Based on user-defined criteria you can specify address lists that can be exported for sending newsletters, for example.
Contacts can be either contact persons or organizations. Organizations, in the sense of contacts, should not be confused with cloud organizations (used for user administration). Duplicate checks support the avoidance of different datasets.
Special property values of contacts (e.g. salutation, address, telephone number and so on) can be assigned to different contact rooms and are therefore only visible to authorized users in the respective contact rooms. This makes it possible, for example, to ensure that the business contact data of employees are accessible to all employees, while the private contact data is only accessible to the HR department.
Audit log entries are written for use cases such as copying data tables or exporting contacts. More information can be found in chapter “Auditing”.
Note: The contact management may have to be enabled by an organization administrator (Organization > Licenses > Solutions > Contact Management with assignment Configured (Inactive) > “Enable” action).
The contacts dashboard is your central access point for contact management.
When you are added to a contact configuration as a contacts user, a dashboard is automatically created and placed on “Home”. If you are removed as a contacts user, the dashboard will also be removed.
The contacts dashboard is divided into the following areas:
You can perform the following actions:
In the contacts configuration, you can define as contacts administrator settings for the metadata of contacts. In addition, you can specify users who are allowed to use the contact management.
Contacts configurations can be created in the organization by the organization owner, organization administrator or payment user. The defined contacts administrators can edit the corresponding contacts configurations.
Note: As contacts administrator, you can switch to the assigned configuration via the contacts dashboard.
Areas
The contacts configuration dashboard is divided into the following areas:
Actions
You can perform the following actions:
Settings
In the contact configuration, you can make the following settings:
“Contact Person” tab
“Organization” tab
“Predefined Values” tab
“Externally Managed Fields” tab
Additional tabs
Contact rooms are used for the structured administration of contacts and to define access rights (“Permissions“ action) and default values (“Settings” action > “Default Values” tab).
You can store the contacts directly in the contact room at top level or structure them further with folders. Special property values of contacts (e.g. the salutation) can be assigned to different contact rooms and are therefore only visible to authorized users in the respective contact rooms.
Address lists allow collecting and exporting contacts from different contact rooms.
In addition to the structured management of contacts, it is also possible to manage them in an unstructured way. You can find more information on unstructured shelves in chapter “Unstructured Shelves”.
To create a contact person, proceed as follows:
Note:
To create an organization, proceed as follows:
Note: Before an organization is created, a duplicate check is automatically carried out (see chapter “Duplicate Check”).
When creating or changing contacts, it is checked whether a corresponding contact already exists. The duplicate check is only performed with contacts that the user, who executes the action, has access to. If a duplicate has been found, you can clean up or merge the contacts in a dialog.
Contact persons are recognized as duplicates if
Organizations are recognized as duplicates if
To perform a duplicate check, proceed as follows:
Contacts can be assigned to another contact room. Full control is required in the source contact room and change access in the target contact room. If you do not have the necessary rights, the change request can also be forwarded to another user.
To change an assignment of contacts, proceed as follows:
Note: You can determine contact administrators by switching to the configuration and clicking the “Permissions“ action.
Address lists can be created in a contact room (access rights context) using the “Create Address List” action. However, the contacts in address lists can be collected from different contact rooms.
If a user does not have access rights to a contact in the address list, the contact is displayed with “Access Denied”.
Additional address lists can be created in address lists. This makes it possible to create an address list hierarchy. For example, an address list “Events” can consist of address lists for different events. When exporting the “Events” address list, all contacts of the subordinate address lists are taken into account.
You can manually compose address lists by copying and pasting contacts into the address list. Alternatively, you can also define search criteria.
To define search criteria for an address list, proceed as follows:
Note:
The import and export of contacts is possible in address lists. When importing contacts, they are assigned to the contact room of the used address list. If a user-defined form is assigned to contacts, these properties can also be imported and exported (the programming name of the respective property serves as the column caption).
Import
Contacts can be imported and updated using a CSV or XLSX file.
To import contacts, proceed as follows:
The imported contacts are stored in the address list and in the corresponding contact room.
The CSV columns are generally user-defined text fields of the type string or date (yyyy-mm-dd). For multi-value fields (e.g. nameorgext) a carriage return (CR LF) is used as separator.
Note: The externally managed properties of a contact can only be updated, if the specified data source matches the data source of the existing contact.
Organization
The following table contains all relevant columns for organizations.
CSV Column | Field | Possible Value |
---|---|---|
objexternalkey | Import ID | String To fill fields with several lines (e.g. addresses), you can specify several lines with the same external key (objexternalkey) in the CSV file. |
objclass | Object Class | String (ContactRoomOrganisation) |
externaldatasource | External Data Source | String |
objcategory | Category | Import ID or short reference of a category (e.g. FormCategory_3_2875). |
orgname | Name | String |
orgnameext | Name (Extended) | String list |
address.addrstreet | Addresses (Street) | String |
address.addrpostofficebox | Addresses (P.O. Box) | String |
address.addrzipcode | Addresses (Zip Code) | String |
address.addrcity | Addresses (City) | String |
address.addrstate | Addresses (State) | String |
address.addrcountry | Addresses (State) | String |
address.addrtopic | Addresses (Type) | Short reference of an address type (e.g. TermBusiness, TermPrivate) |
emailinformation.emailaddress | E-Mail Addresses (E-Mail Address) | String |
emailinformation.addrtopic | E-Mail Addresses (Type) | Short reference of an address type (e.g. TermEMail1, TermEMail2) |
telephone.telnumber | Telephone Numbers (Telephone Number) | String |
telephone.addrtopic | Telephone Numbers (Type) | Short reference of an address type (e.g. TermBusiness, TermFax) |
website | Web Site | String |
telephonebusiness | Telephone Numbers (Telephone Number, Business) | String |
telephonefax | Telephone Numbers (Telephone Number, Fax) | String |
telephonemobile | Telephone Numbers (Telephone Number, Mobile) | String |
telephoneprivate | Telephone Numbers (Telephone Number, Private) | String |
emailbusiness | E-Mail Addresses (E-Mail Address, Business) | String |
emailprivate | E-Mail Addresses (E-Mail Address, Private) | String |
addressbusiness.addrstreet | Addresses (Street, Business) | String |
addressbusiness.addrpostofficebox | Addresses (P.O. Box, Business) | String |
addressbusiness.addrzipcode | Addresses (Zip Code, Business) | String |
addressbusiness.addrcity | Addresses (City, Business) | String |
addressbusiness.addrstate | Addresses (State, Business) | String |
addressbusiness.addrcountry | Addresses (Country, Business) | String |
addressinvoice.addrstreet | Addresses (Street, Invoice) | String |
addressinvoice.addrpostofficebox | Addresses (P.O. Box, Invoice) | String |
addressinvoice.addrzipcode | Addresses (Zip Code, Invoice) | String |
addressinvoice.addrcity | Addresses (City, Invoice) | String |
addressinvoice.addrstate | Addresses (State, Invoice) | String |
addressinvoice.addrcountry | Addresses (Country, Invoice) | String |
addressprivate.addrstreet | Addresses (Street, Private) | String |
addressprivate.addrpostofficebox | Addresses (P.O. Box, Private) | String |
addressprivate.addrzipcode | Addresses (Zip Code, Private) | String |
addressprivate.addrcity | Addresses (City, Private) | String |
addressprivate.addrstate | Addresses (State, Private) | String |
addressprivate.addrcountry | Addresses (Country, Private) | String |
orgsuppliernr | Supplier Number | String |
orgcustomernr | Customer Number | String |
orgcompanycode | Company Code | String |
orgtradeid | Trade Directory ID | String |
orgvatid | VAT ID | String |
orgdataprocid | Data Processing ID | String |
orgjurisdiction | Court of Jurisdiction | String |
orgindustries | Industries | Import ID of a term |
overridekeys | - | CSV columns of properties to be overwritten separated by commas (otherwise empty values are ignored and values are added in list properties) |
Note: For overridekeys with multipart CSV column names, specify the string before the dot (e.g. telephone). Overwriting therefore affects all values of the telephone aggregate and all other telephone columns serving simplification purposes (telephone.telnumber, telephone.addrtopic, telephonebusiness, telephonefax etc.). For addresses, e-mail addresses and telephone numbers you have to specify the respective base column (address, emailinformation or telephone).
Contact Person
The following table contains all relevant columns for contact persons.
CSV Column | Field | Possible Value |
---|---|---|
objexternalkey | Import ID | String To fill fields with several lines (e.g. addresses), you can specify several lines with the same external key (objexternalkey) in the CSV file. |
objclass | Object Class | String (ContactRoomPerson) |
externaldatasource | External Data Source | String |
objcategory | Category | Import ID or short reference of a category (e.g. FormCategory_3_2875). |
userfirstname | First Name | String |
persmiddlename | Middle Initial | String |
usersurname | Surname | String |
persposttitle | Post Title | String |
persawardedtitle | Awarded Title | String |
persjobtitle | Job Title | String |
persacademictitle | Academic Title | String |
persnickname | Nickname | String |
perssex | Sex | String (SEX_FEMALE or SEX_MALE) |
persbirthday | Date of Birth | Date |
perssalutations.salutation | Salutations (Salutation) | String |
perssalutations.addrtopic | Salutations (Type) | Short reference of a salutation type (either TermFormalSalutation or TermPersonalSalutation) |
persmothertongue | Mother Tongue | Short reference of a system language (e.g. LANG_GERMAN, LANG_ENGLISH) |
commlanguage | Language for Communication | Short reference of a system language (e.g. LANG_GERMAN, LANG_ENGLISH) |
address.addrstreet | Addresses (Street) | String |
address.addrpostofficebox | Addresses (P.O. Box) | String |
address.addrzipcode | Addresses (Zip Code) | String |
address.addrcity | Addresses (City) | String |
address.addrstate | Addresses (State) | String |
address.addrcountry | Addresses (State) | String |
address.addrtopic | Addresses (Type) | Short reference of an address type (e.g. TermBusiness, TermPrivate) |
emailinformation.emailaddress | E-Mail Addresses (E-Mail Address) | String |
emailinformation.addrtopic | E-Mail Addresses (Type) | Short reference of an address type (e.g. TermEMail1, TermEMail2) |
telephone.telnumber | Telephone Numbers (Telephone Number) | String |
telephone.addrtopic | Telephone Numbers (Type) | Short reference of an address type (e.g. TermBusiness, TermFax) |
website | Web Site | String |
telephonebusiness | Telephone Numbers (Telephone Number, Business) | String |
telephonefax | Telephone Numbers (Telephone Number, Fax) | String |
telephonemobile | Telephone Numbers (Telephone Number, Mobile) | String |
telephoneprivate | Telephone Numbers (Telephone Number, Private) | String |
emailbusiness | E-Mail Addresses (E-Mail Address, Business) | String |
emailprivate | E-Mail Addresses (E-Mail Address, Private) | String |
addressbusiness.addrstreet | Addresses (Street, Business) | String |
addressbusiness.addrpostofficebox | Addresses (P.O. Box, Business) | String |
addressbusiness.addrzipcode | Addresses (Zip Code, Business) | String |
addressbusiness.addrcity | Addresses (City, Business) | String |
addressbusiness.addrstate | Addresses (State, Business) | String |
addressbusiness.addrcountry | Addresses (Country, Business) | String |
addressinvoice.addrstreet | Addresses (Street, Invoice) | String |
addressinvoice.addrpostofficebox | Addresses (P.O. Box, Invoice) | String |
addressinvoice.addrzipcode | Addresses (Zip Code, Invoice) | String |
addressinvoice.addrcity | Addresses (City, Invoice) | String |
addressinvoice.addrstate | Addresses (State, Invoice) | String |
addressinvoice.addrcountry | Addresses (Country, Invoice) | String |
addressprivate.addrstreet | Addresses (Street, Private) | String |
addressprivate.addrpostofficebox | Addresses (P.O. Box, Private) | String |
addressprivate.addrzipcode | Addresses (Zip Code, Private) | String |
addressprivate.addrcity | Addresses (City, Private) | String |
addressprivate.addrstate | Addresses (State, Private) | String |
addressprivate.addrcountry | Addresses (Country, Private) | String |
persfunctionbc | Function According to Business Card | String |
perssupervisor | Supervisor | String |
persassistent | Assistant | String |
persmainorgname | Name of the Organization | String |
persfunctions | Functions | Import IDs of terms separated by a carriage return |
persmainorg | Main Organization | Import ID of an organization |
perscurremployments.emplorg | Current Organizations (Organization) | Import ID of an organization |
perscurremployments.emplfunction | Current Organizations (Function) | String |
perscurremployments.emplfrom | Current Organizations (From) | String |
perscurremployments.emplto | Current Organizations (To) | String |
perspastemployments.emplorg | Previous Organizations (Organization) | Import ID of an organization |
perspastemployments.emplfunction | Previous Organizations (Function) | Import ID of a term |
perspastemployments.emplfrom | Previous Organizations (From) | String |
perspastemployments.emplto | Previous Organizations (To) | String |
persconsentdeclarations | Declarations of Consent | Import IDs of terms separated by a carriage return |
overridekeys | - | CSV columns of properties to be overwritten separated by commas (otherwise empty values are ignored and values are added in list properties) |
Note: For overridekeys with multipart CSV column names, specify the string before the dot (e.g. telephone). Overwriting therefore affects all values of the telephone aggregate and all other telephone columns serving simplification purposes (telephone.telnumber, telephone.addrtopic, telephonebusiness, telephonefax etc.). For addresses, e-mail addresses and telephone numbers you have to specify the respective base column (address, emailinformation or telephone).
Export
Contacts can be exported as CSV file. For property lists, the first value found is exported.
To export contacts, proceed as follows:
The CSV file with the selected columns is downloaded.
Note: Contacts in the wastebasket are not exported.
To delete a contact (to be placed in the recycle bin) you need to have change access. If property values of the contact are assigned to a different contact room, also change access is required in this room. If you do not have the necessary rights, contact a contacts administrator. To delete permanently a contact (to be removed from the recycle bin) full control is required.
To delete a contact, execute the “Delete” context menu command.
Access to contacts is also possible via third-party products such as “Apple Contacts”, which support the CardDAV standard. A password for applications is required for access. If you have not yet created one for CardDAV, create one now (see chapter “Access for Applications”).
To display contacts in a third-party product, proceed as follows:
The cloud contacts are now displayed in the third-party product and can be edited if applicable.
Note: The “Open Cloud Address Book” context menu command of the Fabasoft Cloud notification symbol can be used to include the address book list in Microsoft Outlook.
Via a serial e-mail you can send personalized e-mails to defined recipients from the contact management.
Note: This functionality is only available if your cloud organization has its own SMTP server configured.
To send a serial e-mail, proceed as follows:
Metadata
“Serial E-Mail” tab
“Addressees” tab
“Transmission Log” tab