Adding the Ignition Perspective Module to the Ignition platform gives users a. So, we can do a whole bunch of stuff from here. Ignition Perspective is a module for Ignition, the world’s first unlimited industrial application platform that empowers you to connect all of the data across your entire enterprise, rapidly develop any industrial automation system, and scale your system in any way. manipulate the value returned from the binding using any Python script you want. As long as this view's open, whenever the binding updates, we'll call our script. Ignition is made by Inductive Automation, based in Folsom, California. Now if we head back to the interface there, to kind of wrap up this little lesson here, this transform's almost like a property change script, if you think about it. And you can see, we're showing the same value that's on my tag on the component. So, how about in this case, we'll check to see if the value is greater than 100, if it is, we'll return the string "Too hot", otherwise just return whatever the value is. And, of course, the self argument which gives us a reference to the component this transform is on.
![inductive automation ignition bind to all interdfaces inductive automation ignition bind to all interdfaces](https://inductiveautomation.com/static/images/edge/Architectures/IgnitionEdge_Enterprise-StoreandForward@2x.png)
You can see that we do have a built-in value object that's defined up above, as well as quality and timestamp. And how about just a real simplistic example, move this down a bit, and maybe we can just test to see if our value's past a certain point. So, I'm going to make a little bit of room here. The whole point of using a Script Transform is to take the value from the binding or the prior transform, do something with it, and then return something. Based off the date, it's clear that this post is referring to Vision, but we would want to implement this across multiple modules, which certainly adds further complications. Additionally, you generally want to return something here. The amount of effort involved in refactoring the binding interfaces to allow multi-editing is fairly substantial. Now, the Script Transform is ultimately part of a function definition here, so you want to keep this gutter clear, or have everything indented over. And you can see we get a little interface to start typing some Python code. Technically, the Script Transform can do the same thing that those other transforms can do, but you have to write the code. The other transforms can do quite a bit, and have very simple interfaces. Now, in most cases, the Script Transform probably shouldn't be your go-to transform. Now the Script Transform will go and run a Python script, meaning you can do quite a bit. And we see I'm using a Tag binding, I'll add a transform, and we've selected the Script Transform.
![inductive automation ignition bind to all interdfaces inductive automation ignition bind to all interdfaces](https://docs.inductiveautomation.com/download/attachments/24445932/2019-06-03_17-06-33.png)
I'd like to apply a Script Transform just to talk about what it can do.
![inductive automation ignition bind to all interdfaces inductive automation ignition bind to all interdfaces](https://images.slideplayer.com/47/11649132/slides/slide_2.jpg)
This Label has its text property bound to this temperature Memory Tag. In this lesson, we'll take a look at the Script Transform.