Differenze tra le versioni di "MDMM management"
Da itm wiki.
| (2 versioni intermedie di uno stesso utente non sono mostrate) | |||
| Riga 14: | Riga 14: | ||
|- | |- | ||
| − | | Custom | + | | Custom Fields || |
|- | |- | ||
| Riga 29: | Riga 29: | ||
|- | |- | ||
| − | | | + | | DSG5 || |
|- | |- | ||
| − | | | + | | DSG6 || |
|- | |- | ||
| Riga 63: | Riga 63: | ||
|} | |} | ||
| + | |||
| + | ''[[glossary|MDMM]]'' settings work for all ''[[glossary|workflows]]'' when a ''[[glossary|workflow field]]'' is used. | ||
Versione attuale delle 20:16, 5 nov 2017
MDMM functionality enables to condition the visibility of workflow fields values base on the project / service of the ticket.
For example a workflow field might have three values, "1", "2" and "3". With MDMM it could be possible to made visible values "1" and "2" for service "A" and "2", "3", for service "B".
This functionality is very useful because it makes it possible to avoid creating different workflow fields with different values, one per each project / service, thus greatly simplifying configuration.
For the following workflow fields it is possible to enable MDMM management:
| Field | Comment |
|---|---|
| Area | |
| Custom Fields | |
| DSG1 | |
| DSG2 | |
| DSG3 | |
| DSG4 | |
| DSG5 | |
| DSG6 | |
| Functionality | |
| Product | |
| Requester | |
| Resolution Cause | |
| Service | |
| Ticket Closure Cause | |
| Ticket Tuple |
|
| Ticket Type | |
| Timesheet Category |
MDMM settings work for all workflows when a workflow field is used.
