View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000039 | Oberon Platform | Context Design | public | 2011-05-01 15:08 | 2011-05-01 15:13 |
| Reporter | administrator | Assigned To | administrator | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.2 - DB build 0059 | ||||
| Target Version | 2.3 - DB build 0060 | Fixed in Version | 2.3 - DB build 0060 | ||
| Summary | 0000039: Tree view with Application Level as parent node | ||||
| Description | In Context design, we should have a tree view and have Application Level as parent node; so the ApplicationX will have under all admin objects associated with that application; with current solution we can only filter all admin objects | ||||
| Tags | No tags attached. | ||||
|
|
Added new level in the tree view; first node is the <All Elements> and collects all objects. If you define a menu item as application, a new node will be added to the tree; under this node will be reported all elements associated with this application. Every element form includes now the selection of the application to associate with the item; OOQL commands are also extended to define this new property and to filter with application name pattern. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-05-01 15:08 | administrator | New Issue | |
| 2011-05-01 15:12 | administrator | Note Added: 0000044 | |
| 2011-05-01 15:12 | administrator | Status | new => resolved |
| 2011-05-01 15:12 | administrator | Fixed in Version | => 2.3 build 0060 |
| 2011-05-01 15:12 | administrator | Resolution | open => fixed |
| 2011-05-01 15:12 | administrator | Assigned To | => administrator |
| 2011-05-01 15:13 | administrator | Target Version | => 2.3 build 0060 |
