mirror of
https://github.com/Icinga/icingaweb2-module-businessprocess.git
synced 2026-01-05 13:19:35 -05:00
commit
23b3c92ed7
6 changed files with 75 additions and 0 deletions
|
|
@ -30,6 +30,7 @@ Documentation
|
|||
* [Getting Started](doc/02-Getting-Started.md)
|
||||
* [Create your first process node](doc/03-Create-your-first-process-node.md)
|
||||
* [Importing Processes](doc/04-Importing-Processes.md)
|
||||
* [Customize Node Order](doc/05-Customize-Node-Order.md)
|
||||
|
||||
### Web Components
|
||||
* [Breadcrumb](doc/12-Web-Components-Breadcrumb.md)
|
||||
|
|
|
|||
74
doc/05-Customize-Node-Order.md
Normal file
74
doc/05-Customize-Node-Order.md
Normal file
|
|
@ -0,0 +1,74 @@
|
|||
<a id="Customize-Node-Order"></a>Customize Node Order
|
||||
=====================================================
|
||||
|
||||
By default all nodes are ordered alphabetically while viewing them in the UI.
|
||||
Though, it is also possible to order nodes entirely manually.
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> Once manual order is applied (no matter where) alphabetical order is
|
||||
> disabled for the entire configuration.
|
||||
|
||||
Reorder by Drag'n'Drop
|
||||
----------------------
|
||||
|
||||
Make sure to unlock the configuration first to be able to reorder nodes.
|
||||
|
||||
### Tile View
|
||||
|
||||
To move a tile simply grab it with your mouse and drag it to the location you
|
||||
want it to appear at.
|
||||
|
||||

|
||||

|
||||
|
||||
### Tree View
|
||||
|
||||
While in tree view nodes can be moved the same way. You just have a narrower
|
||||
area to grab them.
|
||||
|
||||

|
||||

|
||||
|
||||
The tree view also has an advantage the tile view has not. It is possible to
|
||||
move nodes within the entire hierarchy. But remember to unfold processes first,
|
||||
if you want to move a node into them.
|
||||
|
||||
File Format Extensions
|
||||
----------------------
|
||||
|
||||
The configuration file format has slightly been changed to accommodate the new
|
||||
manual order. Though, previous configurations are perfectly upwards compatible.
|
||||
|
||||
### New Header
|
||||
|
||||
A new header is used to flag a configuration file as being manually ordered.
|
||||
|
||||
```
|
||||
# ManualOrder : yes
|
||||
```
|
||||
|
||||
Once this is set alphabetical order is disabled and only the next techniques
|
||||
define the order of nodes.
|
||||
|
||||
### Changed `display` Semantic
|
||||
|
||||
Previously there were only two valid values for the `display` directive.
|
||||
(0 = Subprocess, 1 = Toplevel Process)
|
||||
|
||||
```
|
||||
display 0|1;<name>;<title>
|
||||
```
|
||||
|
||||
This has now been extended so that values greater than zero refer to the order
|
||||
of root nodes. (ascending)
|
||||
|
||||
```
|
||||
display 0|n;<name>;<title>
|
||||
```
|
||||
|
||||
### Significant Children Order
|
||||
|
||||
Previously the order of a node's children in a configuration file was not
|
||||
important in any way. Now this is significant and refers to the order in
|
||||
which children appear in the UI and how process states are determined.
|
||||
BIN
doc/screenshot/05_customize_node_order/0501_tiles_grab_tile.png
Normal file
BIN
doc/screenshot/05_customize_node_order/0501_tiles_grab_tile.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
BIN
doc/screenshot/05_customize_node_order/0503_tree_grab_header.png
Normal file
BIN
doc/screenshot/05_customize_node_order/0503_tree_grab_header.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
Loading…
Reference in a new issue