Improvement - configurations By entity

[phamorais]

Hi @yllen

Firstly congratulations on the plugin.

I would like to know if it is possible to make the plugin settings separate by entity, as currently all enabled rules are applied from outside Global (for all entities).

However, in some cases, the rules should not be applied to all entities. By separating the rules by entity, we would have a more personalized way of using the rules of this plugin for child entities.

[yllen]

You can't had separate configuration per entity for all parameters.
Example: ticket's number are always for all entities.
Which parameter would you like to have per entity?

[rafaths]

Would it be possible to add another parameter to form the format of the ticket number, for example 'ymde0001' where the 'e' would be the entity's id? I need to differentiate tickets by entity.

[phamorais]

Hi @yllen

I completely agree that the number of tickets cannot be separated by entity, given that the GLPI base uses this value as incremental.

However, all other fields (from the little understanding I have) can be separated by adding entity validation.

In my case, our needs would mainly be the fields:

-*

the option "Protect from simultaneous update" I don't know what its purpose is. So don't include it in the list.

With the use of GLPI through an ESM (enterprise service manager), the use of the software for other areas of the company is growing very quickly, and the Behaviors rules help us a lot. However, when using many different entities and service areas, the service rules generally differ between areas. I believe it would be a great improvement to the plugin.