Overview
This Component Plug-in provides the capability to display interactive charts in Appian using Google Charts. It offers support for the following types of charts:
Key Features & Functionality
These charts work on all Appian user interfaces and with the Appian mobile application. They are easy to configure and a sample application is provided as part of the download. The plug-in can be used to set up to provide interactive charts with drill-down capabilities and allow the event context to pass into any SAIL component(s) on the same or a different interface.
How to use the component:
2019 AppMarket Award Winner - Best Use of the Integration SDK
The charts have a "onSelection" option to save the selection from the chart. However, when testing it on the combochart it returns the row and column values. It's there a way to save the actual set of data selected? The original google charts api contains a getSelection() function, does this plugin have anything similar to return the data subset selected?
Also, the original Appian bar charts contain little marks next to the series to indicate where the text is aligned to each bar. Is there a way to activate this on this plugin?
Jose H. Additionally, Stacked Bar and Column charts are already available as Appian OOB that's why we have avoided adding redundant charts.The purpose of making this google chart plugin is to extend already available charting capability in Appian.
Hi Jose H. Yes you can create stacked bar/column charts by our google combo chart field where you have to just pass the following configuration to make it stacked -
chartOptions: {isStacked:true}
is there a way to create stacked bar/column charts with this? I've started playing with it but it seems to have many fancy options, except the main 2 which are bar charts and column charts. Is there a way to simulate a stacked bar/column chart with the given options?
Hi maxs just to correct the what said - We have used Visualizations API to render the chart.
The Google Chart API has two different implementations (Chart API and Visualizations API). Are you saying you are using "Chart API"? If so, then both the data and the chart configuration options are sent in the URL to Google, which they store on their servers for two weeks. That would not be acceptable for clients with sensitive data. Are you sure that this is the method you are using in this plugin? Is chart data sent in the URL to Google with this plugin?
Here is the explanation from Google located in the Google Charts API FAQ Support here: https://developers.google.com/chart/interactive/faq
What is the difference between the Google Chart API and the Google Visualization API?
The Chart API provides a simple way to create image charts of various kinds by sending a formatted URL that includes both the data and chart configuration options to a Google server. The Chart API includes a closed set of charts with various options. The Chart API datasets are limited to the size of a URL (roughly 2K).
The Visualization API provides a way to connect charts and data sources over the web and to publish them:
Is Google logging all my chart data?
The chart data included in the HTTP request is saved in temporary logs for no longer than two weeks for internal testing and debugging purposes. Of course you should understand that if your chart appears in an image tag on a public webpage, it could be crawled.
We are using Google Chart API. Regarding the data privacy policies of a chart, please find the same at Google charts documentation site of the respective chart.
Is this using the Google Chart API or the Visualisation API? There are two different flavors. The Chart API sends your data to Google to render the chart and return a result. The Visualisation API renders in the browser and does not send data to Google. In your plugin, is a the library installed and available to be rendered in the browser?
Thanks for your reply
No special deployment steps are required. Just place the component file in the standard plugin directory (<APPIAN_HOME>/_admin/plugins/).
Note: Please make sure you have static and dynamic content URL configured to use the custom component.