A few additional features have been included in version 3.2

Job Task Validation

Per-customer validation has been introduced for job tasks. Whenever a job is saved the SQL-Server procedure TaskValidation_RT is called, which in turn calls the procedure TaskValidation_RT_Local. This procedure can be modified to meet your local requirements and is not affected by upgrades. If a task is invalid then the procedure returns the text which will be displayed to the user and the job save is disallowed. If the task is valid then no text is returned.

Because, at the time that it is called, no data has yet been written to the database, all values are passed to the procedure as arguments. The supported arguments are:

TaskDescription
EquipmentId
JobTypeId
JobStatusId
JobCallDate
JobStartDate
JobEndDate
JobTaskNo
PersonnelId
Hours
JobTaskStatusId
JobTaskTypeId
TaskStartDate
TaskEndDate
HourlyRate
HourlyRateVAT
Billable
Mileage
TravelHours

KPI Report Options

For all of the reports which use Microsoft Excel spreadsheets as templates, system options have been added to allow the templates to be held in the server location of your choice

 

TNA Property Page Red, Amber, Green Validation

Per-customer validation has been added to the TNA property page. The validation causes the traffic light to be displayed as either red, amber or green. Whenever any relevant data on the screen is changed the SQL-Server procedure TNAGetRAG_RT is called, which in turn calls the procedures TNAItemRed_RT_Local, TNAItemAmber_RT_Local and TNAItemGreen_RT_Local. These procedures can be edited to enforce whatever validation rules you require and are not affected by upgrades.

At the time the procedures are called no data has been written to the database and so all values to be validated must be passed as arguments. The arguments currently supported are:

RequiredCompetenceTypeId
AttainedCompetenceTypeId
PersonnelCompetenceStatusId
ModelId
TrainingDate
AssessmentDate
ReviewDate

Per-Bin Spare Part Prices

It is now possible to enter spare part prices for parts in individual stock locations. When a part is added to a job, if the part in the selected bin has a price then that value is used rather than the Effective Job Charge value from the spare part itself.

Note that per-contract markups/discounts are still applied

We hope to get 3.2 into beta next week and out on general release within a couple of weeks of that