Thanks for your encouraging comments, not needed indeed as I am learning as well by helping others with their use cases.
Go back to business. The workflow in HUB has been updated, I hope it covers all bullet points with the desired performance now. The main changes over the previous version are three (red marks in the picture):
- As previously commented, a ‘Rule Based Row Filter’ validates the Power Event Period on a pre-processing position; and replaces the two ‘Rule Engine’ nodes with the following rule (include TRUES):
( $Powered On_Period$ <= $${IREPORT_ID}$$ ) AND ( $Powered Off_Period$ >= $${IREPORT_ID}$$ ) => TRUE
TRUE => FALSE
This change #1 generates a problem, as a gap in time events continuity will not be reflected in the summary report when pivoting the REPORT_ID.
-
To solve this, an ‘Empty Table Switch’ allows to introduce an unique empty register in the loop step, that can be easily filtered in the reporting section.
-
This latest change #2 brings another undesirable effect, because the Summary Report’s ‘Pivot’ node changes the default resorting of the columns, giving priority to the unreferenced ones.
As we want the columns to be ordered chronologically in an automated way, and aiming to achieve a Time-Line format; a new branch has been added to feed the ‘Reference Column Resorter’ at the very end of the workflow.
That’s all from this side. Regards