Dmon.mif

Topic creation date:2008-08-16

DMON.MIF is designed to be used with the SuperVISor Net ODBC MBMNetODBC.dll version 1.1.0.51. For versions of SuperVISor Net ODBC MBMNetODBC.dll version 4.2.1.356 and greater use DMON4.MIF, as it is includes a more up to date and complete set of features.

This filter use an ODBC connection to link to the Monitor Faircom Database, which requires the DSN (Data Source Name) is specified. If AutoImportFilePathName is set then the filters will use this as the DSN. If AutoImportFilePathName is blank then ImportDSN field in the [import] section of the PMA.INI file is used as the DSN. ImportFileDSN in the [import] section is not used for this filter.

In he PMA.INI file [IMPORT] section ImportFilterName needs to be set to "dmon.mif"

General PMA.INI file settings

In the PMA.INI file the [System] section settings are:

PmaKey = 4

PMASystemLongName = "Monitor Business Systems"

PMASystemShortName = "MON"

The PMASystemShortName is not currently being used, but is kept in for reference.

WidthOfClientCode = 21

WidthOfMatterCode = 21

WidthOfGeneralCode = 21

The width of string fields should be set to 21.

Matters and Clients

If the MatterClientRelationship (in the system section of the PMA.INI file) is logically 'and'ed with 4 (CLIENT_FIND_MATTER) or MatterClientRelationship is logically 'and'ed with 2 (MUST_HAVE_CLIENT) then the filter treats the import as an import of clients, and will populate the client fields. This makes the client the primary and the matter secondary in the client matter relationship Otherwise the filter populates the matter fields, and the matter is the primary and the client secondary in the client matter relationship.

In either case the Monitor "secondary" table fields:- Number, Name, Department, "Price code" are used to populate the client or matter field as outlined above. If a number starts with '!' it is ignored. The following table shows the mappings for the "secondary" or Monitor secondary database:

Monitor secondary database import mapping table

	Faircom ODBC	Supervisor (Monitor)	MonTel
	Number	Secondary Number	'Matter Code' or 'Client Code'
	Department	Secondary Department	Department
	Name	Secondary Name	'Matter Description' or 'Client Name'
	Price Code	Secondary Price Code	ChargeCode

If 'Price Code' = 9 then ChargeCode = 1 meaning that this is an Admin code, otherwise ChargeCode = 1, meaning it is a normal chargeable code.

If the matter is the primary in the mater client relationship and the MatterTypeName (in the descriptions section of PMA.INI) is set, then the matter description will be the "Secondary Name" with MatterTypeName appended in brackets, eg 'Acme Pty Ltd' as the Secondary Name will be 'Acme Pty Ltd (Matter)'. In addition, if the MATTER_FIND_CLIENT bit is set in the MatterClientRelationship then the client will also be populated using the fields from the table above.

If the client is primary then only the client fields will be populated, regardless of the other bit settings such as CLIENT_FIND_MATTER. For better control and the ability to have separate matters and clients with the client as the primary, use the DMON4.MIF filter (if using a more recent monitor SuperVISor Net ODBC MBMNetODBC.dll).

Disbursments

Disbursements are populated, naturally enough, from the Monitor "Disbursement" table using the Number and Name fields. If a number starts with '!' it is ignored.

Activities

Activities are also populated from the Monitor "Disbursement" table using the Number and Name fields. If a number starts with '!' it is ignored.

Employees

Employees are populated from the Monitor "Prim" table using the Number, Name, ID, Department. The following table shows the mappings for the "prim" or Monitor primary database:

Monitor primary database import mapping table

	Faircom ODBC	Supervisor (Monitor)	MonTel
	Number	Primary Number	Employee Code
	Department	Department	Department
	Name	Primary Name	Full Name
	ID	Primary ID	Login Name

If a number starts with '!' it is ignored.

ImportReportFormat

	ImportReportFormat (From the import section of the PMA.INI file)	Bit value	Add this number
	Default value see the Monitor primary database import mapping table and Monitor secondary database import mapping table above.	0	0
	Department becomes 'Extension Number' in MonTel. MonTel Department is blank.	1	1
	Primary Number is copied to Pin Number as well as Employee Code.	2	2
	Primary ID becomes Employee code as well as Login Name, and Number becomes Pin Number.	3	4
	LDAP import only. Import users from Active directory.	9	256
	LDAP import only, search entire Active Directory tree for users, not just the 'users' folder.	10	512
	LDAP import only, ignore users who are not in the either the MonTelUsersGroup or MonTelAdminGroup	11	1024
	LDAP import only, import users even if they don't have a telephone number entry in Active Directory.	13	4096