Differenze tra le versioni di "MDMM management"
Da itm wiki.
(Created page with "TBC") |
|||
| (8 versioni intermedie di uno stesso utente non sono mostrate) | |||
| Riga 1: | Riga 1: | ||
| − | + | ''[[glossary|MDMM]]'' functionality enables to condition the visibility of ''[[glossary|workflow fields]]'' values base on the ''[[glossary|project]]'' / ''[[glossary|service]]'' of the ''[[glossary|ticket]]''. | |
| + | |||
| + | For example a ''[[glossary|workflow field]]'' might have three values, "1", "2" and "3". With ''[[glossary|MDMM]]'' it could be possible to made visible values "1" and "2" for ''[[glossary|service]]'' "A" and "2", "3", for ''[[glossary|service]]'' "B". | ||
| + | |||
| + | This functionality is very useful because it makes it possible to avoid creating different ''[[glossary|workflow fields]]'' with different values, one per each ''[[glossary|project]]'' / ''[[glossary|service]]'', thus greatly simplifying configuration. | ||
| + | |||
| + | For the following ''[[glossary|workflow fields]]'' it is possible to enable ''[[glossary|MDMM]]'' management: | ||
| + | |||
| + | {| class="wikitable" | ||
| + | ! 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 || | ||
| + | |||
| + | |} | ||
| + | |||
| + | ''[[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.
