Page History
...
Using the example application system described in the previous section, we can visualize it as a series of independently accessible menus as follows:
...
...
| nopanel | true |
|---|
...
CUSWRK CUSREP ORDWRK
| | |
------------
...
-----
...
----- --------|-------
...
---
| | | | | | |
CUS001 CUS002 CUS003 CUS004 ORD001 ORD002 ORD003
¨ PROWRK PROREP TABWRK
| | |
| ---------- ----------
| | | | |
PRO0001 PRO002 PRO003 TBL001 TBL002
| No Format | ||
|---|---|---|
| ||
PROWRK PROREP TABWRK
| | |
| ------ ------
| | | | |
PRO0001 PRO002 PRO003 TBL001 TBL002 |
However, taking it one step further, by using the "process attachment" capability of LANSA (described in Other Processes on the Process Menu in the LANSA for i User Guide), we can quickly create a generalized "menu" (actually a new process called SYSMNU) for end users of this system. This could be visualized like this:
...
| nopanel | true |
|---|
...
SYSMNU
|
-------------------------------------------------------------------------------------------
...
| | | | |
CUSWRK | CUSREP | ORDWRK
| | | | |
----------- | ------------ | ------------|-----------
| | | | | | | | |
CUS001 CUS002 | CUS003 CUS004 | ORD001 ORD002 ORD003
| |
| |
PROWRK PROREP
| |
| ----------
| | |
PRO0001 PRO002 PRO003
One step further still, and a "tailored menu" can be created, say, for the accounting department. This "tailored menu" is actually another process called ACCMNU, and it can be visualized as follows:
...