The help link appears to be broken. When I implemented something similar I had to add {attribute 'reflection} above the declaration of the FB with {attribute 'instance-path'} above the string VAR that would contain the path. Then wrote a function to trim off however much I wanted removed by searching for periods, then formatting it with spaces at the periods and removing brackets on arrays while also breaking up the PascalCase to present it a bit nicer for the end-users.
With the IIoT library/license or the one provided by the hardware OEM. Several examples online of how to use the MQTT Client SL library.
What do the details show? Is it requesting an online change or download? If the compile file is missing, it will request a download. Several things can trigger an online change, if you haven't changed the code, likely libraries. The details should provide some guidance.
Looking for a better way to manage Persistent Variables. We tend to have local vars in our FBs that need persistence through downloads as the systems are updated/altered on a regular basis. Retain would suffice if we had an easy mechanism to backup and restore like we can with Persistent variables and recipes. Although not having to remember that step with Persistent variables is preferred. We're running into issues with persistent storage capacity (WAGO PFC200) using the Persistent variable list...
You can write any expression that evaluates to TRUE/FALSE in that property, you can also call a method from the property.
I'm a fan of the analog indicators from ISA101. To recreate these, I use a number of rectangles that are dynamically sized and colored based on the input configuration. To keep it standard and easy, everything is built around 100px height. Then when instantiated in a frame, it can be resized as needed with the math remaining the same. The math logic is in a METHOD called by the rear most rectangle. These indicators do not use a "filling" bar graph, rather a fixed bar graph with a carrot to track...
Uninstalling and deleting all ProgramData manually, then re-installing appears to have fixed it.
WAGO will use 0-32767 as the raw units. Note a value of 3 means over/under range. Map that IO however you please, then scale in your program using any of the available libraries or with your own simple y=mx+b scaling formula to get to the engineering units you desire. Inverse for the AO to get back to 0-32767.