Problem Management models
You can use Problem Management models to tailor processes for specific use cases.
Problem Management models enable you to define:
- States for specific use cases
- State transitions
- State transition conditions
| Model | Description |
|---|---|
| General | Problem process equivalent to the non-model base problem life cycle. |
| Model | Description |
|---|---|
| Root cause analysis | Task process equivalent to the non-model base problem life cycle. |
| General | Task process equivalent to the non-model base problem life cycle. |
Creating Problem Management models
You can create custom models for problems and problem tasks to extend their default models without compromising on existing capabilities. Test Problem Management models in a non-production instance first. If you have changed the base problem life cycle or life cycle actions, you must make the equivalent changes to your custom models.
- Create a problem model
- Create a problem task model
- Enable Problem Management models (Required only for customers upgrading to Yokohama.)
Considerations for Problem Management models and Service Operations Workspace
The com.snc.problem_management.models.enabled system property is enabled by default for new customers starting from the Yokohama release.
Upgrade customers must enable the com.snc.problem_management.models.enabled system property introduced in the Xanadu release.
Before disabling Problem Management models, you must apply any additional features you have added through custom Problem Management models to your non-model life cycle.
Service Operations Workspace 6.x is based on the Xanadu release and it supports Problem Management models.
Service Operations Workspace 5.x is based on the Washington DC release and it doesn't support Problem Management models.
If you are using Service Operations Workspace 5.x and you enable Problem Management models, you will manage problems and problem tasks in the classic UI16 experience, rather than in Service Operations Workspace.