How do i show / hide controls in the onDialogInitialize event?

[WindForce]

Hi
I have javascript code to dynamically show or hide panels, but i need to run it in the emitted javascript in the onDialogInitialize event.
In that event, i load data about a specific patient, and depending on the retrieved data, i need to hide one or two panel cards. How do i reference panel cards and navigator in the emitted javascript?

Thanks
Jaime

[lgrupido]

At the end of the onDialogueintialize event, you can run any JavaScript you want by setting e.javascript as in

e.JavaScript = "alert('hello');"

You can run ANY JavaScript that way, so just put your JavaScript code in there.

Is that what you are asking or is there something else?

[WindForce]

I know how to emit the javascript. I am asking how to access the controls, particularly the panel cards, in order to set some properties, but being in the onDialogInitialize event, i don't know if i can emit "{dialog.object}.panelGet('MYPANEL',true);" Does the panel "exist" at this point, or will it be constructed later?

[RichCPT]

I would NOT use onDialogInitialize to directly manipulate the display state of elements, I'm guessing they might not exist yet. If you are needing to evaluate state variables in that event that could be a problem too. I don't recall the exact problem of state variables, other than somewhere in my code (don't recall if it was Grid or UX) that I have to check for existence of state variables before running code that needs them. If they don't exist yet, I don't execute my JS. Fortunately, in what ever component I was working with, the Alpha JS library calls the event a second time before the component is rendered.

I would only use "onRenderComplete" to directly manipulate display state of elements. If you allow the Alpha JS library to open your UX a subsequent time from cache then make sure you copy the code from onDialogInitialize to the onSynchronizeDialog.

I mostly use client-side expressions to show / hide and otherwise change the appearance of controls. That way the code gets called at the appropriate time, albeit I think the code may get called also when it doesn't need to be called, but the user doesn't notice.

[lgrupido]

You can certainly TRY emitting that JavaScript in the initialize event. If it doesn't work, move it to onRenderComplete.

Note: in onRenderComplete all of the data will be in the UX, so you can use getValue to test the data if need be to determine what to show/hide.

[WindForce]

Note: in onRenderComplete all of the data will be in the UX, so you can use getValue to test the data if need be to determine what to show/hide.

Thanks that's what i was looking for, and that's why didn't use it in the first place.

[RichCPT]

Okay, but remember to do the same in "onSynchronizeDialog", if you allow the UX to be opened from cache.

P.S. For the most part, I gave up on trying to use Cached components. So, I almost always turn that off in the Action Javascript properties window.