Hi all,
I am using Firefox to view the session (Ignition 8.1.52). On my view there is a button with enable binding linked to security. (true/false depending on if the user has all the necessary security levels). When i first logged in with the user with correct credentials, the button is still disabled. This binding seems to not update unless i navigate to another page and go back. Refreshing does not change anything. The issue persists where when i log out, the button is still enabled. The binding only updates if i navigate to another page and go back to original page.
No issue on chrome or edge.
You need to force a refresh the bindings of your objects when the security level changes.
Create a custom property in your view, bind the custom property to whatever session property changes depending on security level. This should be the same as what you already have, you should be just moving the binding to a custom property, producing a true/false result.
Add a change script to the custom property you just added to refresh the bindings of all other objects in the view. In the case of your button you can directly set the enabled property to true/false.
This is the simplest and most direct method. There are other methods which might be more scalable depending on the complexity of your user security schema.
Hi Lane,
Thanks for the response. I was using the custom property boolean (IsAuthorised) to figure out if user is authorized or not. This had an expression binding which took in an array of security levels and used util.security.isAuthorized to return true or false.
My issue was on chrome and edge, this worked perfectly. If a user log in/out, the binding was executed (i put a logger in the script to confirm) but on Firefox the binding was not re executing unless i switch pages.
You idea of forcing a refresh of binding gave me an idea of changing my binding to a expression structure with session user also as a input. This got around the issue where if the session user changed, forcing the execution of the binding script.
I believe the original issue is a genuine bug with firefox.