Apologies for the vague title, I’m a bit stumped and not really sure what’s going on to accurately describe it.
I have an application where somebody else has developed a perspective application. This person had never used Ignition in any form before, did not spend a lot of time with any sort of documentation, and has created something…uhm…unique. I’m now tasked with working on it, and doing some modifications, and I can’t work out how they’ve actually made some things work.
The thing I’m most concerned about is that they’ve bypassed the application security and put together their own login screen of sorts. On this screen there are three objects: a text field for username entry, a password field for password entry, and an image that you click to “log in”. No actual login or authentication against any user source actually happens during this process - it’s simply a case that once you enter the correct user name and password, the “log in” button appears which will navigate to a certain “password protected” view.
The username entry field has no bindings on any of its components, no scripts, and no events. Likewise with the password field. However, when text is entered into these fields from a session, a memory tag shows the entered contents (yes, including the password, in plain text). These tags have no scripts associated with them.
During a session, the “log in” button (image) does not appear unless the user types in the correct user name and password (not “a” correct user name and password; one specific user/password combination). The image does not have any bindings for any components, so it’s not a simple visibility/size/position animation. It has no associated scripts, and only one event - an onClick event that runs a one-line script to show another view.
Using preview mode in the designer, none of this works. Text entered into the username/password field is not transferred to the memory tags, and the “log in” image is visible at all times.
There are no scripts or events associated with anything else on the view. There are no gateway event scripts, shared scripts or session scripts.
So how is all of this “working”? How does the text entered in the text fields make its way into the tags? How does the “log in” image component appear and disappear? Have they somehow modified the view’s source code outside of Ignition? How would I go about tracking down how all of this works?