DynamicField as on service

[eterjack]

Good night,

It is possible, using DynamicField as an attribute of the service?

When we configure a service, it is possible to select:

type
criticality

You add one more attribute?

[crythias]

ACL

[eterjack]

Actually it's not quite it.

What I need is to create a new DynamicField as characteristic of the service.

http://imgur.com/BPJCMhK

[crythias]

In practical terms, this will result in a field that is dependent on the service chosen and be applied per ticket.

There is no significant difference (after configuration) between applying as a service-dependent (via ACL) ticket dynamic field which applies to the ticket and a service-dependent "service" dynamic field.

Edit: Except, if the service *always* has this attribute, you're likely looking at the service to do things that aren't as relevant to the service.

The service is designed to be the thing being addressed by the ticket. It isn't designed to be the thing that sets the criticality or priority. Even SLA, which is attached to the service, isn't setting criticality, impact or priority, but each of those is separately necessary to be chosen. A high criticality could have minimal impact (except for the CEO). A wide impact might be a minor bug but not something that needs to be addressed right now.

If you want to do what you want, you might consider (I'm just throwing it out there) changing the name of the service to reflect the combo that you want:
ServiceName-CriticalityName-ImpactName-PriorityName

[eterjack]

Thx, for replay

Imagine this Senary

There must be a catalog of unique service to meet 10 companies.

Inside from catalog, public services exist, and specific services for each client.

Instead of creating a service that has the name "PUBLIC", "COMPANY A", "COMPANY B", the idea would be to have a DynamicField with reference to the service

[crythias]

Assign segregated services to an entire company

If the widget being serviced is unique and company specific, this widget may better be set as an attribute of the Company or Customer.
If multiple widgets are company specific, you might be able to use the above link.
If the widget in your catalog must be a service, and must have the company name attached to the widget, you will need ACL to prevent the service widget from being shown to any but the company who has this branded widget.

If you want *exactly* what you ask for, it will require development.

If you sell hammers as part of your catalog, even if the hammer is branded, the service being addressed by the ticket is the hammer repair. You already know what customer/company is asking for repair of hammer, so you don't have to have anyone in particular to choose "again" that this is a CompanyA hammer. That doesn't mean that CompanyA doesn't have a personal SLA attached to the service/repair of hammers, but no other customer needs to know that CompanyA has a service for a custom hammer. It won't be in his list.