What's new
Render content from external sources with profiles
Administrators can now configure profiles which specify a set of parameters that can be used to access external data from other applications such as GitLab and GitHub. This access to external data by ensuring sensitive information, such as login credentials and access tokens, are hidden behind a pre-configured profile. Thus, users only need to provide the rest of the URL in the macro's settings to access the content that the relevant macro must process.
Profiles are created, updated, and deleted from the Configuration . Users can then select a pre-defined profile when configuring their table using the CSV Table or JSON Table macros. Once the profile is selected, users simply provide the URL of their CSV or JSON data through the macro configuration.
For more information about any of the app's configuration options, refer to the Admin guide.
Filter table data with regular expressions
Users can filter table data (through regular expressions) to display only desired information. Users can toggle on the Display data filter option from the macro settings to see a To learn more about regular expressions, refer to this article.
Enforce user-defined styles for rows and columns
Users can specify if the styes they define for rows and/or columns must be applied, regardless of default Confluence styles. Though users could define styles for header or data rows and/or columns in the macro's settings, there were some issues wherein the specified styles were not rendered completely on the Confluence pages.
Users can now avail the Apply column styles to data column cells option and the Apply row styles to data row cells option, under Column settings and Row formatting respectively, to make the styles persist for rows and/or columns on the pages. By default, these options are toggled off. Toggle either of these options on so that the specified styles are rendered in entirety for the rows and/or columns.
For more information about the app, refer to User Guide.
Blacklist pre-defined sites in Global Configuration
Administrators can choose to blacklist a pre-defined list of private networks, hosts or subnets to avoid Server Side Request Forgeries (SSRF) using the Blacklist domains configuration option.
By default, this option is disabled. If enabled, and if a request from any of the blacklisted sites is received, an error message is displayed. However, if users still need to access a blacklisted site, they must contact their system administrator to disable this option. Click the link named listed (in the description beneath the option) to view the pre-defined list of the most commonly blacklisted domains in a pop-up window.