Controls not addressable by "page.ui.get…" in 8.6

Ryan Miller

March 6, 2018 at 6:05 am #5021

Ever since upgrading to BPM 8.6 , I am unable to address controls in my browser Developer Tools console using the page.ui.get(“controlName”) syntax. I get the following error in Google Chrome:

TypeError: page is not defined

I have tried this in client side human service that I had upgraded from a previous version of BPM. And have also tried it in a brand new client side service with only a button on it.

Any clues?

 

SPARK Support

March 6, 2018 at 9:50 am #5022

Hi Ryan,

This is a weird issue.  If you inspect one of the elements, suddenly the page variable will be defined.

Regards,

Stephen P.

Ryan Miller

March 6, 2018 at 10:35 am #5023

Hi Stephen,

That is not working for me. Are you able to replicate?

SPARK Support

March 6, 2018 at 2:29 pm #5028

Hi Ryan,

I am able to replicate. Using BPM 8.6.0, I attempt to use the page variable, and it is not defined.  I then inspect an element on the page using the DOM explorer.  I am then able to reference page.ui.get(“controlName”).  (see attached screenshot)

Regards,

Stephen P.

Ryan Miller

March 6, 2018 at 2:40 pm #5031

Are you saying that the act of inspecting a DOM element somehow enables the page.ui.get…? I’m not sure that’s a workable solution.

We have found that the coach content is all inside of an iframe and can be (inconveniently) referenced this way:

document.getElementsByTagName(“iframe”)[0].contentWindow.page.ui.get(“Switch1”);

 

SPARK Support

March 7, 2018 at 8:21 am #5036

Hi Ryan,

Yes, clicking into the iframe is what enables the reference.  I usually start by inspecting the element as it also conveniently contains the full control name, including nested coach views and/or container references.

Regards,

Stephen P.