I’m currently customizing the presentation in Discoverer Viewer and starting to work with the .uix format.
I have now only one single issue: I would like to show a tree collapsed when my page load.

This is the code responsible for showing it:

id="${uix.data.constants.PARAMETERS_HIDE_SHOW}"
name="${uix.data.constants.PARAMETERS_HIDE_SHOW}"
disclosed="${uix.eventResult.paramshs}"
rendered="${uix.eventResult.parametersRendered}"
text="${uix.data.nls['text.parameters']}">

This is the code for the event:

shortDesc="${uix.data.nls['text.go']}"
onClick="paramsbi_selectParams();">

The disclosed attribute sets if it is expanded (true) or collapsed (false). By default, the value ${uix.eventResult.paramshs} is true. After reading this artivle, I used the ! operator and set disclosed=”${!uix.eventResult.paramshs}” and it worked (it was collapsed on load)! Unfortunately, nothinng happened on click: the event didn’t work in this condition

I’d be glad if you could help me!
Best regards,

Ricardo Pinto.

I’m currently customizing the presentation in Discoverer Viewer and starting to work with the .uix format. I have now only one single issue: I would like to show a tree collapsed when my page load.

The code is:

id="${uix.data.constants.PARAMETERS_HIDE_SHOW}"
name="${uix.data.constants.PARAMETERS_HIDE_SHOW}"
disclosed="${uix.eventResult.paramshs}"
rendered="${uix.eventResult.parametersRendered}"
text="${uix.data.nls['text.parameters']}">

The disclosed attribute sets if it the tree is expanded (true) or collapsed (false). By default, the value ${uix.eventResult.paramshs} is true. After reading this article, I used the logical operator ‘!’ to get the logical not of the value. When I entered my page, it worked: the tree was collapsed! Unfortunately, the event didn’t work anymore (it never expanded)

This is the event code:

Could you help me on this?
Thanks in advance,

Ricardo Pinto

I’ve got 2 remarks; re the first item; I think you can get a cleaner separation of presentation (the way it looks) and behaviour if you move the rules (ie behaviour) that determine whether the button is displayed or not, out of the page and into a UI-helperbean-property. Let the getter for the property return a boolean indicating visible or not.

The same approach can be applied to the second item; the initialisation of the object that’s edited in the screen should belong in the controller, not in the view layer.

Don’t know how easy this can be realized using UIX and ADF, currently I’m looking at JSF where it’s rather straightforward. As Oracle’s JSF implementation (ADF-Faces) builds upon UIX I would expect it to be feasable…

Cheers, Hans