Assigning an Alias to a Child UX

[Pizzadude]

Build 8301
I am opening a child UX from a button us Action Javascript Open a UX Component, and Use Cached UX Component is checked.

I want to execute client-side onRenderComplete in the child when it is opened.

This code apparently no longer works:

if(typeof window['ALIASNAME_R11_DlgObj'] != "undefined") {
[window['ALIASNAME_R11_DlgObj']._executeEvent('onRenderComplete');
}

I can't find the name of the window using Chrome debugger.

Has something changed? Is there an another method?

[CharlesParker]

That might be better answered by asking AA support directly. If they changed the naming convention it might be version specific, etc. Unless you can give us access to that page so we can dig into dev tools too I don't see any of us answering you to a helpful end...

[Pizzadude]

Here are some components to demonstrate this.
I have an alert in onRenderComplete in the child UX. It fires the first time the UX is opened, but not when opened the second time using the cached component.
I can find the child windows using ID 'A5dlg0'.
But window['A5dlg0']._executeEvent('onRenderComplete'); does not fire onRenderComplete in the child UX.
There is a second button in the parent UX that used to work. In fact I have that method working in my production app. But if I open and close the Open a UX Component, it stops working. So something has changed in the builder.

The goal is to fire onRenderComplete, or any other client-side events when the child component is opened cached.

TestChildAlias.zip

[CharlesParker]

sounds a lot like an unexpected change in behavior, you might be better off submitting this as a bug. There was a bug fix in the last build for delay render:

UX Component - List - Delay Render Till Visible - Now works more reliably when the List is in a Panel Card that is inside a Panel Navigator that is nested in a parent Panel Navigator.

It could be related...

[Pizzadude]

I submitted a bug report. Selwyn mentioned that Alpha may have made a change to the Open a UX Component action, and he provided a solution...

Instead of executing javascript from the parent UX to fire a client side event in the child, use the same code in the child UX's onSyncronizeDialog event.

if(typeof window['ALIASNAME_R11_DlgObj'] != "undefined") {
[window['ALIASNAME_R11_DlgObj']._executeEvent('onRenderComplete');
}

I don't think it is necessary to check if the window exists, because onSyncronizeDialog would not fire unless it does.

If you are using the method to fire client side events in a child UX from a parent UX, as in my first post, the next time you open the builder for Open a UX Component, it will generate new code and cause that method to fail.

So its kind of a sleeper bug.

[CharlesParker]

Yes we have seen that before, in the builder...good to know - and thanks! I wouldn't call it a bug per se in that is how it is supposed to work BUT it needs to be documented somehow as a warning - no suggestions though from me. I always wondered why it would generate a new alias instead of keeping it the same. Its a great reason to offload that type of code to a function that doesn't change rather than relying on a builder