In addition to the standard logging of job changes that are recorded in the JobLogs table
JobLog.Meaning
0=jlmCreated,
1=jlmJobRefChange,
2=jlmJobTitleChange,
3=jlmJobStatushange,
4=jlmJobDatesChange,
5= jlmQuoteValueChange);
Additional logging can be switched on for changes to the following - writing the changes to the ChangeNarrative as appropriate (introduced in DB Version 302)
Control Word | Logged Field | ChangeNarrative | ChangeMeaning |
cClient | Client (using | Client ID | 6 |
cClientName | Client | ClientName | 7 |
cType | Job Type | Type ID | 8 |
cHandler | Job Handler | Handler ID | 9 |
cHandlerName | Job Handler | Handler Name | 10 |
cDates | Job Dates* | 4 | |
cPrice | Job Price* | 5 | |
cSalesP | Sales Person | Salesperson ID | 11 |
cSalesPName | Sales Person | Salesperson name | 12 |
cInvoiceState | Invoice State | Invoice State Id | 13 |
* These are enabled by Default but can be switched off as below
To turn on a log of the selected field use the following SQL - in this example I am turning on the salesperson Id - so I have used cSalesP in the 'key' field and 'TRUE' in the 'Value' field
INSERT INTO USERSETTINGS
(Section, Key, User, Value)
VALUES
('trJobLog_Jobs', 'cSalesP','GLOBAL', 'TRUE');
To turn off the logging for a field change the 'TRUE' to 'FALSE' - note the TRUE and FALSE are strings not binary values
INSERT INTO USERSETTINGS
(Section, Key, User, Value)
VALUES
('trJobLog_Jobs', 'cSalesP','GLOBAL', 'FALSE');
Comments
0 comments
Article is closed for comments.