#29 RAVEN Components to trigger creation of subblocks

[Anna Wojtowicz]

In RAVEN, Components have parameter fields called "controlled" and "monitored". First of all, these parameters should only have discrete values (defined by the YAML file), which is addressed by MOOSE Feature Request #11.

When a Component's "controlled" parameter is set, this means that a corresponding subblock should be added to the "Controlled" block of the tree. Currently in Peacock, when the controlled parameter is set on a particular Component, it asks if you'd like to add the corresponding subblock to the Controlled block, and opens a dialog for your to create the new subblock. Currently in NiCE, there is no automatic linking between Components and the Controlled block.

Similarly, if the "monitored" parameter of a Component is set, then a corresponding subblock should be added to the "Monitored" block of the tree. Peacock similarly links Components to the Monitored block.

Additionally, if a component is flagged as monitored, only then can the operator parameter of that component can be set, both on the actual component, and its corresponding subblock in Monitored. (Double check this last point - also verify that components can only be controlled or monitored, not both)