RWManipulationBuilder

Add Derived Metric to Dataset or Template through Derived Metric Editor

Used to add a new target to an already created template level selector, optionally creates new cgb node if the target is configured to have separate cgb nodes, if not then an already created cgb key and the newCGB flag as false needs to be passed.

end of template level selector manipulation and methods

Used to associate two template nodes to keep their filters synchronized or brushing and highlighting. There is no automation on backend for this, the client reads the associated nodes collection and decides what to do with it.

Used to clear template level selector associations, optionally removes the CGB node(s)

Convert a dataset to managed.

Edit Derived Metric on Dataset or Template through Derived Metric Editor

Grid Drill handler. requires RWInstance to be set for setting partial retrieval nodes

Handles selections of template level selectors, receives a collection of selections, creates an expression from it and applies it to a control node.

Used to convert a template level selector target from using shared cgb nodes to separate cgb nodes and vice versa. The manipulations are as follows: - From shared to separate: for each non first control remove cgb association (68) create a new cgb node (64) associate control with new cgb (67) - From separate to shared: for each non first control remove cgb association (68) remove cgb node (66) associate with first cgb (67)

Dissociates a control of a set of group by keys, and creates new cgb nodes and associates the selector to them. It is used when duplicating a vis that acts as a source of one or more targets that are configured to use separate CGB nodes

Set visualization as filter consists on two parts, one associating the nodes using associateNodes method and if the source visualization is being used as a filtering template, the selector/cgbNode relationship needs to be set. There are two types of selector/cgbNode/Target relationships, shared cgbNodes and separate cgbNodes: if the relationship is shared, each target has a unique CGB node that is shared with all the selectors pointing to that target, what happens in that case is that when a template updates the selection the CGB node expression is replaced by the last selection. If the relationship is separate, each selector has one CGB node for each target so when a selection is made on the source template the CGB node expression is set and the target will show the union of all the different CGB nodes targeting it.

For old VI documents that still use unit level selectors instead of template level selectors. It adds or removes targets to the CGB node.

Returns the boolean value from JSON object for the given prop(key). If the property is not present, throws an JSONException

Returns the int value from JSON object for the given prop(key). If the property is not present, throws an JSONException

Returns the JsonObject from the object passed for the given prop(key). If the property is not present, throws an JSONException

Returns the boolean value from JSON object for the given prop(key). If the property is not present, returns the optional boolean value passed

Returns the int value from JSON object for the given prop(key). If the property is not present, returns the optional int value passed

Returns the JsonObject from JSON object for the given prop(key). If the property is not present, returns the optional value passed

Returns the String from JSON object for the given prop(key). If the property is not present, returns the optional value passed

Returns the String from JSON object for the given prop(key). If the property is not present, throws an JSONException