Creating a new Px view

In core Niagara, a widget (label or chart) is associated with a data source (object) using a binding. This binding defines an ORD property that identifies the location of the object that updates and animates the widget. The framework replaces the ORD with a tag, which causes the binding to collect data from all points tagged with the same tag. You set up a Px View in Workbench to visualize framework data the same way you set up a regular Niagara Px View. This topic provides basic instructions using framework examples.
Prerequisites: You are working in Workbench and are familiar with how to use the PxEditor.
  1. Right-click your equivalent of a Logic folder, click Views > New View, and assign a view name.
    The New Px View window opens.
    Image
  2. Assign a View Name and click OK.
    The Edit view of the PxEditor opens.
  3. Right-click the canvas pane and click New > Label (or duplicate a similar label you already created) and expand the size of the label.
    The system creates an unbound label and populates the Properties tab at the bottom right corner of the Px Editor view and opens the Properties window for the Label.
  4. Click the add binding button (Image) at the top of the window.
    The Add Binding window opens.
    Image
  5. To an unbound label, select one of the analytics: bindings and click OK.
    • The analytics:Analytic Rollup Binding combines (rolls up) multiple instances of a value into a single value.
    • The analytics:Analytic Value Binding reports the current, real-time value of the point.
    The system associates the binding with the label and displays the binding properties.
  6. Scroll down in the Properties window until you see the binding properties for the analytics: binding you selected.
    Image

    The example shows the Analytic Rollup Binding properties. The first four properties: degradeBehavior, hyperlink, summary, and popupEnabled are familiar Workbench properties. The rest are unique to the framework.

    Any request (query) from the database requires you to configure at least the data source. The framework pulls data from one or more points with this tag.

    The other values are optional depending on the binding request. A value binding always deals with current values. The system ignores any setting of the rollup property for a value binding. An aggregation requires the starting node when aggregating multiple data sources. This node is usually a container that identifies a building or geographic location.

  7. Use the file finder button (Image) and component chooser to populate the data and node properties.
     NOTE: Unlike building a Px View in core Niagara, you do not select a point to establish an ORD. Your tag and node selections determine the point(s) to use. These properties take the place of a traditional ORD. 
  8. Do one or both of the following:
    • If you are configuring a rollup value based on historical data, click the rollup property, enable Use This Value, select (from the drop-down list) the function (count, first, last, avg, etc.) to use to roll up the data and click OK.
    • If you are aggregating multiple data sources, click the aggregation property, enable Use This Value, select (from the drop-down list) the function (count, first, last, avg, etc.) to use to aggregate all values into a single resulting value, and click OK.
    Both rollup and aggregation default to their preferred settings in the data definition that is associated with each tag.
  9. If you started this procedure from an unbound label, scroll up in the Properties tab, right-click text and click Animate.
    The Animate window opens with the default format set to %.%. In core Niagara you might configure this property to read %out.value%. The equivalent in the Niagara Analytics Framework is %value%.
  10. Change Format to %value% and click OK.
    The framework returns the value and not the point status.
 TIP: If the chart includes a large number of bindings, and some bindings yield small quantities of data (very near each other on the chart), the labels may overlap and become unreadable in a PDF. To fix this problem, increase the size of the chart to allow space for label placement without overlaps.