Description
To avoid having to split up and shift around properties in my object payload, please support a standard "property" input as a typedInput. Same as the built in switch node, file, range, etc, nodes do
I would recommend, to keep this simple, it would default to msg.payload and would only support msg and JSONata.
Anyone who knows JSONata can use performance * availability * quality directly in the input property
Anyone who doesn't know or like JSONata, can use a math node or other nodes to compute the OEE value then pass it into the ui-text node
This means given this payload:
{
name: "Cooling Stage 1"
time: '16:00',
cycleCount: 800,
availability: 0.938,
performance: 0.933,
quality: 0.983
OEE, "86%"
productionHours: 8,
partCount: 700,
targetCount: 800,
scrap: 12
}
I can change this...
into this...
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Description
To avoid having to split up and shift around properties in my object payload, please support a standard "property" input as a
typedInput. Same as the built in switch node, file, range, etc, nodes doI would recommend, to keep this simple, it would default to
msg.payloadand would only supportmsgandJSONata.Anyone who knows JSONata can use
performance * availability * qualitydirectly in the input propertyAnyone who doesn't know or like JSONata, can use a math node or other nodes to compute the OEE value then pass it into the ui-text node
This means given this payload:
I can change this...
into this...
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate