InetSoft Product Information: Axis Grid Formulation

AxisSpec.setGridStyle(value)

Specifies the style of the axis grid lines.

Parameter
 value
 a GLine value
Example (Report or Viewsheet)
 importPackage(inetsoft.graph)
 importPackage(inetsoft.graph.data)
 importPackage(inetsoft.graph.element)
 importPackage(inetsoft.graph.aesthetic)
 importPackage(inetsoft.graph.scale)
 importPackage(inetsoft.graph.coord)
 importPackage(inetsoft.graph.guide.form)
 
 var arr = [["State","Quantity"],["NJ",20000],["NY",30000]];
 dataset = new DefaultDataSet(arr);
 graph = new EGraph();
 var elem = new IntervalElement("State", "Quantity");
 var qscale = new LinearScale("Quantity");
 var aspec = new AxisSpec();
 aspec.setGridColor(java.awt.Color(0xff0000));
 aspec.setGridStyle(Chart.DASH_LINE);
 qscale.setAxisSpec(aspec);
 graph.setScale("Quantity", qscale);
 graph.addElement(elem);
demo
Read how InetSoft saves money and resources with deployment flexibility.

AxisSpec.setLabelVisible(boolean)

Specifies whether the axis labels are visible or hidden.

Parameter
 Boolean
 true if visible
 false if not visible
Example (Report or Viewsheet)
 importPackage(inetsoft.graph)
 importPackage(inetsoft.graph.data)
 importPackage(inetsoft.graph.element)
 importPackage(inetsoft.graph.aesthetic)
 importPackage(inetsoft.graph.scale)
 importPackage(inetsoft.graph.coord)
 importPackage(inetsoft.graph.guide.form)
 
 var arr = [["State","Quantity"],["NJ",20000],["NY",30000]];
 dataset = new DefaultDataSet(arr);
 graph = new EGraph();
 var elem = new IntervalElement("State", "Quantity");
 var qscale = new LinearScale("Quantity");
 var aspec = new AxisSpec();
 aspec.setLabelVisible(false);
 qscale.setAxisSpec(aspec);
 graph.setScale("Quantity", qscale);
 graph.addElement(elem);

AxisSpec.setLineColor(value)

Specifies the color of the axis lines.

Parameters
 value
 a java.awt.Color object
Example (Report or Viewsheet)
 importPackage(inetsoft.graph)
 importPackage(inetsoft.graph.data)
 importPackage(inetsoft.graph.element)
 importPackage(inetsoft.graph.aesthetic)
 importPackage(inetsoft.graph.scale)
 importPackage(inetsoft.graph.coord)
 importPackage(inetsoft.graph.guide.form)
 
 var arr = [["State","Quantity"],["NJ",20000],["NY",30000]];
 dataset = new DefaultDataSet(arr);
 graph = new EGraph();
 var elem = new IntervalElement("State", "Quantity");
 var qscale = new LinearScale("Quantity");
 var cscale = new CategoricalScale("State");
 var aspec1 = new AxisSpec();
 var aspec2 = new AxisSpec();
 aspec1.setLineColor(java.awt.Color(0xff0000));
 aspec2.setLineColor(java.awt.Color(0x00ff00));
 qscale.setAxisSpec(aspec1);
 cscale.setAxisSpec(aspec2);
 graph.setScale("Quantity", qscale);
 graph.setScale("State", cscale);
 graph.addElement(elem);

AxisSpec.setLineVisible(boolean)

Specifies whether the axis lines are visible or hidden.

Parameters
 Boolean
 true if visible
 false if not visible
Example (Report or Viewsheet)
 importPackage(inetsoft.graph)
 importPackage(inetsoft.graph.data)
 importPackage(inetsoft.graph.element)
 importPackage(inetsoft.graph.aesthetic)
 importPackage(inetsoft.graph.scale)
 importPackage(inetsoft.graph.coord)
 importPackage(inetsoft.graph.guide.form)
 
 var arr = [["State","Quantity"],["NJ",20000],["NY",30000]];
 dataset = new DefaultDataSet(arr);
 graph = new EGraph();
 var elem = new IntervalElement("State", "Quantity");
 var qscale = new LinearScale("Quantity");
 var cscale = new CategoricalScale("State");
 var aspec1 = new AxisSpec();
 var aspec2 = new AxisSpec();
 aspec1.setLineVisible(true);
 aspec2.setLineVisible(false);
 qscale.setAxisSpec(aspec1);
 cscale.setAxisSpec(aspec2);
 graph.setScale("Quantity", qscale);
 graph.setScale("State", cscale);
 graph.addElement(elem);

InetSoft Viewpoint

I think this is the critical part. Right now organizations are having to spend a lot of their resources on the integration of these different components and now are looking for complete BI platforms that can address all the BI needs they have. And what we find is that oftentimes we have found that business intelligence efforts are not successful, not because of the BI tools, themselves, necessarily, but because of the data they are forced to leverage and use.

BPM solutions are oftentimes not successful, not because of the business intelligence technologies themselves, but because of the information made available to users to make their decisions. And that’s why it is so important to have a holistic picture that addresses all of the different aspects of a BI solution. Because there is no such thing as a standalone BPM or BI solution. BPM tools are used to manage and enable you to drive specific business activities which require you to leverage information coming from across your organization.

And that’s why having the ability to aggregate and cleanse information across these different environments becomes so important. In addition, and what we have seen is that organizations are beginning to create separate operational data stores, set up different data marts and data warehouses to support all the needs they have across an organization.

Read why choosing InetSoft's cloud-flexible BI provides advantages over other BI options.