Sample process administration with domain specific applications
The following example illustrates process administration with domain-specific applications and modules.
As the administrator of the Oceanic domain, David Loo decides to customize the Configuration application. To start with, David reviews the modules available in the Configuration application module.
Image omitted: Domain\_overrides\_appmod\_01.png
David decides to rename the Configuration application to CMDB and to allow the inventory\_admin role to see the application.
David decides to rename the Configuration application to CMDB and to allow the inventory\_admin role to see the application.
Image omitted: Domain\_overrides\_app\_02.png
Next, David decides to change the Incident application by activating the **Open - in "New" State** module and adding a new filter item to show open incidents in the Oceanic category.
Next, David decides to change the Incident application by activating the **Open - in "New" State** module and adding a new filter item to show open incidents in the Oceanic category.
Image omitted: Domain\_overrides\_mod\_03.png
This creates a new module entry in the application rather than overwriting the existing module in the global domain.
This creates a new module entry in the application rather than overwriting the existing module in the global domain.
Image omitted: Domain\_overrides\_mod\_04.png
If another administrator from another domain, such as Fred Luddy, logs in and looks at the Configuration application, the settings from the global domain appear.
If another administrator from another domain, such as Fred Luddy, logs in and looks at the Configuration application, the settings from the global domain appear.
Image omitted: Domain\_overrides\_appmod\_04.png
\[Omitted image "Domain\_overrides\_appmod\_05.png"\] Alt text:
\[Omitted image "Domain\_overrides\_appmod\_05.png"\] Alt text: