Fabasoft Folio supports the management of contacts. In addition to the classic contact management, a separate contact management app that can be enabled is also available.
The following object types define contacts:
For persons
Name and address details, including e-mail addresses and telephone numbers, can be entered for individual persons. Each person has a list of business objects directly assigned to the person and a list of correspondence (Communication) and a journal. In general, the person's main address is the first address entered. However, if the option to use the organization's address as the main address has been selected, this is the main address.
For organizations
Note: To search for persons and organizations, search for “Contact”.
An organization represents a legal person. Contact persons who are employed in this organization can be added. In addition, the corresponding business objects are stored in an organization, as well as the direct correspondence with the legal person. All correspondence with an organization - i.e. both those conducted directly with the organization and those conducted indirectly via contact persons - appears in the communication.
To create an Organization, proceed as follows:
In contrast to organizations representing external partners, an own organization is represented by an Own Organization. Employees can be assigned to own organization.
To create an Own Organization, proceed as follows:
An employee can be created in the Employees field of an own organization or on “Home”.
To create an Employee, proceed as follows:
A contact person can be created either in the Contact Persons field of an organization or on “Home”.
To create a Contact Person, proceed as follows:
Note: Contact persons are not allowed in the Employees field of an own organization.
Persons and organizations have a Communication field, in which the incoming and outgoing communication of this organization/person is recorded.
To display the communication with a person/organization, proceed as follows:
All business objects that have been received from/sent to this person/organization will be displayed in the Communication field.
Addressee Lists can be created for bulk mailings. An Addressee List is created using sets of contacts, which can be filtered by individual countries.
The contacts determined this way can have several addresses, so a Topic (i.e. a Term) can be specified in an addressee list that gives the purpose of the addressee list (for example, TechEd invitation). In this case, the address of a contact that has this (or a higher-level) Term entered will be used. If no address is found for the Term, the main address of the contact will be used.
To create an Addressee List for bulk mailings, proceed as follows:
Resolving an addressee list
Before an Addressee List can be used for mailings, it must be resolved. For this purpose, the “Resolve” context menu command is available.
During resolving, the individual addresses will be determined and stored for the addressee list in the form of a CSV file. This CSV file will be stored on the “Result” tab and can be downloaded using the “Download” button. In addition, the number of determined addresses will be provided in the Count field and a preview will be provided in the Addressees (Preview, Maximal 100 Lines) field.
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. 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.
Note: To enable the contact management app, an administrator must add the app to a group on the “Apps” tab, in the Licensed Apps field. After applying the changes, a corresponding configuration is automatically added to the App Configurations field. Users who should administer the app can be added as Contacts Administrator to the configuration.
The contacts dashboard provides your access point to the 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.
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
Contact rooms are used for the structured administration of contacts and to define access rights (“Team” 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.
Unstructured Contact Rooms
If you want to manage a large number of contacts in a contact room, an unstructured contact room is a good option, which allows each user to individually specify which contacts are to be displayed using search criteria.
Using the “Tools” > “Display Entries in Flat List” context menu command, users with full control can convert a contact room into an unstructured contact room. Note that this will delete all existing contact folders.
The following options are now available to you:
Using the “Tools” > “Structure List Entries in Folders" context menu command, you can convert an unstructured contact room back into a structured one. In doing so, the contacts are stored in folders that correspond to the respective initial letter. A separate folder is created for address lists.
Note:
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 “Team” 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 |
orgname | Name | String |
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) | Reference of an address type (e.g. TermBusiness, TermPrivate) |
emailinformation.emailaddress | E-Mail Addresses (E-Mail Address) | String |
emailinformation.addrtopic | E-Mail Addresses (Type) | Reference of an address type (e.g. TermEMail1, TermEMail2) |
telephone.telnumber | Telephone Numbers (Telephone Number) | String |
telephone.addrtopic | Telephone Numbers (Type) | 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 |
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 |
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) | Reference of a salutation type (either TermFormalSalutation or TermPersonalSalutation) |
persmothertongue | Mother Tongue | Reference of a system language (e.g. LANG_GERMAN, LANG_ENGLISH) |
commlanguage | Language for Communication | 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) | Reference of an address type (e.g. TermBusiness, TermPrivate) |
emailinformation.emailaddress | E-Mail Addresses (E-Mail Address) | String |
emailinformation.addrtopic | E-Mail Addresses (Type) | Reference of an address type (e.g. TermEMail1, TermEMail2) |
telephone.telnumber | Telephone Numbers (Telephone Number) | String |
telephone.addrtopic | Telephone Numbers (Type) | 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.
To display contacts in a third-party product, proceed as follows:
The Folio contacts are now displayed in the third-party product and can be edited if applicable.
Via a serial e-mail you can send personalized e-mails to defined recipients from the contact management.
To send a serial e-mail, proceed as follows:
Metadata
“Serial E-Mail” tab
“Addressees” tab
“Transmission Log” tab