How do you modify the properties of chart that exists inside a subflow? I need to create a subflow that has two graphs and two gauges. This subclow will be used at least 10-20 time thus the need to reuse the charts rather than create and maintain 40-80 charts and gauges individually.
These need to have the dashboard group and page properties set so that they can be laid out properly. These properties are not configured with free-form text fields and therefore I cannot use environment variables. Some have drop-down lists and I don't know how to set their value from outside the subflow or in the subflow configuration page.
Is there an example of setting chart and gauge properties from outside the subflow?
As you are new here, for the first few days you will be limited to how much you can post.
(Though I think you've been told that when you joined.)
Sorry, but the dumbest questions are the ones not asked.
WHY are you putting a chart node in a subflow?
Put all the workings in the subflow, sure. But the chart too?
If you do it this way, the charts can be where ever you want - by editing their details.
The subflows don't need that and so you have an output from the subflow to the chart.
Easier I think that way.
Up to you.
(Just something to share as you are new here.)
There are no RIGHT or WRONG ways to do things. So long as the job gets done.
But from what I've recently .... discovered is I was building all my flows a bad way.
Bad as in they weren't easy to update how they were laid out.
There are two ways to lay out a flow - of which I understand.
1 - the way I was doing it - is where you have the flows grouped into functional blocks where all the workings and (to call it) eye candy mixed up with one another.
2 - a better way - is to go one step further!
Sure, have these blocks, but also keep the workings SEPARATE from the eye candy.
As I just suggested with the subflow.
This way if ever you want to change the WORKINGS of a flow, you just migrate that part to where ever you want.
Then, hook up a few wires to the inputs and some from the workings block to the eye candy part/s.
The main reason for putting the charts in the subflow is that there will be many duplicates of the same gauges and charts but displaying different data from several different sensors. It's just code re-use. Rather than maintain and change the properties of 40 charts and gauges that are all the same, I'd rather have the properties in one location where a change to the segment colors or divisions can be edited once rather than having to edit 40 gauges and charts.
The layout is simple but need to put two charts and two gauges into one group. I have 10-20 groups to create all displaying data from different temperature and moisture sensors.
While I do have the logic for processing the data in a subflow, I was hoping there is a way to define the base properties of a chart and gauge once and then re-use those settings everywhere. I'd be able to update the gauge segments, colors, range once and have affect all of them.
Even if I could just lump the gauges and charts into a subflow by themselves and set the flow up from the data processing subflow to the display subflow would be great. The goal is to not have to maintain 20-40 separate charts and gauges individually when all their settings should be the same except for the page/group settings.
Only one group of charts and gauges are defined at the moment. Each sensor has a chart and a gauge for both Temp and Humidity. So with the 7 sensors, there will be 28 separate gauges and charts combined that need to sync'd except for the group and possibly page settings. Once I add more sensors, it's going to be nearly impossible to edit all the gauges and charts if I need to make a change and having to edit that many separately is prone to mistakes as well.
Each sensor will have it's own group on the dashboard that looks like this:
What I want to do is put the two charts and two graphs in subflow and just reuse that over and over, only changing the group/and page settings for each subflow. Thereby avoiding having to edit each manually. I'd just edit the subflow and all the sensors settings would sync instantly.
I'm strongly suggesting this because when you get more and more into this it will become evident of the benefits of doing it this/that way.
(Keeping the separate.)
Otherwise you want to update some of the workings and can't easily copy it to other flows/machines (what ever) without all the eye candy being mixed in with it.
Thanks for the ideas. It still doesn't help me when I need to make a change to 28+ charts and gauges. Ideally, I need gauge and chart template or a way to put the repetitive UI elements into a subflow and then reuse that single subflow multiple times, only changing the placement location data. Hm. Doesn't seem like there's a way to do that right now.
I am sure you can send template information to them with no problems.
You set the charts (eye candy) to receive template information.
So you edit 1 subflow, it propagates to all instances and the eye candy receives the templates and adjusts accordingly.
BTW: I am way down the learning scale. There are smarter people here.
Just - at this point - I guess I'm online.
I know it sounds painful what I'm saying.
(I can speak from your side of the coin very well)
But if you take the effort NOW - while you are still VERY NEW to it, I hope it won't enstill (how ever you spell it) bad habits with how you do things.
The suggested way is that all the template stuff is done at another level of the language and so you don't need to worry about it.
It would mean a lot of work inside the subflow, but not really much more than if you do it your way anyway. Just you are moving WHERE the work is done.
Before the eye candy or in the eye candy.
Sorry, I'm using that to make a demarcation line between the two types of nodes.
