Skip to main content
Skip table of contents

Cloud and Data Center Differences

There are some feature discrepancies between PocketQuery for Confluence Cloud & Data Center. While the basic functionality remains the same across both versions, there are some differences when it comes to more advanced functionality. We are working on creating feature parity between the two. Please let us know if one of the features is urgent for you so you can help us prioritize them better.

Feature

Data Center

Cloud

Query Parameters (e.g.: :parameter)

(tick)

(tick)

Query Wildcards (e.g.: :@pageid)

(tick)

(tick) Wildcards starting with @user are not available in Cloud due to security and privacy restrictions. The @spacecategory wildcard is not available in Cloud (yet)

Custom REST Datasources

(tick)

(tick)

Basic REST Datasources

(tick)

(tick)

OAuth REST Datasources

(tick)

(tick)

Application Link Datasources

(tick)

⚠ This feature is not possible to implement in the Cloud.

SQL Datasources

(tick)

(tick)

Custom JDBC Drivers

(tick)

⚠ This feature is technically impossible in the Cloud. You can only use JDBC Drivers / Datasource Types that we have implemented. However, we are always adding new JDBC drivers / Datasource Types to our list. If you think there’s one missing, please let us know. Currently available JDBC Datasources:

  • Postgres

  • MySQL

  • MariaDB

  • MSSQL (Microsoft SQL Server)

  • Oracle

  • IBM DB2

  • SAP HANA

Custom Templates

(tick)

(tick)

Custom Template $PocketQuery Velocity API

(tick)

(tick) + More helpers than on DC and $PQ shorthand syntax. Unfortunately, Confluence context objects like $req that exist on Server are impossible to implement in the Cloud.

Custom Template PocketQuery JavaScript API

(tick)

⚠ Partially available. PocketQuery.load is not available yet.

Custom Template Charting API

(tick)

(tick)

Custom Template Velocity Version

Version 1.x

Version 2.x (more features)

Custom Template Errors in Debug Mode

(error)

(tick)

Custom Converters

(tick)

(tick)

Custom Converter Syntax

EcmaScript Version 5

EcmaScript Version 2020 (more features)

Custom Converter Errors in Debug Mode

(error)

(tick)

Custom Converter API

(tick)

(tick)

Render any Query result with the Default Template

(error) On DC, Query results must always be in a table layout. This often requires the use of a Converter.

(tick)

Add Query results to the Confluence search index

(tick)

(error) Not possible. Confluence Cloud is missing APIs needed to implement a feature like this.

PocketQuery Macro Debug Mode

(tick)

(tick) (+ more information than on Server)

PocketQuery Macro “Change Params Template”

(tick)

(tick)

PocketQuery Macro “Allow URL parameters”

(tick)

(error) Technically not possible on the Cloud platform.

Restricting Queries to spaces

(tick)

(tick)

Require dedicated spaces for queries

(tick)

(tick)

Custom PocketQuery Administrators & Editors Group

(tick)

(tick)

Import / Export of Entities

(tick) (Support of Server->Server)

(tick) (Support of DC->Cloud & Cloud->Cloud)

Copying Entities

(tick)

(tick)

PDF / Word Export

(tick)

(tick)

Nested Queries

(tick)

(tick)

Accept XML results from REST Datasources

(tick)

(tick)

Testing queries from within PocketQuery Administration

(tick)

(error) Queries currently need to be tested by adding the PocketQuery macro to a Confluence page

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.