|
Home > Archive > WebSphere HATS > September 2005 > iSeries menu as subfile - transform to links
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
iSeries menu as subfile - transform to links
|
|
| Debbie H 2005-07-20, 5:45 pm |
| I have a client who has iSeries menus implemented as subfiles instead of the
usual menu format. On top of that, the menu is 2 columns wide, not just a
single column. They would still like to have this 'menu' transformed with
the options rendered as links just like you would do with a 'selection list'
rule. I can't figure out how to do this with a subfile. Has anyone else
run across menus being done this way and how did you resolve? I'm not even
sure HATS 6.0 is capable of doing this.
Here is an example of what the menu looks like:
1 - Display Customer 4 - Display Item
2 - Work with Customer 5 - Work with Item
3 - Work with Order 6 - Display Order
Thanks for any suggestions.
Debbie
| |
| R Craig 2005-09-15, 2:45 am |
| Debbie H wrote:
> I have a client who has iSeries menus implemented as subfiles instead of the
> usual menu format. On top of that, the menu is 2 columns wide, not just a
> single column. They would still like to have this 'menu' transformed with
> the options rendered as links just like you would do with a 'selection list'
> rule. I can't figure out how to do this with a subfile. Has anyone else
> run across menus being done this way and how did you resolve? I'm not even
> sure HATS 6.0 is capable of doing this.
>
> Here is an example of what the menu looks like:
>
> 1 - Display Customer 4 - Display Item
> 2 - Work with Customer 5 - Work with Item
> 3 - Work with Order 6 - Display Order
>
>
> Thanks for any suggestions.
>
> Debbie
>
>
>
Just a wild shot, but maybe try using selection list instead of subfile.
Just looking at it, it doesn't **look** like a subfile, so I'd try a
different component.
If you want to disable subfile for just a few pages, you could just
customize just those menu pages. Remember, if there is some text that's
always on the menu pages, you can use that to recognize an entire class
of screens in a single customization.
|
|
|
|
|