| How to Create a Formatted Table From SQL Data | Create Confluence page| Div |
|---|
|  Estimated Time: 2 min
|
Create In this step, you will create a Confluence page that will eventually contain the macro macros needed to produce the table. - Create a page named Products in a space accessible to the desired audience.
- Click the Unrestricted button to open the Page Restrictions screen.
- Click the Restrict editing radio button.
- Start typing confluence-administrators in the text box and select that group name from the list of suggestions to apply an edit restriction to that group.
 This restriction is being added so that Macro Security managed macros can be used. You will be configuring Macro Security in a later step. - Click Save to close the Page Restrictions screen.
- Click Save to save the new page.
| Adding page restrictions: Image Removed Image Added
|
|
| How to Create a Formatted Table From SQL Data | | Div |
|---|
| Estimated Time: 1 min |
Edit the Products page and do the followingIn this step, you will insert and configure the SQL Query macro, which is part of the SQL for Confluence (Pro Edition) add-on, to retrieve and format your data. Edit the Products page and do the following: - Insert the Chart SQL Query macro.Click the Chart macro container and click Edit so you can adjust
- Adjust its parameters as shown on the right.
- The Type Data source name parameter indicates to display a pie chart.
- The Width parameter indicates the width of the chart in pixels.
- The Height parameter indicates the height of the chart in pixels.
- The Display rendered data parameter indicates that a data table should be displayed after (below) the chart.
- The Chart Title parameter provides a title for the chart.
- The Content Orientation parameter indicates that the data will be derived from the data rows rather than the data columns. You will be defining the data in the next step when you configure the SQL Query macro.
- Click Save to save your changes to the Chart macro's parameters.
| Anchor |
|---|
| step2 | step2 | SQL Query macro parameters:
| Data source name | examplegeardb |
| Use database column labels | true |
| Show error if there are no rows | true |
Text to display when there are no rows | No rows selected- use the examplegeardb data source profile that you set up when installing the Examplegear database.
- The Use database column labels parameter indicates to use the column names defined within the SELECT statement (e.g., Product, Sell Start Date, Status) rather than the columns names defined within the database table(s) themselves.
- The Show error if there are no rows parameter indicates to show an error if no rows are returned in the resultset of the SQL query.
- The Text to display when there are no rows parameter indicates the text of the error message to be displayed when no rows are returned in the resultset of the SQL query.
- The Row styles parameter provides the CSS to format the table rows. This parameter is a comma separated list of styles, each of which can contain one or more properties. The first (and only) style is colored in blue to the right. Since only one style has been specified, it will be applied to the heading row. It formats it with a gray shaded background and a thick border around it.
- The Column styles parameter provides the CSS to format the table columns. This parameter is also a comma separated list of styles, each of which can contain one or more properties. The first style is colored in blue to the right, and it formats the first column with a yellow shaded background and a thick border. The second style is colored in green, and it formats the second column with a thick border but no shaded background. The third style is colored in red, and it indicates to apply the same style as was specified for the second column.
- Click Save to save your changes to the SQL Query macro's parameters.
With the cursor positioned inside the SQL Query macro container, paste in the SQL statements.
| Code Block |
|---|
| language | sql |
|---|
| theme | DJango |
|---|
| linenumbers | true |
|---|
|
SELECT
P.FullProductName AS Product,
P.SellStartDate AS 'Sell Start Date',
CASE
WHEN P.DiscontinuedDate IS NULL THEN '{status:colour=GREEN|title=Active}'
ELSE '{status:colour=RED|title=Discontinued}'
END AS Status
FROM Products P
ORDER BY 1; |
- All three columns in the resultset are specified with an alternate column name, e.g., Product, Sell Start Date and Status.
- The third column uses a CASE statement to turn the DiscontinuedDate into a Status macro indicating the product is active (if the DiscontinuedDate is null) or discontinued (if the DiscontinuedDate is not null).
SQL Query macro parameters: | Data source name | examplegeardb | | Output format | Wiki | | Use database column labels | true | | Show error if there are no rows | true | | Text to display when there are no rows | No data was found. | | Row Styles | background:#f0f0f0;color:#222;font-size:14px;border-bottom:black 3px solid;border-top:black 3px solid;, | | Column Styles | background:lightyellow;border-width:3px;border-color:black;border-style:solid;cellborder-width3px;,border-width:3px;border-color:black;border-style:solid;cellborder-width:3px;,2 |
Products page, in Edit mode: Image Removed Image Added |
|
| How to Create a Formatted Table From SQL Data | SQL Query | Div |
|---|
| Estimated Time: 2 min |
This step uses the SQL Query Cache macro, which is part of the SQL Cache for Confluence (Pro Edition) add-on, to retrieve the data that will be displayed in the pie chart. To configure the SQL Query ensure the page will render as quickly as possible. Although there is a small amount of data being retrieved in this recipe, it is a best practice to use the Cache macro to guard against slow load times and provide a better user experience when users view this page. To configure the Cache macro, do the following: - With the cursor positioned inside the Chart macro container, insert the SQL Query macro.
- Adjust its parameters as shown on the right.
- The Data source name parameter indicates to use the examplegeardb data source profile that you set up when installing the Examplegear database.
- The Use database column labels parameter indicates to use the column names defined within the SELECT statement (e.g., Product, Revenue) rather than the columns names defined within the database table(s) themselves.
- The Show error if there are no rows parameter indicates to show an error if no rows are returned in the resultset of the SQL query.
- The Text to display when there are no rows parameter indicates the text of the error message to be displayed when no rows are returned in the resultset of the SQL query.
- Click Save to save your changes to the SQL Query macro's parameters.
With the cursor positioned inside the SQL Query macro container, paste in these SQL statements: | Code Block |
|---|
| language | sql |
|---|
| theme | DJango |
|---|
| linenumbers | true |
|---|
| SELECT P.BaseProductName AS Product, ROUND(SUM(S.SubTotal)) As Revenue
FROM Sales S
INNER JOIN LineItems LI ON S.SalesID = LI.SalesID
INNER JOIN Products P ON LI.ProductID = P.ProductID
GROUP BY P.BaseProductName
ORDER BY 2 DESC;above the SQL Query macro, , insert the Cache macro.- Click the Cache macro container and choose Edit to adjust its parameters as shown on the right.
- The Cache refresh period parameter indicates that viewers will view a cached version of this page for 2 days. The first user viewing the page after that will trigger the refreshing of the cache.
- The Check attachments parameter indicates says that there is no no need to refresh the cache if any file attachments to the page are changed.
- The Show refresh icon parameter indicates to show an icon that a user can click to force an immediate refresh of the cache, without waiting for its expiration and automatic refresh after 2 days.
- The Show date parameter indicates to display the date the cache was last refresh.
- The Date format parameter indicates the format in which to show the date the cache was last refreshed.
- Click Save to save your changes to the Cache macro's parameters.
- Next, click the SQL Query macro container and drag it into the Cache macro container.
- Your screen should now look like the screenshot shown to the right.
- Click Save to save the Products page.
| SQL Query Cache macro parameters:| Data source name | examplegeardb | | Use database column labels | true | | Show error if there are no rows | true | | Text to display when there are no rows | No rows selectedCache refresh period
| 2d | Check attachments
| deselected | Show refresh icon
| selected | | Show date | selected | Date format
| EEE, MMM d, YYYY |
Products page, in Edit mode: Image Modified
|
|
| How to Create a Formatted Table From SQL Data | | Div |
|---|
| Estimated Time: 2-3 min |
Before you save the Products page, you should install the Macro Security for Confluence add-on (if you haven't do so already) and configure it with a property file that identifies who can run each security-enabled macro. Each macro security enabled macro accepts specific parameters to controls its use. This safeguards your Confluence instance and data from misuse or performance issues caused by inexperienced users or inappropriate use. Follow these steps to configure it: - Download the sample macro-security.properties file that is configured for moderate restrictions. This restricts most security-enabled macros so that only Administrators can execute them, but allows some others to be used by any user.
Review the file and ensure that the lines beginning with "sql-query.datasource.*", "run" and "run-now" are restricted to the confluence-administrators group as shown in the example configuration file to the right. - Save the file.
- In a new tab in your browser, create a Confluence page entitled Macro Security Configuration in a space accessible only to Administrators (or apply page-level restrictions so the page is accessible only to Administrators) and attach the file to it. Take note of the space key of the space. The space key appears in the URL of the page after you've saved, immediately after "display/". For instance, in the URL
http://wiki.examplegear.com/display/admin/Macro Security Configuration, the space key is admin. - Go to Manage Add-ons administration screen, locate the Macro Security add-on and click its Configure button. This will take you to the Macro Security configuration screen.
- In the Load Security Configuration section, supply the location of your macro-security.properties file, in the form of
spacekey:pagetitle^filename such as admin:Macro Security Configuration^macro-security.properties and click Load. - Select the Enable button and click Save.
| Example configuration file:| Code Block |
|---|
| language | text |
|---|
| theme | DJango |
|---|
| title | macro-security.properties file |
|---|
| linenumbers | true |
|---|
| # See the documentation space - https://bobswift.atlassian.net/wiki/display/CMSP
# More specifically:
# - managed macros: https://bobswift.atlassian.net/wiki/display/CMSP/Macro+Security+Managed+Macros
#
# Macro security is enabled/disabled from the UPM configure link for Macro Security for Confluence
# Property setting are loaded from the same configuration screen.
#
# Property settings here can restrict use of some powerful macro capabilities to trusted users
# while still allowing non-trusted users to view content created by using these macros
# - this is accomplished by requiring those pages using the restricted macros
# are controlled by trusted users
# - a page is controlled by having edit capabilities restricted to a group
# that is identified as being trusted in the properties file
# - a page is also considered to be controlled if it is in a permitted space
#
# Property file
# - The property file can be loaded from any file location on the Confluence server or from an attachment
#
# No specific configuration
# - Add-ons can implement their own rules if there is no specific configuration found
# depending on what they are restricting
# - Standard/default is
# - Configuration entry must be specified if the macro is restricted
# - *ANY can be used to allow all use (run is an example where *ANY is a likely use)
# - Some macros have additional, finer grained (parameter level) restrictions
# - these MUST also have something specified, otherwise macro use is not authorized
# - Some macros only restrict a specific parameter
# - these generally do not have to be specifically configured for use
#
# Property keys and values are case sensitive
#
# Property values are a comma separated list of groups or space names
# - the page edit restriction must match one of the groups listed
# - no other users or groups can be permitted to edit the page
# - use *ANY to indicate no restriction
#
# SQL - https://bobswift.atlassian.net/wiki/display/SQL
sql = confluence-administrators
sql.datasource.* = confluence-administrators
sql.datasource.testDS = *ANY
sql.limit = confluence-administrators
sql.disableAntiXss = confluence-administrators
sql.querytimeout = confluence-administrators
sql-query = confluence-administrators
sql-query.datasource.* = confluence-administrators
sql-query.datasource.testDS = *ANY
sql-query.limit = confluence-administrators
sql-query.disableAntiXss = confluence-administrators
sql-query.querytimeout = confluence-administrators
# Live template support - https://bobswift.atlassian.net/wiki/display/CMSP/Live+Template+Support
sql-query&live-template.datasource.* = *global
# Script - https://bobswift.atlassian.net/wiki/display/SCRP
beanshell = confluence-administrators
groovy = confluence-administrators
gant = confluence-administrators
jython = confluence-administrators
# HTML - https://bobswift.atlassian.net/wiki/display/HTML
html = confluence-administrators
xslt = confluence-administrators
# Run CLI Actions - https://bobswift.atlassian.net/wiki/display/CCLI
cli = confluence-administrators
cli.profile.* = confluence-administrators
cli.product.* = confluence-administrators
cli.directory.* = confluence-administrators
cli.datasource.* = confluence-administrators
include-remote = confluence-administrators
include-remote.profile.* = confluence-administrators
# Cache - https://bobswift.atlassian.net/wiki/display/CACHE
cache = *ANY
future = *ANY
future.timeout = confluence-administrators
# Run - https://bobswift.atlassian.net/wiki/display/RUN
run = confluence-administrators
run-now = confluence-administrators
run.disableAntiXss = confluence-administrators
# Advanced Tables - https://bobswift.atlassian.net/wiki/display/TBL
csv.url.* = *ANY
csv.disableAntiXss = confluence-administrators
json-table.url.* = *ANY
json-table.disableAntiXss = confluence-administrators
# Excel - https://bobswift.atlassian.net/wiki/display/XL
excel.url.* = *ANY
excel.disableAntiXss = confluence-administrators
# Flash - https://bobswift.atlassian.net/wiki/display/FLASH
flash.url.* = confluence-administrators
# Markdown - https://bobswift.atlassian.net/wiki/display/MARKDOWN
markdown.allowHtml = confluence-administrators
markdown-attachment.allowHtml = confluence-administrators
markdown-url.allowHtml = confluence-administrators
# Code Pro - https://bobswift.atlassian.net/wiki/display/CODE
code-pro.url = *ANY
code-pro.profile.* = confluence-administrators |
Macro Security Configuration page, after loading the macro-security.properties file: Image Removed Image Added |
|
| How to Create a Formatted Table From SQL Data | Save and test the page| Div |
|---|
| Estimated Time: 1-2 min |
Now, go back to the Products page and click Save to save it. You should now see a page that appears as shown on the right. The pie chart is shown, with the data table appearing after it. If you see an error such as "Error rendering macro 'sql-query' : com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException", then check the syntax of the SELECT statement within the SQL Query macro container. If you see an error such as "Error rendering macro 'sql-query' : Unable to connect to database", then verify that the SQL Query macro's Data source name parameter is set to the correct value and that the examplegeardb data source profile was set up per the installation instructions. | Products page: Image Modified |