Overview Configuration Data/Files

Transcription

1 Overview Configuration Data/Files Copyright combit GmbH ; Rev EN All rights reserved.

2 Contents 1 General Project directory Project file (.crm) Project database / SQL Server database Input Form (.dli) List View / Container Layout (.vlc) Global Import and Export templates Printer specific settings for print templates System database ("combit_crm_system.cmbt_files") Project specific settings User specific settings Layout and content "combit_crm_system.cmbt_files" crm rights management - ER Model Local Application Data directory User specific Import and Export templates Further configuration files Registry General Database connection Layout of list views and containers Container filter and AskString User specific settings address pick-up configuration

3 1 General Please note that the stored configurations may change due to program changes. 3

4 Project directory 2 Project directory 2.1 Project file (.crm) The project and view properties are generally stored in the combit Relationship Manager project file. This project file (file extension '.crm') is stored in an Unicode XML format. The project properties can be viewed in the crm under Settings > Project. Example: <item name="id">695581df265d41919da8d18b0e1dd7d9</item> [Unique project ID] <item name="name">crm_solution</item> [Name of project] <item name="description">das crm Referenz Projekt</item> [Description] <item name="dbname">combit_crm_solution</item> [SQL database] Global, but user independent settings within the project are also stored in the project file, e.g. Sort Orders, Quick Find fields, global filters, global statistics. Additionally the configuration for "Merge" as well as the Navigation Structure is stored in the project file. 2.2 Project database / SQL Server database Table cmbt_manflttags Description (Temporary) Storage of the manual filter; a.tag file is created with these entries cmbt_autoinc_counters cmbt_tm_appoint_xxx cmbt_tm_appointments cmbt_tm_resources cmbt_tm_todo_xxx cmbt_tm_todos Auto Counter (Help) tables for Appointments Appointments Ressource Management (Help) tables for Tasks Tasks 2.3 Input Form (.dli) The Input Form (incl. Cont. Links, Combobox entries, Script Direct contents, etc.) is stored in the combit Relationship Manager project directory in file <View name>.dli (Text format). 2.4 List View / Container Layout (.vlc) The standard layout of the list views / containers is stored in the combit Relationship Manager project directory in file <View name>.vlc (Text format). 2.5 Global Import and Export templates Global Import and Export templates are searched resp. stored in the project directory of the currently loaded project: <instdir>\*.itp Import templates <instdir>\*.etp Export templates 4

5 Project directory 2.6 Printer specific settings for print templates If printer specific settings like Printer, Duplex Mode, Trays, etc. are set for a print template, these settings will be stored in a separate file under the same name with the difference of the last character of the extension being a 'p'. This is the so called "P-File", e.g. 'Persons Adresses.lsp'. This p-file is stored (locally) in the directory "Documents and Settings" as default. However if there is such a p-file in the (mostly central) directory with the print template and this one is newer than the local p-file, the central p-file is copied locally and used. With it printer specific settings can be supplied centrally, by the administrator copying his (local) p-file into the (central) print template directory and the p-file automatically being "distributed" to the clients due to its newer date. Warning: By centrally distributing such a p-file all users will loose their possible own (older) printer specific settings for the print template of the same name! 5

6 System database ("combit_crm_system.cmbt_files") 3 System database ("combit_crm_system.cmbt_files") 3.1 Project specific settings The project specific settings like the Standard Toolbar are also stored here. 3.2 User specific settings User specific settings which are PC-independent, e.g. user specific filters and statistics, toolbar-, menuand shortcut-settings, will be stored here. Note: Is there are no stored Toolbar resp. Keyboard shortcut configuration for the current user, the configuration for the user "MasterTemplate" is automatically used (if existing). With the Toolbar and Keyboard shortcuts of this user it is therefore possible to centrally provide certain Toolbar and Keyboard shortcut configurations for new users (and views). 3.3 Layout and content "combit_crm_system.cmbt_files" Table column "PROJECT" Storage of the unique ProjectID for assigning the entry to a certain project Table column "PATH" The "path" is a pseudo file name, which describes the content of the "file" (see FILECONT) Table column "FILECONT" Binary content, containing the "file", which is readout at runtime Content Path global.ini tmconfig.xml <USER>\TM.xml <USER>\dli_global.ini <USER>\dli_user.ini <USER>\toolbar.cfg <USER>\toolbar2.cfg <USER>\toolbar3.cfg <USER>\toolbar4.cfg <USER>\toolbar5.cfg Description Storage of scripting settings (Set/GetGlobalProperty) Stored sort order of Appoinments / Tasks Configuration of the Appointments / Tasks managment Default settings for input forms (internal) Default settings for input forms (internal) Storage of the main window toolbar (crm ). Storage of the main window toolbar (crm ). Storage of the main window toolbar (crm ). Storage of the main window toolbar (crm and higher). Storage of the main window toolbar 6

7 System database ("combit_crm_system.cmbt_files") <USER>\toolbar_tm.cfg <USER>\toolbar2_tm.cfg <USER>\toolbar3_tm.cfg <USER>\toolbar4_tm.cfg <USER>\toolbarshortcuts.cfg <USER>\toolbarshortcuts2.cfg <USER>\toolbarshortcuts3.cfg <USER>\toolbarshortcuts4.cfg <USER>\toolbarshortcuts_tm.cfg <USER>\toolbarshortcuts2_tm.cfg <USER>\toolbarshortcuts3_tm.cfg <USER>\toolbarshortcuts4_tm.cfg <USER>\<VIEW>\LastFilter.xml <USER>\<VIEW>\user.ini <USER>\<VIEW>\toolbar.cfg <USER>\<VIEW>\toolbar2.cfg <USER>\<VIEW>\toolbar3.cfg <USER>\<VIEW>\toolbar4.cfg <USER>\<VIEW>\toolbar5.cfg <USER>\<VIEW>\toolbarshortcuts.cfg <USER>\<VIEW>\toolbarshortcuts2.cfg <USER>\<VIEW>\toolbarshortcuts3.cfg <USER>\<VIEW>\toolbarshortcuts4.cfg <USER>.xml <USER>\favorites.xml <USER>\history.xml (crm and higher). Storage of the Appointments and Tasks toolbar (crm ). Storage of the Appointments and Tasks toolbar (crm ). Storage of the Appointments and Tasks toolbar (crm and higher). Storage of the Appointments and Tasks toolbar (crm and higher). Storage of the main menu keyboard shortcuts (crm ). Storage of the main menu keyboard shortcuts (crm ). Storage of the main menu keyboard shortcuts (crm and higher). Storage of the main menu keyboard shortcuts (crm and higher). Storage of the Appointments and Tasks keyboard shortcuts (crm ). Storage of the Appointments and Tasks keyboard shortcuts (crm ). Storage of the Appointments and Tasks keyboard shortcuts (crm and higher). Storage of the Appointments and Tasks keyboard shortcuts (crm and higher). Automatic storage of the 9 last used filter expresses ('Filter > General'). The storage is done user- and view specific. (crm and higher). Storage of scripting settings (Set/GetGlobalProperty) and mail settings. Storage of the view window toolbar (crm ). Storage of the view window toolbar (crm ). Storage of the view window toolbar (crm ). Storage of the view window toolbar (crm and higher). Storage of the view window toolbar (crm and higher). Storage of the view menu keyboard shortcuts (crm ). Storage of the view menu keyboard shortcuts (crm ). Storage of the view menu keyboard shortcuts (crm and higher). Storage of the view menu keyboard shortcuts (crm and higher). User defined filter expressions and templates for relational appending. Favorites History 7

8 crm rights management - ER Model 4 crm rights management - ER Model The graphic shows the rights managment of the combit Relationship Manager for a possible transfer to another database. Please notice that the fields "LoginName" (cmbt_users) and "Name" (cmbt_groups) always have to be unique! Note: If rights have to be set for special crm projects, these have to have unique ProjectIDs. The assigned ID can be viewed in the crm under Settings > Project. 8

9 Local Application Data directory 5 Local Application Data directory The crm stores certain configuration settings in a "combit\crm\" subdirectory in the local Windows Application Data directory of the user. Typically these are the directories: Windows 2000, XP: C:\Documents and Settings\<User>\Application Data\combit\cRM Windows Vista, 7: C:\Users\<User>\AppData\Roaming\combit\cRM 5.1 User specific Import and Export templates Import templates: *.itp Export templates: *.etp 5.2 Further configuration files CMBTSMS.INI: Configuration file of the phone manager SMS provider cmph??.cfg: phone manager TAPI Driver configuration cumc.cfg: Thunderbird and Tobit David.Infocenter AddIn configuration file cumc.log: Log file of the crm archiving for Thunderbird and Tobit David.Infocenter dialuser.ini: phone manager configuration file enrich.txt: Log file for the phone directory enrichment ical_export.log: Log file of the time manager ical export ical_import.log: Log file of the time manager ical import Outlook_cRM.txt: Log file of the crm archiving for Outlook Printer specific settings for print templates (see Printer specific settings for print templates) 9

10 Registry 6 Registry 6.1 General The basic Registry key, under which possible settings of the combit Relationship Manager are stored is HKEY_CURRENT_USER\Software\combit\combit Relationship Manager. 6.2 Database connection At start of the combit Relationship Manager the database connection info like database server, database type etc. are readout from the registry under.\settings. 6.3 Layout of list views and containers A possible user specific layout configuration is stored under.\projects\<projectname>\<view>\brwconfig User specific layout or standard layout? With a timestamp entry it is decided, if the user has a customized user specific layout configuration or if the global layout configuration (.vlc file) is used. As soon as the value in the registry is "newer" as the.vlc file, the configuration from the registry is used. If an unexpected layout configuration for the user is used, the date of the PC and the timestamp values of the corresponding list in the registry and.vlc file should be checked. 6.4 Container filter and AskString If a container filter uses AskString, the last entered value is stored under the following registry key, e.g. under.\projects\<projectname>\<view>\brwconfig\id.contacts.personid#{b3c0768a b5-b4f2-7d31a6c10ec5}\askstringinputs. 6.5 User specific settings User and PC specific settings at the same time (Layout of list views and containers, dialog positions, selected fields for search, last search expression, history combobox entries, AutoMessageBox values, etc.) are stored in the registry under.\projects\<view>. Example: ComboBox entry of the last search (Find > Find...):.\Projects\cRM_Solution\Adresses\CUIDlgFullTextSearch\History 6.6 address pick-up configuration The activation of the clipboard monitoring is stored under: HKEY_CURRENT_USER\Software\combit\Address Parser\WatchClipboard A separate branch is stored for each configuration: HKEY_CURRENT_USER\Software\combit\Address Parser\Job 1, Job 2, etc. 10