Hi Julien,
I think option 2 is better, but I would imagine a equivalent to
notifications (templates and notifications separated).
An example :
- My company manages customers
- I've got a set of global categories (ie root entity, recursives)
- I apply a template for this category
- For one customer, I need another template (because of a different
contract, and so on)
The simpliest solution would be to add an object to describe the
relation (ticketcategories_id, entities_id, is_recursive,
tickettemplates_id). The other one would be a rules engine that let
people do whatever the want (my example would be easy with it).
Walid.
On 01/09/2011 22:32, MoYo wrote:
Hi,
We are working on templates for tickets in order to set mandatories,
hidden and predefined fields.
We have two choices to implement that :
- Permit to choose a template on ticket creation.
- Link templates to ticket's categories. Selecting a category will
load the template.
What do you think about these 2 options ?
Regards
Julien
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
