Dear All,

It would of great help if additional tags for technician are added in notification templates.

Like mobile number email I'd etc

Currently there r tags for author phone number mobile number etc.

I have built out of GLPI, FusionInventory, CustomFields, Microsoft MDT (Deployment tool) and a home made database synchronisation tool something that is close to SCCM at very low cost.

I plan to relase it as soon as it is clean enough to be shared.

Basically, I use the data from GLPI to feed the MDT database. This enable automatic OS deployment just pressing "F12" at boot (PXE boot to MDT). Our technicians just choose the OS version, the machine name, the additional applications (MS office, OpenOffice....) in GLPI and that's it.

In order to manager hardware specificities, I rely on the computer model to set some default, model based values. This used to work fine until the lastest update (21) in FusionInventory. A lot of machines where identified with a technical code for the model rather than a commercial name. This code is what MDT relies on to identify a model (plus, several models with slightly different hardware may often the same commercial name). The output on screen is much nicer (20C600JJFR is now ThinkPad Edge E540) but MDT is broken.

Therefore my suggestion is:

- Have GLPI manage both the commercial name and the technical code for computer models.

- Add one column to the glpi_computermodels table for code. Make this column indexed unique while names can be non unique.

- Show both code and name on computer description page.

- Adapt Fusion Inventory import code to store both informations.

Indeed, there will be an issue when two different versions of FI will report a different name for the same code. I guess the rule should be:

- If code and name reported are the same and conflict with an existing model where they differ, keep the one that differs as this is probably more up to date.

- If code and name reported are different, then update table. Last to talk wins! 

GLPI has only one automatic SLA action that is SLATICKET and this action has only one TICKET RECALL notification, for a 20% ticket and a ticket due date, you will receive the same notification by email. This for the actor is not good, because he will not understand very well, because he can not use more than one notification model for SLA. The ideal is to have 2 notifications for the SLA duedateNotification and Ticket Recall notice. Because this is very important for both the client and the manager to improve the company process.

Create another notification similar to TICKET RECALL for SLA duedate

To deal with asset leasing we need to add the following features :

- start / end date for leasing

- start / end date for leasing warranty

- link infocom to leasing supplier

- link contract to leasing supplier

Please Enable the option of the choose Colours Palettes for Priority Colors in

Preference field

Please add the selectable option Contracts to the Tool Projects in

GLPI.With this option the user could select the "Assigned Contract" in
their Projects

Please add the selectable option Supplier to the Tool Projects in GLPI.With this option the user could select the principal "Supplier" in their Projects

Please add the selectable option Budgets to the Tool Projects in GLPI.

With this option the user could know how make moderate "investments with the budget"

Add the possibility to disable automatic actions from massive actions

Display the right explanations in the Setup => Dropdown form.

There's no legend that indicates what represent each of the 2 colors