Features Introduced in Previous Versions of Tableau Server

All Tableau Server Release Notes(Link opens in a new window) | All Known Issues(Link opens in a new window)

Added or changed in previous versions

Version 2021.2

Added in 2021.2

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New Tableau Desktop and Web Authoring(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Multiple analytics extensions in a site

Beginning with version 2021.2, you can now create multiple analytics extensions connections for each site. This means that organisations with different language or connection requirements can use analytics extensions on the same Tableau Server site, with different workbooks using different connections. For more information on analytics extensions, see Configure Connections with Analytics Extensions. Note: As of 2021.2, Einstein Discovery analytics extensions are still limited to one per site.

New Server service - Collections

Beginning with version 2021.2, a new service has been added to support the Collections feature. The new process is called the Collections service. For more information on what this service does and guidance on how to configure this process for multi-node installations, see Tableau Server Collections Service.

Collections are like playlists that let users organise content in a way that is meaningful to them. For more information on how to create and manage collections, see Organise Items in a Collection(Link opens in a new window) in the Tableau Desktop and Web Authoring Help.

Configure settings for extracts in web authoring

Beginning with version 2021.2, you can configure settings for extracts that you create in Web Authoring. Optionally, configure options to tell Tableau how to store, define filters for and limit the amount of data in your extract. For more information, see Create Extracts on the Web.

Streamlined site settings for Ask Data

Streamlined site settings for Ask Data now disable or enable the feature site-wide for all data sources. If it's enabled site-wide, indexing frequency remains customisable for each data source. For more information, see Disable or Enable Ask Data for a Site.

Bring Einstein Discovery predictions into your Prep flows on the web

Beginning with version 2021.2, you can bring prediction models built in Einstein Discovery directly into your Prep flows on the web.

Note: You must have a Salesforce licence and user account that is configured to access Einstein Discovery to use this feature.

With the power of machine learning and artificial intelligence, you can bulk score your flow data and generate new fields for predicted outcomes at the row level, as well as add top predictors and recommended improvement fields to include data about which fields contributed to the predicted outcome. Add a Prediction step to your flow, sign in to Einstein Discovery, choose from deployed models and apply them to your flow data. Then generate your flow output and use the new data source to analyse the predicted outcomes in Tableau. This feature was first introduced in Tableau Prep Builder in version 2021.1.3. For more information, see Add Einstein Discovery Predictions to your flow(Link opens in a new window) in the Tableau Prep help and Create and Interact with Flows on the Web.

Share explanations from Explain Data in published dashboards

Explain Data has a reimagined user interface optimised for a broader audience of business users. Authors (Creators or Explorers with editing permissions) can now enable Explain Data for viewers of dashboards and sheets in published workbooks. Viewers can select a mark of interest in the view and run Explain Data to explore their data more deeply than before.

Access to Explain Data in viewing mode is not enabled by default, so authors will need to enable this option. For information on how to enable Explain Data in viewing mode, see Enable Explain Data in viewing mode in published workbooks and dashboards.

For more information on Explain Data, see Discover Insights Faster with Explain Data, Get Started with Explain Data and Control who can use Explain Data and what they can see.

Daily removal of embedded external assets without downstream connections

Beginning with version 2021.2, a backgrounder job for Tableau Catalogue (or Tableau Metadata API) runs daily by default to delete embedded external assets without downstream connections to Tableau content. For more information, see features.DeleteOrphanedEmbeddedDatabaseAsset and databaseservice.max_database_deletes_per_run.

New Subscription jobs configuration key

Beginning in version 2021.2, a new configuration key, backgrounder.timeout.single_subscription_notify, changes how you configure the maximum time to complete for single subscription jobs. For more information, see "New configuration key for setting maximum time for single subscription job" in What's Changed in 2021.2.

Configure custom OAuth

You can now configure custom OAuth clients for a site to 1) override server-wide OAuth client settings if configured for the server or 2) enable support for securely connecting to data that requires unique OAuth clients. For more information, see Configure custom OAuth for a site.

Add-ons

Tableau Catalogue – part of the Data Management Add-on

Add Field Descriptions - You can add descriptions for fields in a published data source that then display in the Description column on the data source page Lineage tab. You can also see the description on the Data tab when you build a visualisation. For more information, see Describe fields in a published data source in the Tableau Desktop and Web Authoring Help.

Data Quality Warning Updates

  • Formatted text support for warning messages - When you create or edit a data quality warning message, you can format the text with bold, underline and italics and include a link or an image. For more information, see Set a Data Quality Warning.
  • Message required for warnings - When you create a data quality warning, you're now required to enter a message to display to users. (This doesn't apply to warnings generated when you set Tableau to monitor for extract refresh or flow failures.) For more information, see Set a Data Quality Warning.

Inherited descriptions appear in Tableau Desktop - When a description for a field exists upstream from the field, it now appears in Tableau Desktop with information about where the description is inherited from. For more information, see Describe fields in a published data source in the Tableau Desktop and Web Authoring Help.

Full table name appears - The table's full name has been added to the table page.

Filter by tags - You can now filter databases, files and tables by tags in the Connect To dialog box.

Filter by embedded or non-embedded - On the External Assets page, you can filter databases, files and tables by asset category: embedded or non-embedded.

Resource Monitoring Tool – part of the Server Management Add-on

Automated Process Discovery

Resource Monitoring Tool now supports hot topology changes on Tableau Server and automatically updates the processes information. You no longer have to configure the process information manually.

CLI support for Environment setup

New CLI commands are available to allow you to configure a new environment during installation or updating an existing environment. Previously, you had to use the web interface to configure the Environment. Here are the new commands related to Environment setup:

  • rmtadmin create-env: Creates a new Environment
  • rmtadmin update-env: Updates an existing Environment:
  • rmtadmin bootstrap-file: Downloads the bootstrap file to register Agents.

For more information, see Install the RMT Server Using Command Line and rmtadmin Command Line Utility.

New CLI commands

Several new CLI commands have been added to support environment setup and management. Here is a list of all the new commands added in this release:

  • rmtadmin agents: Lists all the registered Agents on Tableau Server nodes for all environments.
  • rmtadmin create-env: Creates a new Environment
  • rmtadmin bootstrap-file: Downloads the bootstrap file to register Agents.
  • rmtadmin cleanup: Deletes the log files that are older than a certain number of days.
  • rmtadmin delete-env: Deletes a specific environment and all data that has been collected for that environment.
  • rmtadmin delete-server: Deletes the configuration information of the Tableau Server node from the environment, deregisters the Agent on that node and deletes all monitoring data collected specific to that node.
  • rmtadmin delete-server-data: Deletes the data collected from one or more Tableau Server nodes.
  • rmtadmin deregister-agent: Deregisters the Agent from the environment.
  • rmtadmin environments: Lists all the environments.
  • rmtadmin servers : Lists all the Tableau Server nodes across all environments or a specific environment.
  • rmtadmin test-env: Tests the various connection points between and Tableau Server.
  • rmtadmin update-env: Updates the environment settings.

For more information, see rmtadmin Command Line Utility.

Node Selector

If you have more than 5 Tableau Server nodes, you will now be able to navigate and filter by nodes. Previously, the Tableau Processes chart only showed information for 5 nodes.

Agent Compatibility

Resource Monitoring Tool Agent should be on the same version as the Master Server or a compatible version. If you have one or more Agents on a non-compatible version, an incident will be logged and reported. For more information, see Agent Incidents.

External Repository - part of the Server Management Add-on

You can now configure a stand-alone PosgreSQL database instance as the External Repository for Tableau Server. For more information, see Create a PostgreSQL Database as a Stand-alone Installation

Content Migration Tool – part of the Server Management Add-on

Content Migration Tool now supports personal access tokens as an authentication method for your source and destination servers. For more information, see Migration Plans: Servers.

Changed in 2021.2

Version 2021.2 includes the following changes you should know about before upgrading.

Encrypted communication channel with Active Directory is required

Beginning with Tableau version 2021.2, Tableau Server no longer allows insecure connections with Active Directory. If your current instance of Tableau Server is communicating with Active Directory over a non-encrypted channel, upgrade will fail.

Run the following command to allow an insecure connection on your current version of Tableau Server before you upgrade:

tsm configuration set -k wgserver.domain.allow_insecure_connection -v true --force-key

After upgrade completes, we recommend securing the channel and then setting this option to false.

Note: By default (when wgserver.domain.allow_insecure_connection is set to true), Active Directory group synchronization will fail if the communication channel with Active Directory is not encrypted.

Secure SAML configuration is enforced

Beginning with version 2021.2, Tableau Server enforces secure SAML configuration for Server-wide and Site SAML.

Signature algorithm The certificate that you configure for SAML must use a secure signature algorithm, for example SHA-256. If you attempt to upgrade Tableau Server with a SAML certificate that uses SHA-1 signature hash, upgrade will fail.

We recommend that you upload a new certificate with SHA-256. See Update SAML Certificate.

Alternatively, you can configure Tableau Server to accept the less-secure SHA-1 hash by setting the tsm wgserver.saml.blocklisted_digest_algorithms configuration key.

RSA key and ECDSA curve sizes The certificate used for SAML must either have an RSA key strength of 2048, or ECDSA curve size of 256. If you attempt to upgrade Tableau Server with a SAML certificate that uses less-secure key or curve sizes, upgrade will fail.

We recommend that you upload a new certificate with more secure key or curve size. See Update SAML Certificate.

Alternatively you can configure Tableau Server to accept the less-secure sizes by setting the respective configuration keys, wgserver.saml.min_allowed.rsa_key_size and wgserver.saml.min_allowed.elliptic_curve_size.

Site SAML secure configuration verification

This release includes an updated tabcmd utility with the validateidpmetadata command. The validateidpmetadata command will scan your existing SAML sites and identify the signature algorithms and key sizes that are configured for each site. See validateidpmetadata.

Tableau Server on Windows installer logging changes

Beginning with Tableau Server 2021.2, due to internal changes to the installer, the logging behaviour by the Tableau Server installer program has changed if you use the /log switch on the command line.

Prior to version 2021.2 you could use the /log switch to specify a log file name without a path, and the file was written to the current working directory. Starting in 2021.2, if you do not also specify a path, the file will be written to a temporary location that is deleted when the installation is done. If you use the /log switch, you must also specify both the path and the log file name in <name>.<ext> format if you want to preserve the log. If you do not include a file name, the installer will ignore the switch and save the log to %TEMP%.

The behaviour is unchanged if you do not use the /log switch: the installer log is created in the logged in user's temp directory, %TEMP% using a naming convention of Tableau_Server_<version_code>.log.

For more information on command line switches for the installer, see Install Switches and Properties for Tableau Server

Tableau Prep Flow Service has been renamed to Tableau Prep Minerva Service

Beginning with version 2021.2, the Tableau Prep Flow Service (flowqueryservice) has been renamed to the Tableau Prep Minerva Service (flowminerva). This process appears on the TSM Status page and in the output of the TSM command tsm status -v. For more information, see Tableau Server Processes.

New configuration key for setting maximum time for single subscription job

Beginning in version 2021.2, you now set the maximum time to complete a single subscription job using the new backgrounder.timeout.single_subscription_notify configuration key. This key replaces use of the backgrounder.timeout_tasks key for configuring timeouts on single subscription jobs. As of version 2021.2 the backgrounder.timeout_tasks key no longer uses the single_subscription_notify option. For more information, see backgrounder.timeout.single_subscription_notify.

Version 2021.1

Added in 2021.1

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New Tableau Desktop and Web Authoring(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Integration of Einstein Discovery Predictions

Beginning with version 2021.1, you can integrate predictions directly into Tableau views and dashboards using models deployed by Einstein Discovery in Salesforce. For an introduction to Einstein Discovery in Tableau, see Integrate predictions from Einstein Discovery into Tableau in What's New in Tableau Desktop and Web Authoring help. Also see the Einstein Discovery in Tableau(Link opens in a new window) page and demo(Link opens in a new window) on tableau.com(Link opens in a new window).

To use Einstein Discovery predictions on Tableau Server, some server configuration is required. For more details, see Configure Einstein Discovery Integration. For information on required licenses, access and permissions in Salesforce and Tableau, see Requirements for access(Link opens in a new window).

For information on how to configure and use Einstein Discovery predictions in workbooks and dashboards, see Integrate Einstein Discovery Predictions in Tableau(Link opens in a new window) in Tableau Desktop and Web Authoring help.

Server authorisation-to-run (ATR) service

Server authorisation-to-run (ATR) enables you to activate Tableau Server in any cloud, container, or virtual environment without being impacted by underlying hardware changes that lead to maximum activation errors. For more information, see Activate Tableau Server using the authorisation-to-run (ATR) service(Link opens in a new window).

Zero downtime licensing

With zero downtime licensing, you can apply most licensing changes to Tableau Server without needing to restart when licence end dates, capacity or installed features change. For more information, see Zero downtime licensing(Link opens in a new window).

Specify ports that should not be used during dynamic port allocation

Use the new configuration key ports.blocklist to specify ports in the dynamically assigned range that should not be used by Tableau. Setting this key with specific ports will cause Tableau Server to not use the ports when dynamically assigning ports on start up. For more information, see Blocking specific ports within the range.

Block ingestion of complex content

Use the tsm configuration set command option metadata.ingestor.blocklist to troubleshoot content ingestion issues with Catalogue or Metadata API. For more information, see metadata.ingestor.blocklist.

Use personal access tokens for admin impersonation

Beginning with version 2021.1, you can enable Tableau Server personal access token impersonation. In this scenario, access tokens that are created by server administrators can be used for user impersonation when using the Tableau Server REST API. See Server administrator impersonation.

Backup performance improvements

Beginning with version 2021.1, you can increase the number of threads the tsm maintenance backup command uses. This can significantly improve performance if your hardware supports it. Our testing suggests that the default option provides the best results. However, should you choose to go beyond the default multithreading option, you should limit the number of threads to the number of virtual processors on the computer, up to a recommended maximum of four. To increase the number of threads, set the backup.zstd.thread_count configuration key, and use the --multithreaded option with the tsm maintenance backup command. For more information about backing up Tableau Server, see Back up Tableau Server data.

New Server Process – Content Exploration Service

Beginning with version 2021.1, a new server process has been added to enhance the searching and navigation capabilities in Tableau Server. The new process is called the Content Exploration Service. For more information on what this service does, and guidance on how to configure this process for multi-node installations, see Tableau Server Content Exploration Service.

Redesigned notifications centre now includes notifications for sharing and comments

Users can now see notifications for new comments and shares by selecting the bell icon in the top right corner of their Tableau site. The redesigned notification centre also displays updates for flows and extract jobs. Users can also control where they receive notifications in their Account Settings – directly in Tableau, by email or both. To configure notifications for all site users, turn on notifications in Settings under Manage Notifications. For settings information, see Site Settings Reference. For more information on this change, see Changed in 2021.1.

Add-ons

Azure Key Vault - part of the Server Management Add-on

Tableau Server can use an Azure Key Vault as a Key Management System (KMS) beginning with version 2021.1. This requires the separately licensed Server Management Add-on for Tableau Server. For more information, see Azure Key Vault.

External File Store and External Repository – part of the Server Management Add-on

Enhanced snapshot backup – If you have both External File Store and External Repository configured for your Tableau Server, you now have additional options to manage backup and restore of your Tableau Server data. For more information, see Backup and Restore with External File Store.

Note: Beginning with Tableau Sever 2021.1, if you have both External File Store and External Repository enabled, Tableau Server Backup process no longer includes creating a backup file of the repository by default. If you are upgrading from a version earlier than 2021.1, and you have scripts to run or schedule your backups, and want to continue to include the repository backup, see Option 1: Include Repository in the Backup.

Resource Monitoring Tool – part of the Server Management Add-on

  1. Performance improvements – The Resource Monitoring Tool can now provide real-time performance reporting for a Tableau Server deployment serving up to 5,500 views per hour.
  2. Filters – New filter options are available in the web interface to improve navigation and help explore event monitoring.
  3. SSL configuration for Tableau Server Repository – You can now configure secure encrypted communications between Resource Monitoring Tool and Tableau Server Repository database. For more information, see Encrypted Data Collection.

Tableau Catalogue – part of the Data Management Add-on

Automated data quality warning – You can set Tableau to monitor for extract refresh failures and for flow run failures. When a failure occurs, Tableau generates a data quality warning that displays to users. For more information, see Set a Data Quality Warning.

Quick search results expanded – Quick search results now include tags on external assets.

Changed in 2021.1

Version 2021.1 includes the following changes you should know about before upgrading.

Change in default behaviour for snapshot backups

Note: If you have both External File Store and External Repository enabled and use scripts to do backups, this can potentially result in not having a backup of the repository.

Beginning with Tableau Sever 2021.1, if you have both External File Store and External Repository enabled, the Tableau Server backup process no longer includes creating a backup file of the repository by default. If you are upgrading from a version earlier than 2021.1, and you have scripts to run or schedule your backups, and want to continue to include the repository backup, see Option 1: Include Repository in the Backup.

SHA-256 hash algorithm enforced for SAML assertions with IdP

Beginning with Tableau Sever 2021.1, Tableau Server will hash message signatures and digests with SHA-256 in SAML assertions to the IdP. To change this behavior, see wgserver.saml.sha256.

New SAML configuration keys

Beginning with Tableau Sever 2021.1, Tableau Server includes three new SAML configuration keys:

  • wgserver.saml.blocklisted_digest_algorithms:Specifies the digest algorithms that are not allowed as part of certificates used in SAML configuration or for signing SAML assertions. When set, assertions that are signed with a blocklisted algorithm will fail and certificates containing a blocklisted digest algorithm will fail. We recommend blocking the SHA-1(SHA1) algorithm. Before blocking SHA-1, confirm that your SAML certificates digest algorithms are not SHA-1, and that your SAML IdP does not sign messages with SHA-1.

  • wgserver.saml.min.allowed.elliptic_curve_size: Specifies the minimum elliptic curve size required for ECDSA certificates that are uploaded and configured for Tableau Server. If Tableau Server is configured with an ECDSA certificate that does not satisfy this minimum curve size, Tableau Server may go into a degraded state. If you attempt to upload a certificate that does not meet the minimum curve size, Tableau Server will reject the certificate. We recommend a minimum curve size of 256.

  • wgserver.saml.min.allowed.rsa_key_size: Specifies the minimum key size required for RSA certificates that are uploaded and configured for Tableau Server. If Tableau Server is configured with an RSA certificate that does not satisfy this minimum key size, Tableau Server may go into a degraded state. If you attempt to upload a certificate that does not meet the minimum key size, Tableau Server will reject the certificate. . We recommend a minimum key size of 2048.

In future releases of Tableau Server, these keys will be configured with secure minimum defaults, as specified in the recommendations above. In future releases, if your SAML configuration is not configured with the minimum requirements, SAML functionality or upgrade may fail. In the meantime, we recommend that you update your SAML configuration to be in compliance with the recommendations above.

Client and CA certificates used for mutual SSL must meet minimum security requirements

Beginning with Tableau Server 2021.1, Tableau Server configured for mutual SSL authentication will enforce secure certificate requirements.

Client and certificate authority (CA) certificates used for mutual SSL must either have an RSA key strength of 2048, or ECDSA curve size of 256.

Tableau Server will fail mutual authentication requests from client certificates that do not meet these requirements.

Additionally, upgrade of Tableau Server will fail if the certificate authority (CA) certificate that is configured for mutual SSL does not meet these requirements.

Improvements to JVM maximum heap size scaling for Tableau Catalogue ingestion and elastic server

Beginning with Tableau Sever 2021.1, JVM maximum heap size scales automatically for Catalogue ingestion and elastic server. For more information, see noninteractivecontainer.vmopts and elasticserver.vmopts.

Old notifications do not appear in new notifications centre

When you upgrade to Tableau Server 2021.1, old notifications will not appear in the new notifications centre. All existing email notifications will continue. To continue tracking older notifications, make sure the server setting for Notifications for Extract Jobs and Flow Runs is enabled before upgrading. For more information, see What's New and Changed in Tableau Server.

 

Version 2020.4

Added in 2020.4

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Enable and configure Catalogue or Metadata API indexing limits for content

Use the following tsm configuration set command options to enable and configure Catalogue or Metadata API indexing limits, also called event throttling, for new and updated content across all sites:

Activate and register multiple product keys

Beginning with version 2020.4.0, you can activate and register multiple product keys during installation. Tableau Services Manager checks licensing levels (cores versus product keys) and licence types (creators versus explorers and viewers) to ensure the installation can be completed due to licensing. You can apply additional product key(s) to Tableau Server if necessary, to achieve the desired number or creator, explorer and viewer seats, cores and features to accommodate user capacity. For more information, see Activate and Register Tableau Server.

Configure Tableau Server for offline maps

Beginning with version 2020.4.0, you can configure Tableau Server to use offline maps that are installed with Tableau. To do this, set the vizqlserver.force_maps_to_offline configuration key to true and apply pending changes. For more information, see Displaying Maps in an Air-Gapped Environment.

Turn off Web Page objects

To prevent Web Page objects in dashboards from displaying target URLs, do either of the following:

  • For a specific site, deselect Enable Web Page Objects in the site settings.
  • For an entire server, set the vizqlserver.web_page_objects_enabledconfiguration key to false.

Improved control of extract query workloads

You can now fine tune extract query workload management in a multi-node deployment by using the new node role, extract-queries-interactive. For more information, see Workload Management through Node Roles. To use this feature, you must have a valid Server Management Add-on licence activated on your Tableau Server.

Automatic configuration of query cache size

The size of the query cache is now automatically set based on the amount of available system memory. This improves the number of query results that will fit into the cache by default. For more information, see General Performance Guidelines.

The default query cache settings are suitable for most situations but it is possible to manually configure them using the TSM command line interface. The TSM settings are: native_api.InitializeQueryCacheSizeBasedOnWeights, native_api.QueryCacheMaxAllowedMB, native_api.LogicalQueryCacheMaxAllowedWeight, native_api.MetadataQueryCachMaxAllowedWeight, native_api.NativeQueryCacheMaxAllowedWeight and native_api.QueryCacheEntryMaxAllowedInPercent. For more information, see native_api.InitializeQueryCacheSizeBasedOnWeights.

Custom sign in note appears for server sign in errors

In 2020.4, sign in page notes added to the Sign In Customisation setting will also appear when a user receives a sign in error, such as when a user attempts to log in with SSO (SAML, Site SAML and Open ID). Server administrators can use this note to help users understand how to get a licence or why they can’t access a site. For more information, see Customise Your Server. For more information, see Customise Your Server.

New processes related to Tableau Prep flows

The 2020.4 release adds some new processes to Tableau Server. The Tableau Prep Flow Authoring (floweditor) and Tableau Prep Flow Service (flowqueryservice) processes now appear on the TSM Status page and in the output of the TSM command tsm status -v. For more information, see Tableau Server Processes.

Ask Data Usage and Adoption admin view

You can now see how users engage with Ask Data on a site, using the new Ask Data Usage admin view. The dashboard highlights the top Ask Data users, data sources and data source owners, along with headline value metrics. For more information, see Ask Data Usage.

New tsm schedules commands

Version 2020.4.0 introduces new commands for managing scheduled jobs. For this first release you are limited to using the tsm schedules commands with backup jobs, but our intent is to expand the scope of these commands in future releases of Tableau Server. For more information, see Scheduling and Managing Backups, tsm schedules, and tsm maintenance backup.

Checkpoint upgrades

Enhancements to the upgrade-tsm script give server administrators more options when faced with a failed upgrade. For more information, see "Changed in 2020.4" below.

Additional dynamically configurable keys for logging

Dynamic configuration was introduced in version 2020.2, and version 2020.3 added dynamically configurable logging options to those made available in 2020.2.0. Version 2020.4 continues to build on this with two new keys. When you make configuration changes with these keys, or configuration changes with these keys in combination with Tableau Server Dynamic Topology Changes, you do not have to restart Tableau Server.

New dynamically configurable keys in 2020.4:

  • tomcatcontainer.log.level
  • vizportal.log.level

For details viewing dynamically configurable keys, see tsm configuration list-dynamic-keys. For more information about the introduction of dynamic configuration in version 2020.2, see Dynamic Configuration. For more on changing logging levels, see Change Logging Levels.

Create extracts on the web

Now you can create extracts directly in web authoring, without using Tableau Desktop. For more information, see Create Extracts on the Web. You can extract new workbooks in addition to existing workbooks. Optionally, the extract creation can run in the background and you can be notified when it's completed. This will let you close your authoring session while the extract is being created, which can be helpful with large extracts that might take a long time.

Create and interact with flows on the web

You can now create flows to clean and prepare your data using either Tableau Prep Builder, Tableau Server or Tableau Online. Connect to your data, build a new flow or edit an existing flow and your work is automatically saved every few seconds as you go. Create draft flows that are only available to you or publish your flow to make it available for others. Run your individual flows right from the web or run your flows automatically on a schedule using Tableau Prep Conductor if you have the Data Management Add-on. For more information, see Create and Interact with Flows on the Web.

Add-ons

Tableau Resource Monitoring Tool updates- part of the Server Management Add-on

Resource Monitoring Tool is included in the separately licensed Server Management Add-on for Tableau Server. For more information, see Get Started with Tableau Resource Monitoring Tool.

The following features are included in this release:

Linux Support - Resource Monitoring ToolMaster Server and Agents can now be installed on Linux platform. For more information, see Install the Tableau Resource Monitoring Tool.

SSL Certificates - You can now use a locally imported SSL Certificates.

Agent OS Detection - Master Server can detect the OS that each Agent is installed on and will list it in the web interface. For more information, see Install the Tableau Resource Monitoring Tool.

Tableau Server External Repository- part of the Server Management Add-on

Tableau External Repository is included in a separately licensed Server Management Add-on for Tableau Server. For more information, see Tableau Server External Repository.

Azure Support - You can now configure Tableau Server External Repository on Azure Database. For more information, see Create a Azure Database PostgreSQL Instance on Azure.

Upgrade - If you have External Repository configured, before upgrading your Tableau Server to 2020.4, you must make sure you are using PostgreSQL version 12 or later. For more information, see Upgrade Tableau Server with External Repository for a New Major Version of PostgreSQL.

Tableau Catalogue updates – part of the Data Management Add-on

Tableau Catalogue is included in the separately licensed Data Management Add-on for Tableau Server and Tableau Online. For more information, see About Tableau Catalogue.

The following features are included in this release:

Data Quality Warning History admin view - Site administrators can see how data quality warnings are being used on the site using the pre-built admin view, Data Quality Warning History. For more information see Data Quality Warning History.

See quality warning details in Tableau Desktop - Tableau Desktop users can hover over the warning icon on the Data tab to see details about the data quality warnings affecting the data in their workbook. For more information, see Set a Data Quality Warning.

Metrics appear in lineage and show data quality warnings - Data quality warnings now appear on metrics affected by a warning. Metrics also appear in the Lineage tool, enabling you to see how a metric might be affected by data changes when performing impact analysis. For more information, see Create and Troubleshoot Metrics.

Tableau Prep Conductor updates - part of the Data Management Add-on

Now, the Data Management Add-on is only needed to schedule and monitor flows with Tableau Prep Conductor. Other flow-related tasks no longer require you to licence the add-on. For more information, see Tableau Prep Conductor.

Changed in 2020.4

Version 2020.4 includes the following changes you should know about before upgrading.

SHA1 certificates disabled for SSL mutual authentication

Beginning with Tableau Server 2020.4, Tableau Server configured for mutual SSL authentication will block authentication of users with client certificates that use the SHA-1 signing algorithm.

Users who attempt to log in with SHA-1 client certificates encounter an "Unable to sign in" error, and the following error will be visible in the VizPortal logs:

Unsupported client certificate signature detected: [certificate Signature Algorithm name]

If the clients in your organisation are connecting to Tableau Server using SSL mutual authentication and the clients are using certificates with the SHA-1 signing algorithm, then you must perform one of the following actions before upgrading:

  • Update the certificates used by your clients. The certificates must use the SHA-256 (or stronger) signing algorithm, or
  • Disable the SHA-1 blocklist before upgrading to Tableau Server 2020.4. To disable the blocking functionality, run the following TSM commands before you upgrade:
    tsm configuration set -k "ssl.client_certificate_login.blocklisted_signature_algorithms" -v ""

    Note that the value (-v) includes an empty set of quotes to specify a null value.

    For more information about how to reset this value after you have updated client certificates, see the Knowledge Base article, Mutual SSL Fails After Upgrading if Certificates Signed with SHA-1(Link opens in a new window).

For more information about why this change has been implemented, see the Tableau Community post, Retiring Default Support for SHA-1 Signed Certificates Used During Mutual SSL Authentication in Customer-Managed Tableau Server 2020.4(Link opens in a new window), and the National Institute of Standards and Technology policy statement, NIST Policy on Hash Functions(Link opens in a new window).

wgserver.domain.whitelist config key has been deprecated

Beginning with version 2020.4, the wgserver.domain.whitelist configuration key has been deprecated. Use the new key, wgserver.domain.accept_list to specify allowed domains.

All functionality of the older key has been transferred to the new key. As of 2020.4.0, existing installations configured with the old key will not be impacted, and the key can still be used, but you must include the --force-keys option when setting the key, and the key will be permanently removed in a future release. For all new configurations, use wgserver.domain.accept_list instead. For more information about the new configuration key, see wgserver.domain.accept_list.

CPU requirement update

Beginning with version 2020.4, Tableau Server requires all nodes to have CPUs that support SSE4.2 and POPCNT instruction sets. These CPUs have been common for more than 10 years and are installed on most newer computers. If you attempt to install or upgrade Tableau on a computer that does not support these instruction sets, the installer will not allow you to continue.

Checkpoint Upgrade for Tableau Server

Version 2020.4 of Tableau Server includes updates to the upgrade-tsm script that give you the ability to rerun the script when an upgrade fails. The script keeps track of successful progress, and when you rerun the script after an upgrade failure, restarts at the latest successful "checkpoint". This saves time because successful steps do not need to be repeated on rerunning the script. As a first troubleshooting step, rerun the upgrade-tsm script. Doing this can result in a successful upgrade if a momentary environmental problem or timing issue caused the initial failure.

Checkpoint upgrades also give experienced IT professionals the option to further troubleshoot the failure, and make corrections (for example, if there is a problem with disk space, or a permissions issue on a particular file or directory) before rerunning the upgrade script. For troubleshooting details, see Upgrade fails on 2020.4.0 or later.

PostgreSQL upgrade

Version 2020.4 of Tableau Server includes a major-version update of the PostgreSQL database used for the Tableau repository. During the upgrade a temporary pgsql-only backup is created and this increases the length of time the upgrade takes as well as the amount of temporary disk space used.

If you have External Repository configured, before upgrading your Tableau Server to 2020.4, you must make sure you are using PostgreSQL version 12 or later. For more information, see Upgrade Tableau Server with External Repository for a New Major Version of PostgreSQL

Visual improvements to user, group, and site dialogs

The 2020.4 release adds visual updates to administrator menus and dialogs to make managing users, groups and sites easier in Tableau Server.

Changes to default JVM heap size for Tableau Catalogue ingestion

Beginning with Tableau Server 2020.4, the default JVM heap size for Catalogue ingestion is determined by and then scales based on system memory. To review the default values for Catalogue ingestion, see noninteractivecontainer.vmopts.

Version 2020.3

Added in 2020.3

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Server ‘Pre-flight Check’

Beginning in Tableau Server on Windows version 2020.3 a pre-flight check runs when you install or upgrade Tableau Server. This check, on install, looks at common permissions issues related to the install directory and data directory that cause problems when installing Tableau Server. On upgrades, permissions are checked, as well as potential port conflicts for key services. In addition, new tsm maintenance preflight-check commands have been added for both permissions and ports.

For more information see Tableau Server Pre-Flight Check.

New command to list dynamically configurable keys

Version 2020.3 introduces a new TSM command to view all dynamically configurable keys. The command, tsm configuration list-dynamic-keys, displays a list of all configuration options you can change without needing to restart Tableau Server. This command helps you distinguish dynamically configurable keys from those that require a server restart, allowing you to decide when to set each.

Dynamic configuration was introduced in version 2020.2, and version 2020.3 adds additional dynamically configurable logging options to those in 2020.2.0. When you make configuration changes with these keys, or configuration changes with these keys in combination with Tableau Server Dynamic Topology Changes, you do not have to restart Tableau Server.

New dynamically configurable keys include:

  • backgrounder.log.level
  • clustercontroller.log.level
  • dataserver.log.level
  • filestore.log.level
  • gateway.log.level
  • tdsservice.log.level
  • vizqlserver.log.level

For details on the new command, see tsm configuration list-dynamic-keys. For more information about the introduction of dynamic configuration in version 2020.2, see Dynamic Configuration. For more on changing logging levels, see Change Logging Levels.

Set the Site Time Zone for Extracts

The default time zone for extract-based data sources in a site is Coordinated Universal Time (UTC). Site administrators can now choose to set a different time zone.

For more information, see Set the Site Time Zone for Extracts.

Automatically Suspend Extract Refreshes for Inactive Workbooks

To save resources, Tableau can automatically suspend extract refresh tasks for inactive workbooks. This feature applies to full extract refreshes only, not to incremental extract refreshes. This feature only applies to refresh schedules that run weekly or more often.

For more information, see Automatically Suspend Extract Refreshes for Inactive Workbooks.

Manage Licences for User Groups with Grant Role on Sign-In

Administrators can set a minimum site role for user groups and choose Grant role on sign-in when creating or modifying that user group. Enabling Grant role on sign-in reduces manual work to manage licences, since administrators can designate site role capabilities by group, and provision licences when a user actually needs it. By waiting to grant licences until users sign in, administrators can streamline licence provisioning, without granting licences to inactive users. For more information, see Grant Licence on Sign-in.

Tableau Catalogue updates – part of the Data Management Add-on

Tableau Catalogue is included in the separately licensed Data Management Add-on for Tableau Server and Tableau Online. For more information about Tableau Catalogue, see About Tableau Catalogue.

The following features are included in this release:

See data quality warnings in Tableau Desktop – When you open a workbook in Tableau Desktop that has a data quality warning, the warning icon (either a blue circle or a yellow triangle with an exclamation point) appears on the Data tab on the sheet page of the workbook. For more information, see Set a Data Quality Warning

'Sensitive data' warning type added – You can use this new warning type to set a data quality warning for sensitive data in your organisation. For more information, see Set a Data Quality Warning

Embedded assets are listed in External Assets – You can now see embedded assets listed in the External Assets page. For more information, see Use Lineage for Impact Analysis.

Tag external assets – Add tags to databases, tables and columns, which enables you to, among other things, tag tables and columns with personally identifiable information (PII). For more information, see Tag Items(Link opens in a new window) in Tableau Desktop and Web Authoring Help.

Use admin tools to get indexing status for Catalogue and Metadata API

Tableau Server 2020.3 includes two admin tools to make it easier to get indexing status of Tableau Catalogue and Tableau Metadata API:

  • Monitor initial ingestion progress and validate its status using the Backfill API. For more information, see Get Initial Ingestion Status.
  • After initial ingestion, ensure indexing continues to work as expected using the Eventing API. Fore more information, see Get Eventing Status.

Tableau Content Migration Tool updates – part of the Server Management Add-on

Tableau Content Migration Tool is included in the separately licensed Server Management Add-on for Tableau Server. For more information about Server Management Add-on, see About Tableau Server Management Add-on.

The following features are included in this release:

  • Support for Tableau Online – The Content Migration Tool now includes both Tableau Online and Tableau Server sign-in options when connecting to source and destination servers. To learn about the new sign-in experience, see Migration Plans: Servers.

  • SAML and Single Sign-On – As of version 2020.3, you can authenticate using SAML and Single Sign-On authentication types for non-scripted migration plans.

  • Tableau Bridge data sources – Published data sources that are within a private network (inaccessible to the public Internet) can be migrated and allowed to refresh using Tableau Bridge. For more information, see Migration Plans: Published Data Sources.

  • Tableau Prep Builder and Tableau Prep Conductor – Content produced by Tableau Prep Builder or Tableau Prep Conductor (version 2020.2.x and later) can now be included in your migration plans.

  • Asynchronous publishing – The Content Migration Tool now supports asynchronous publishing of data sources.

  • Resource optimisation – You can specify how many objects to process in memory in parallel with the new Maximum Processing Concurrency setting. The setting allows you to optimise resource usage of CPU and memory when performing migration operations, ultimately reducing your memory footprint. For more information, see Tableau Content Migration Tool Settings.

  • Migrate more content – The Content Migration Tool editor and console runner can now use up to 4 GB of RAM (increased from 2 GB), allowing you to migrate larger workbooks and data sources.

Tag Stale Content for Archiving

The Stale Content Admin view that was introduced in 2020.2, now has an added functionality that allows you to tag content as stale. You can then choose to archive the tagged content. For more information, see Stale Content.

Changed in 2020.3

Version 2020.3 includes the following changes you should know about before upgrading.

Data Acceleration for Workbooks that use the Object Model Framework

Administrators can now also enable data acceleration for workbooks that use the Object Model framework. See Data Acceleration.

Version 2020.2

Added in 2020.2

User

Other new features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Combined What's New and What's Changed in Tableau Server

Beginning with version 2020.2, the "What's New" and "What's Changed" Help topics are combined in a single "What's New and Changed in Tableau Server" topic (this topic). The topic has been relocated in the Table of Content, and the old "What's Changed" topic now has a link to the combined file.

Applies to label for Data Management and Server Management Add-ons

Topics about add-on features list the add-on name in the Applies to section of the topic. For example:

Use Relationships to Combine Data for Multi-table Analysis

Relationships are a new, flexible way to combine data for multi-table analysis in Tableau. Data sources now support multi-table data models in a new logical layer. Tableau recognises the separate tables in your data source and performs aggregations at the native level of detail for each table.

Creators can combine tables using relationships. Using relationships between logical tables makes it easier to explore and analyse multi-table data at the right level of detail, without having to write specialised calculations to control aggregations like averages and totals.

You do not need to specify join types for relationships; during analysis Tableau automatically selects the appropriate join types based on the fields and context of analysis in the worksheet.

Note: Your workbook must use an embedded data source for you to be able to edit relationships in the Data Source page in web authoring in Tableau Server or Tableau Online. You cannot edit the data model of a published data source.

In support of multi-table analysis, several parts of the Tableau interface have changed. The Data Source page (canvas, data grid), View Data window and the Data pane in the worksheet have all been updated to support a multi-table analysis experience. For more information, see Changes to different parts of the interface(Link opens in a new window).

Note: View Data column order has changed in Tableau 2020.2 and later. This change is required to support relationships and logical tables. For details, see View Data column order changes in Tableau 2020.2 and later.

For more information about relationships and changes to data sources, see these topics:

Also see this Tableau blog post: Relationships, part 1: Introducing new data modelling in Tableau(Link opens in a new window)

Create Metrics to Track Data

Metrics help users track changes to their data. Users can create metrics from a view and use them to monitor key numbers like daily sales. For information on how users create metrics, see Create and Troubleshoot Metrics.

As a Tableau Server administrator, you have the ability to control how often metrics refresh and how failing refreshes are handled. You also can ensure that users are able to create metrics or disable metrics for particular sites. For more information, see Set Up for Metrics.

New Admin Views

Two new pre-built administrative views are available in this release:

  1. Backgrounder Dashboard: Use this view to understand the background job details such as, the number of jobs that have completed successfully, failed or cancelled. You can also identify when your Backgrounder is busy or overloaded. For more information, see Backgrounder Dashboard.
  2. Stale Content aka Stats for Unused Content: Identify content that hasn't been accessed or opened in a while and how much disk space is being used by stale content. For more information, see Stale Content.

    In previous versions of Tableau Server, admin views were all displayed in the same workbook, in separate tabs. However, the two new admin views are displayed as separate workbooks and not part of the existing admin view workbook. You can navigate to the new admin views from the Server or Site Status page:

Changes to Create and Modify Schedule

The web interface used to create and modify schedule has changed. You can now select more than one day when you create or modify monthly schedules. For more information and updated screen shots of the new web interface, see Create or Modify a Schedule.

Data Acceleration

Administrators can now enable data acceleration for specific workbooks. The workbook loads faster because Tableau Server precomputes the workbook's data in a background process. For more information, see Data Acceleration.

Extract Query Load Balancing

Improvements to load balancing for extract-based queries are now available in Tableau Server. For more information, see Extract Query Load Balancing.

Dynamic Configuration

Version 2020.2 introduces dynamic configuration for certain configuration options or keys. When you make configuration changes with these keys, or configuration changes with these keys in combination with Tableau Server Dynamic Topology Changes, you do not have to restart Tableau Server. This step toward more flexible server management includes dynamic configuration keys for changing logging levels for some Tableau Server processes, and changing some TSM base file paths.

Dynamically configurable keys include:

  • tsm.log.level
  • tsm.controlapp.log.level
  • tabadmincontroller.auth.expiration.minutes
  • basefilepath.site_import.exports
  • basefilepath.site_export.exports
  • basefilepath.backuprestore

For more information see Change Logging Levels and tsm File Paths.

Tableau Catalogue updates – part of the Data Management Add-on

Tableau Catalogue is included in the separately licensed Data Management Add-on for Tableau Server and Tableau Online. For more information about Tableau Catalogue, see About Tableau Catalogue.

The following features are included in this release:

Raise the visibility of important warnings - You can set a data quality warning to be highly visible, so that users of a visualisation that's affected by the warning see a notification, and the warning displays in a more prominent yellow colour elsewhere in Tableau. For more information, see Set a Data Quality Warning and "Use Data Details to see visualisation information" in Explore and Analyse Data in a View(Link opens in a new window) in the Tableau Desktop and Web Authoring Help..

Dashboards appear in the Lineage pane - When you select the Dashboards item in the lineage, you can see a list of downstream dashboards. For more information, see Use Lineage for Impact Analysis.

Filter external assets on Certified and data quality warnings - In addition to using search to narrow down your choices on External Assets, you can now filter databases, files and tables by Certified and by data quality warnings.

More filters when connecting - When you connect to data, you can filter databases and table on connection type.

Changed in 2020.2

Version 2020.2 includes the following changes you should know about before upgrading.

Analytics extensions (external service) connections must be reconfigured

Tableau supports a set of functions that your users can use to pass expressions to analytics extensions for integration with R and Python. Previously, this feature was referred to "external services". 

In previous versions of Tableau Server, the analytics extensions configuration applied to the Tableau Server global configuration and was administered with TSM.

Beginning with version 2020.2, you can configure a different analytics extensions connection for each site. Administration of the analytics extensions connection has moved out of TSM and to Tableau Server administrator. Additionally, configuring an analytics extensions connection no longer requires a restart of Tableau Server.

However, if you have configured Tableau Server with an analytics extensions connection, then you must reconfigure that connection after you upgrade Tableau Server to version 2020.2.

Before upgrading, document the existing analytics extensions configuration. On previous versions (2019.1-2020.1) you can run the tsm security vizql-extsvc-ssl list command to list the existing connection details. To retrieve the password that is stored for the analytics extensions connection (if any), run the following tsm command:

tsm configuration get -k vizqlserver.rserve.password

After you have upgraded, configure the analytics extension connection. See Configure Connections with Analytics Extensions.

Oracle data source connections require updated driver

Beginning with version 2020.2, Oracle data sources use a new JDBC driver. You must download and install this driver on Tableau Server to enable existing content relying on Oracle connections to properly display. Until this driver is downloaded and installed on Tableau Server, existing content will not display or refresh. Follow the instructions on the Driver Download(Link opens in a new window) page to get and install the new driver. For details on the changes and how they impact Tableau authors, see Oracle(Link opens in a new window) in the Tableau Desktop and Web Authoring Help.

WDC behaviour change if Run As service account has admin group privileges

Beginning with version 2020.2, because of changes to the QTWebEngine component used by Tableau Server, if you use Web Data Connectors (WDCs) and Tableau is configured with a Run As service account in a local administrators or domain administrators group, you may run into problems using WDCs. Our recommendation has been and continues to be to use a domain User account for the Run As service account. This is a good security practice.

For more information on possible issues, see the Tableau Knowledge Base(Link opens in a new window). For details on suggested best practices when creating a Run As service account, see Creating the Run As service account.

Tableau Resource Monitoring Tool Updates

The Startup Values of some TSM services have changed

Beginning in maintenance versions, the startup values of several TSM services have been changed from "Automatic" to "Automatic (Delayed Start)" to help address some occasional issues in timing. This change should not have a significant impact. Services affected: Tableau Server Administration Agent, Tableau Server Administration Controller, Tableau Server Client File Service, Tableau Server Coordination Service, Tableau Server Licence Manager and Tableau Server Service Manager.

If you are running an older version of Tableau Server you can leave the startup values as they were originally configured ("Automatic"), but updating them to the new values ("Automatic (Delayed Start)") will not negatively impact Tableau Server. For more information about service startup values, including the specific maintenance releases where this change took place, see Verify Tableau Service Settings(Link opens in a new window) in our current documentation.

Version 2020.1

Added in 2020.1

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Run Now Server and Site Setting

This new setting allows Server Administrators to configure whether to allow or block users from manually running extract refreshes, flows runs and subscriptions. This can be set at the server level to apply to all the sites on Tableau Server or at a site level to apply to only certain sites. For more information, see Server Settings (General and Customisation).

New configuration options for Hyper

You can use these new tsm configuration set options to configure Hyper to control resource consumption and improve stability:

  • hyper.memory_limit
  • hyper.memtracker_hard_reclaim_threshold
  • hyper.memtracker_soft_reclaim_threshold
  • hyper.network_threads
  • hyper.objectstore_validate_checksums
  • hyper.query_total_time_limit
  • hyper.session_memory_limit
  • hyper.temp_disk_space_limit

For more information, see tsm configuration set Options.

Support for Login-based Licence Management

Login-based licence management, helps you manage licensing for users with Creator roles on Tableau Server and Tableau Online. Users with Explorer or Viewer roles cannot use this feature. If you’re using Role Based Subscriptions with Tableau Server or Tableau Online, you can simplify your licence management using login-based licence management to eliminate separate Tableau Desktop and Tableau Prep Builder product keys. You only need to manage one or more product keys for on-premises Tableau Server, or in the case of Tableau Online, you don’t need to manage any product keys at all.

Support for Kerberos delegation with Vertica data source

You can now authenticate to Vertica data sources with Kerberos delegation. To configure Kerberos delegation on Tableau Server, see Enable Kerberos Delegation. To enable Kerberos for Vertica in Active Directory, see Enabling Kerberos Delegation for Vertica(Link opens in a new window).

Support for managing site role limits

Server administrators can now set a maximum number of Creator, Explorer and Viewer licences available for a site. Site administrators can use those quotas to allocate licences for users on their site. For a site that has user-based licensing with no licensing limits set by the server administrator, maximums for each role are determined by the number of available licences. To learn more, see Manage Site Role Limits . Server admins can also configure site role quotas via the REST API.

Updates for Permission Dialog

Set permissions faster with the new permissions dialog. New permission templates(Link opens in a new window) and capability groupings match common user scenarios. Editing permission rules is easier than ever with direct editing – double click to enter edit mode. Search for groups and users simultaneously without preselecting your choice. Copy(Link opens in a new window) a custom permission rule and paste it for another group or user. And hand off project management to Project Leaders(Link opens in a new window) more intuitively with the new setting. For more information on permissions, see Permissions.

Lock nested projects

Regulating permissions is now more flexible. Project permissions can be locked independently for nested projects. Top-level projects can act as organisational containers for projects with different permission models. Non-admins can create new locked projects. For more information, see Lock content permissions.

Tableau Server External File Store (Server Management Add-on)

You can now configure Tableau Server to use a SAN or NAS to store File Store data. Using a network attached storage for your File Store data provides some benefits like reduced backup times, by using the snapshot backup technologies. For more information see, Tableau Server External File Store

Tableau Catalogue updates – part of the Data Management Add-on

Tableau Catalogue is included in the separately licensed Data Management Add-on for Tableau Server and Tableau Online. For more information about Tableau Catalogue, see About Tableau Catalogue.

The following features are included in this release:

Added connectors - Connect to more data from external assets. We've added support for the following connectors: Google Big Query, Google Drive, Google Sheets, Box, Dropbox and OneDrive.

Create workbooks - Create a workbook from the External Assets page or from a database or table page for Catalogue-supported connections. For more information, see "Tableau Catalogue users create workbooks from external assets" in Creators: Get Started with Web Authoring(Link opens in a new window) in the Tableau Desktop and Web Authoring Help.

Filter on Certified and data quality warnings - Filter data sources, databases, files, and tables by Certified, filter data sources by connections and filter databases and tables by data quality warnings. For more information, see "Open the Connect to Data page" in Creators: Connect to Data on the Web(Link opens in a new window), or "Connect from Tableau Desktop" in Connect to Data by Using Tableau Server or Tableau Online(Link opens in a new window) in the Tableau Desktop and Web Authoring Help.

Enhanced Data Details pane -

  • See a sparkline with the number of times a sheet or dashboard was viewed over the last 12 weeks.
  • Easily see that there are Warnings on a view.
  • Expand a field to see its metadata, such as a description or calculation.
  • When a field in a workbook inherits its description, see where the description comes from.

    For more information, see "Use Data Details to see visualisation information" in Explore and Analyse Data in a View(Link opens in a new window) in the Tableau Desktop and Web Authoring Help.

Changed in 2020.1

Version 2020.1 includes the following changes you should know about before upgrading.

Tableau Server no longer supports Windows 7 or Windows 2008

Beginning with version 2020.1, in keeping with Microsoft's Windows Server support policy, Windows 7 and Window 2008 are no longer supported operating systems for Tableau Server.

For more information about supported versions of Windows, see Operating system requirements.

tableau-server-obliterate script now preserves backup and log files

In previous versions of Tableau Server, running the tableau-server-obliterate script deleted all content from the Data directory. Beginning with version 2020.1, the default behaviour of the tableau-server-obliterate script has changed: the script copies and saves Tableau Server backup and log files to the logs-temp directory. The default location for the logs-temp directory is at \ProgramData\Tableau\logs-temp. You can set options on the script to disable this new functionality.

See Remove Tableau Server from Your Computer.

Improvements to the tsm topology deploy-coordination-service command

Beginning with version 2020.1, the command to deploy a new coordination service ensemble waits for the ensemble to be properly deployed and removes the old ensemble before returning control to the command prompt. This simplifies the process for deploying a new coordination service ensemble and eliminates the chances of continuing on with other commands or actions before Tableau Server is properly configured for the new ensemble. You no longer need to run the tsm topology cleanup-coordination-service command after deploying a new ensemble in version 2020.1.0 and later.

Note: With this change, all coordination service ensemble commands require input for a "y/n" prompt confirming that a server restart will take place. To run these commands without input, include the --ignore-prompt option.

For more information about deploying a coordination service ensemble, see Deploy a Coordination Service Ensemble.

Large statistical file extracts consume system resources

Beginning with Tableau Server 2020.1, a change to the Statistical File (SAS) library may cause large SAS-based extract refreshes to fail. The following connection error will be visible in the backgrounder logs, along with spikes in system memory consumption.

"exceeded per-process memory threshold"

To work around the issue, run the following TSM commands after upgrading Tableau Server:

tsm configuration set -k features.ReadStat -v false
tsm pending-changes apply

For more information and steps to work around the issue in Tableau Desktop, see the Knowledge Base article, Large Sas File Extract Refresh Failed And Huge Memory Consumption Observed After Upgraded Tableau Server To 2020.3.1(Link opens in a new window).

Version 2019.4

Added in 2019.4

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Request access

Users can now request access to see a project, workbook or view when they don’t have viewing permission. When someone requests access to content, Tableau routes an email to the person who controls permissions for that content with information about the request and instructions on making access changes. For information on managing permissions, see Permissions.

Configure recommendations for views

Tableau Server now recommends views to help users discover relevant content. Recommendations for views are an expansion of the system that provides recommendations for data sources and tables.

  • To control whether the recommendations feature is enabled for your server, use the tsm configuration set options recommendations.enabled and recommendations.vizrecs.enabled. For more information, see tsm configuration set Options.
  • To schedule when the recommendations trainer runs on your server, adjust the server settings under Recommendations Training Schedule. For more information, see Server Settings (General).
  • To hide all recommendations on a particular site, or to hide user names from appearing on the recommendation tooltips for a particular site, adjust the site settings under Recommendations for Views.

Enable or disable Ask Data for a site

As a site administrator, you can control the availability of Ask Data in the General area of site settings. For more information, see Disable or Enable Ask Data for a Site.

Personal access tokens

Personal access tokens provide Tableau Server users the ability to create long-lived authentication tokens. The tokens allow users to run automation with Tableau REST APIs without requiring hard-coded credentials or interactive login. More information about using personal access tokens with Tableau REST APIs is at Signing In and Out (Authentication)(Link opens in a new window).

As an administrator, you can revoke and track usage of the tokens. See Personal Access Tokens.

Secure SMTP

You can now configure Tableau Server to connect with your email server over a secure connection. You can encrypt and optionally authenticate with a certificate that you upload and configure on Tableau Server. See Secure SMTP.

Test Email Configuration

After you configure an SMTP connection, use the new command, tsm email, to validate it.

Create Extracts on the Web

Now you can create extracts in the browser, without using Tableau Desktop. For more information, see Create Extracts on the Web. You can also use the new createextracts and deleteextracts commands in tabcmd to create or delete extracts for a published workbook or data source. For more information, see tabcmd Commands.

New Installers for Tableau Server and tabcmd

Tableau Server 2019.4 introduces completely rewritten Setup programs for both Tableau Server and tabcmd. For more information, see What's Changed - Things to Know Before You Upgrade.

Custom welcome banner

You can add a custom message to the welcome banner on the home page for all server users to see. Add up to 240 characters of text and hyperlinks to provide important support information or resource to help server users get started. You can also turn off the default Tableau home banner for all server users. For more information, see Customise Your Server.

Limit visibility of user information

The User Visibility site setting lets administrators manage if users with Viewer and Explorer site roles see other users and groups on the site, which can be important for sites that are used by multiple clients. When User Visibility is set to Limited, Explorers and Viewers cannot see information about other users, including aliases, project ownership, comments and more. Creators and administrators (including Site Administrator Explorers) can still view user information. By default, User Visibility is set to Full. For more information, see Manage Site User Visibility.

Manage Sandboxed Extensions

Tableau now supports Sandboxed extensions, which are a new type of dashboard extension that run in a protected environment hosted by Tableau. Like Network-enabled extensions, Sandboxed extensions are web applications that run in custom dashboard zones and can interact with the rest of the dashboard using the Tableau Extensions API(Link opens in a new window). While Network-enabled extensions have full access to the web, Sandboxed extensions can’t share data or make network calls outside of the hosting Tableau Server. Sandboxed extensions provide a new level of security for Tableau users and administrators.

To learn more about controlling extensions, see Manage Dashboard Extensions in Tableau Server. To learn more about extension security and strategies for deployment, see Extension Security - Best Practices for Deployment.

Changed in 2019.4

Version 2019.4 includes the following changes you should know about before upgrading.

Tableau Server installer has been rewritten

The 2019.4 release of Tableau Server features a newly rewritten Setup program for Tableau Server.

This update changes some of the command line switches and options available for the installer. If you have automated the installing or upgrading of Tableau Server, be sure to review the current command line options for the Server Setup program. See Changes to Command Line Install Options for Tableau Server Setup for more information.

New tabcmd installer for Windows

The 2019.4 release of Tableau Server features a newly rewritten Setup program for installing tabcmd on Windows.

This update changes some of the command line options. If you have automated the installation of tabcmd, be sure to review the current command line options for the tabcmd Setup program. For more information, see tabcmd and Install Switches and Properties for tabcmd (Windows)

Updates to Tableau Server Job management

The Job management page has several updates and new options including the following:

  • The Jobs page now includes Average Run and Average Queue time information for each job.

  • Improved job cancellation experience. Server and Site admins can now enter customised notes as well as pick recipients of the email when cancelling a job.

  • More information is provided in the job detail dialog box, such as: the last time the job was run successfully and the name of the job creator.
  • Cancelling flow run jobs is now supported. Previously, in Tableau Server version 2019.3, only extract refreshes and subscriptions were supported.
  • New Task Type has been added: Encryption jobs.

  • Failed jobs now includes jobs that have been suspended. Suspended jobs are a sub-status of the failed jobs and have their own icon to distinguish them from other failed jobs.

For more information, see Managing Background Jobs in Tableau Server.

Updates to tsm maintenance cleanup command

The tsm maintenance cleanup command now includes an option to clear the image cache.

In addition, the --verbose option has been removed from the command. Running the command with the --verbose option will result in an error. If your organisation has automated task using the tsm maintenance cleanup command with the --verbose option, update your automation scripts.

Changed behaviour for Copy Link when sharing a view

Beginning with version 2019.4, the behaviour of the Copy Link option of the Share button in a view no longer includes the "embed=y" parameter by default. To include this parameter you need to edit the copied URL before adding it to your web page code. For more information sharing views by embedding them in web pages, see Embed Views into Webpages(Link opens in a new window) in the Tableau Desktop and Web Authoring Help. For details about the parameter, see URL parameters for iframe tags(Link opens in a new window) in the Tableau Desktop and Web Authoring Help.

Version 2019.3

Added in 2019.3

Version 2019.3 includes the following new features.

Add PDF Attachments to Subscription Emails

You can give your users the option to attach PDF renderings for views and workbooks subscription emails. You must enable attachment functionality on the server. See Configure Server Event Notification.

Tableau Catalogue features – part of the Data Management Add-on

Tableau Catalogue is included in the separately licensed Data Management Add-on for Tableau Server and Tableau Online, making a variety of features available to you in the data management space. You can use Tableau Catalogue to discover data, curate data assets, communicate data quality, perform impact analysis and trace the lineage of data used in Tableau content. For more information, see About Tableau Catalogue.

Tableau Catalogue on the server – part of the Data Management Add-on

Tableau Catalogue is included in the separately licensed Data Management Add-on. For more information, see Licence the Data Management Add-on.

You can give your users access to metadata and features like expanded search, data details, and lineage when you Enable Tableau Catalogue. To learn more about how Tableau Catalogue and metadata permissions work, see Manage Permissions for External Assets.

Tableau Metadata API

If you're a developer and interested in accessing metadata indexed by or surfaced through Tableau Catalogue see the Tableau Metadata API Help(Link opens in a new window).

Job Management

You can now view, monitor and manage backgrounder jobs on Tableau Server. For more information, see Managing Background Jobs in Tableau Server.

Support for Embedded Credentials in Bootstrap Files

You can now include embedded credentials when generating bootstrap file. This allows you to add a new node to your Tableau Server installation from the command line without needing to provide TSM administrative credentials when installing the node, and can be especially useful if you automate installation of Tableau. This feature is enabled by default and the embedded credentials are valid for a predetermined amount of time (see tabadmincontroller.auth.expiration.minutes) and serve as a session cookie.

Embedded credentials apply when adding a node from the command line, and are designed to provide you with flexibility, so you can choose how you use this feature. You can choose to not include embedded credentials any time you generate a bootstrap file. You can also disable the feature entirely using the features.PasswordlessBootstrapInit option with the tsm configuration set command. When credentials are not included, you are prompted, when adding a node, for the name and password of a user with administrative permissions on the computer where Tableau Services Manager is installed.

Important: The bootstrap file contains a copy of the master keystore file used for encrypting the configuration secrets. The file can also embedded credentials which are valid for a predetermined amount of time (see tabadmincontroller.auth.expiration.minutes) and serve as a session cookie. We strongly recommend that you take additional measures to secure the bootstrap file.

For more information, see tsm topology nodes get-bootstrap-file.

Server Management Add-on

Server Management Add-on is a separately licensed Add-on which will provide enhanced security, manageability and scalability capabilities for Tableau Server.

  • Improved scalability:

    • For Tableau Server deployments hosted on AWS, you can now choose to host your metadata repository externally with Amazon RDS Postgres. Amazon RDS offers scalability, reliability, high availability and security built-in for PostgreSQL. By integrating with AWS, you will be able to take advantage of these additional benefits of deploying the cloud. For more information, see Tableau Server External Repository.
    • You can also tune your Tableau Server processes by customising which nodes process data engine queries and background jobs. For more information, see Workload Management through Node Roles.

  • Increased operational efficiency:

    • New Resource Monitoring Tool and Content Migration Tool which were acquired from Interworks are included as part of Server Management Add-on:

      • The Resource Monitoring Tool provides increased visibility into hardware utilisation and server processes and makes it easier to understand and tune the performance of your Tableau Server installation. For more information, see About Tableau Resource Monitoring Tool.

      • The Content Migration Tool helps streamline your workbook and data source content work flows. You can manage the movement of content between development and production or between other environments. For more information, see About Tableau Content Migration Tool

  • Enhanced security:

    If your organisation will be enabling extract encryption at rest, you can also integrate Tableau Server with AWS Key Management Service to provide an enhanced level of integration and security. For more information, see Tableau Server Key Management System.

Extract Encryption at Rest

Extract encryption at rest is a data security feature that allows you to encrypt .hyper extracts while they are stored on Tableau Server.

Tableau Server administrators can enforce encryption of all extracts on their site or allow users to specify to encrypt all extracts associated with particular published workbooks or data sources. See Extract Encryption at Rest.

Date-range Support for Ziplogs

Two new date options for the tsm maintenance ziplogs command, --startdate and --enddate, give you the ability to specify a date range for the logs being gathered. These options must be used together, and cannot be used with the --minimumdate option. For more information, see tsm maintenance ziplogs.

Tableau Server Usage Data

Beginning with Tableau Server 2019.3, server usage data is sent to Tableau by default. This is the case for new installs and upgrades and can be disabled. You can opt out during installation, upgrade, or at any time after Tableau Server has been installed. For more information about usage data, see What's Changed - Things to Know Before You Upgrade in the What's Change article, and the general overview, Server Usage Data.

Add a Note to Tableau Server Sign In Page

You can add an optional note and URL to your server's sign in page to help new users gain server access or for server-wide announcements. The setting also supports emojis. To set a custom note, sign in to a site on Tableau Server. On the left-side navigation pane, select Manage all sites from the drop-down site list. Select Settings to and add a message to Sign In Customisation. For more information about customising Tableau Server, see Customise Your Server.

Support added for Italian

Tableau has added support for Italian. You can now set Tableau to display the user interface in one of eleven languages:

  • Chinese (Simplified)
  • Chinese (Traditional)
  • English (United Kingdom)
  • English (United States)
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Spanish

For more information, see Language and Locale for Tableau Server.

In addition to supporting Italian in all Tableau products, the help is also available in these languages. To read the help in your preferred language, navigate to the bottom of the main Tableau Help page, and select the language from the footer.

Menu of language options

Changed in 2019.3

Version 2019.3 includes the following changes you should know about before upgrading.

Default cipher suite no longer includes default support for old ciphers

The 2019.3 version of Tableau Server no longer includes default support for Triple-DES, IDEA and CAMELIA ciphers for SSL connections. These ciphers are no longer considered adequately secure. In the previous versions of the Security Hardening Checklist, we included a recommendation to disable the Triple-DES cipher, which was enabled by default.

Depending on your environment, you may need to make additional configurations before our after upgrading:

  • If you disabled the Triple-DES cipher as documented in the Checklist, then we recommend running the following commands before you upgrade to 2019.3:

    tsm configuration set -k ssl.ciphersuite -d

    tsm pending-changes apply

    This command reverts Tableau Server to the 2019.2 (and older) default cipher suite configuration. After you have upgraded to 2019.3, Triple-DES, IDEA and CAMELIA will be removed from the default supported ciphers.

    Do not run the command if you made other changes to the ssl_ciphersuite key.

  • If you did not change the ssl_ciphersuite key, then Setup will update the key value to the new default as part of the upgrade process. The new default value for the ssl_ciphersuite key is HIGH:MEDIUM:!aNULL:!MD5:!RC4:!3DES:!CAMELLIA:!IDEA:!SEED.

  • If your users still require support for Triple-DES, then we recommend upgrading to more recent browsers that support more secure ciphers. If that is not an option, then you can run the following commands after you have upgraded. The first command sets the ssl_ciphersuite key to the pre-2019.3 configuration, which supports Triple-DES:

    tsm configuration set -k ssl.ciphersuite -v "HIGH:MEDIUM:!aNULL:!MD5:!RC4"

    tsm pending-changes apply

Usage data is sent to Tableau

Beginning with Tableau Server 2019.3, server usage data is sent to Tableau by default. This is the case for new installs and upgrades. You have the ability to opt out during installation, upgrade or at any time after Tableau Server has been installed. For more information about usage data, see Server Usage Data.

To disable the sending of server usage data:

  • If you are installing Tableau Server for the first time, you can disable this feature during the configuration of initial node settings. For details, see Configure Initial Node Settings.

  • If you are upgrading Tableau Server, the upgrade-tsm script will let you know about the option and how to disable it.

  • If you want to have installed or upgraded Tableau Server and want to disable the sending of server usage data, you can do this from the TSM Maintenance page, or from the command line. For details, see Server Usage Data.

Upgrade without needing to provide a password

Beginning with Tableau Server 2019.3, when you upgrade from version 2019.2 or later, the upgrade-tsm script no longer requires you to specify a user and password. Version 2019.3 and later take advantage of the What's New and Changed in Tableau Server feature and uses the account you have logged in as to authenticate the upgrade. You can override this behaviour with the --user option, to specify an administrative user. When you do this, you can also provide a password using the --password option, or enter a password when prompted. Upgrades from versions earlier than 2019.2.0 will still prompt you for a password.

Some tsm command options are no longer configurable

Beginning with Tableau Server 2019.3, the following options are enabled on install and are no longer configurable:

  • backgrounder.enable_sort_ jobs_by_job_rank
  • backgrounder.enable_task_ run_time_and_job_rank

Version 2019.2

Added in 2019.2

Version 2019.2 includes the following new features.

Help Design

A blue Send feedback icon is displayed in the bottom right corner of every Help page to make it easier for you to send feedback about the content in a topic. Click the icon to let us know if a topic is helpful to you, and also to comment on what needs improvement.

User

Direct access with TSM CLI

Beginning in the 2019.2 release of Tableau Server, running tsm commands will not require you to enter a password if the following are true:

  • The account you are running commands with is a member of the TSM-authorised group, which is the local Administrators group on the Windows computer.
  • You are running commands locally on the Tableau Server that is running the Tableau Server Administration Controller service. By default, the Tableau Server Administration Controller service is installed and configured on the initial node in a distributed deployment.

See Authenticating with tsm CLI.

Local authentication password policy improvements

Beginning in the 2019.2 release of Tableau Server, you can now set password policies for Tableau Server that is configured for local authentication. For example, you can specify password length, expiry and complexity. Additionally, you can set accounts to be locked out after too many failed sign-in attempts. You can also enable users to reset their own passwords. See Local Authentication.

Select from ten different languages for Tableau

Tableau has added support for two new languages, Chinese (Traditional) and English (United Kingdom). You can now set Tableau to display the user interface in one of ten languages:

  • Chinese (Simplified)
  • Chinese (Traditional)
  • English (United Kingdom)
  • English (United States)
  • French
  • German
  • Japanese
  • Korean
  • Portuguese
  • Spanish

For more information, see Language and Locale for Tableau Server.

In addition to supporting two new languages in all Tableau products, the help is also available in these languages. To read the help in your preferred language, navigate to the bottom of the main Tableau Help page, and select the language from the footer.

Menu of language options

Set a site-level start page

Beginning in the 2019.2 release of Tableau Server, you can set a start page for all site users, so that they land on a particular page when they sign into Tableau Server. Previously, server administrators could only set a start page at the server-level. See Set the Default Start Page for All Users.

Windows Server 2019

Beginning in the 2019.2 release of Tableau Server, you can install Tableau Server on Windows Server 2019. For more information about requirements, see Before you install....

Elastic Server on multiple nodes

Elastic Server is used by Ask Data to index data. You can now run Elastic Server processes on more than one node in a cluster. It is recommended to have an odd number of Elastic Server processes running. For more information, see Tableau Server Processes.

SSL connection to TabPy external service

In previous versions, SSL connections to TabPy were not supported. In Tableau Server 2019.2, you can configure SSL connections. Configuring external services is done with tsm commands at tsm security.

Configuring the threshold for suspending data-driven alerts

By default, an alert is suspended after 350 consecutive alert failures. Server administrators can configure the threshold number of alert failures before an alert is suspended. For more information, see Set Up for Data-Driven Alerts.

Configuring logging levels for TSM processes

You can now easily change the logging levels of Tableau Services Manager (TSM) processes. This allows you to increase logging levels to troubleshoot issues (if you are working with Tableau Support for example). For more information, see Change Logging Levels.

Changed in 2019.2

Version 2019.2 includes the following changes you should know about before upgrading.

Minimum hardware requirements have changed

Beginning with version 2019.2, Tableau Server requires a minimum of 4 cores and 16 GB of RAM in order to install. The installation program will check that the computer you are installing on satisfies these minimums before you can install. If the computer does not meet these hardware minimums, Tableau cannot be installed. For details, see Minimum Hardware Requirements and Recommendations for Tableau Server. For more information about this change, see this Tableau blog post: Updated machine requirements for Tableau Server trials.(Link opens in a new window)

Upgrade requires at least 15% free disk space on each node

Upgrading to version 2019.2 includes a version update to the PostGRES database that Tableau uses internally. This update means that a backup of the database is done before upgrading, and that requires a minimum of 15% free space on each node.

"Referrer-Policy" HTTP header added

Beginning in 2019.2, Tableau Server includes the ability to configure Referrer-Policy HTTP header behaviour. This policy is enabled with a default behaviour that will include the origin URL for all "secure as" connections (policy no-referrer-when-downgrade). In previous versions, the Referrer-Policy header was not included in responses sent by Tableau Server. This change is not likely to impact user scenarios for most browsers. However, we recommend testing browser-based user scenarios after you upgrade to 2019.2. In the event a user scenario is effected, you can disable or change this header behaviour. See HTTP Response Headers.

Map-related internet addresses have changed

Beginning in 2019.2, Tableau Server needs access using port 443 to two new map locations: 

  • mapsconfig.tableau.com
  • api.mapbox.com

These replace the address used by previous versions: maps.tableau.com. For details on configuring Tableau Server for proper internet access, see Configuring Proxies for Tableau Server.

Version 2019.1

Added in 2019.1

Version 2019.1 includes the following new features.

Changes to Tableau Help

Updates have been made to help you navigate our content, including a new right-hand menu to quickly scan and select different topics on a page. We've also created content within tabs, to easily show how to complete tasks for web or command line interface.

User

Server or site administrator

Web authoring auto recovery

With Tableau Server 2019.1, editing and authoring content on the server will auto-recover in the event of a process failure. As you make changes to content, Tableau Server will intermittently (and silently) save changes. In previous versions, a process failure results in lost changes if you did not save them prior to the failure. In Tableau Server 2019.1, changes you make prior to a failure will be persisted when you reconnect to the content.

By default, Tableau Server will save content after you make five changes to it. Your server admin can adjust this interval with the vizqlserver.NumberOfWorkbookChangesBetweenAutoSaves option using tsm configuration set Options. File size limit (vizqlserver.WorkbookTooLargeToCheckpointSizeKiB) and recovery attempts per session (vizqlserver.RecoveryAttemptLimitPerSession) can also be configured.

Microservice Container Processes

The 2019.1 release adds some new processes to Tableau Server. Two container processes, Interactive Microservice Container and Non-Interactive Microservice Container now appear on the TSM Status page and in the output of the TSM command tsm status -v. These processes contain microservices and cannot be configured independently by administrators. For more information, see Tableau Server Microservice Containers.

TSM client authentication

In the 2019.1 release, certificate trust and management for TSM clients (Web UI and CLI) have been updated to make encrypted connections to Tableau Server easier to manage. See Connecting TSM clients.

Ask Data and Elastic Server Processes

With Tableau Server 2019.1, Ask Data and Elastic Server processes have been added to Tableau Server to support the new Ask Data feature. For more information, see Tableau Server Processes.

The Ask Data process is installed and configured automatically. It cannot be configured manually. Logs are stored in the nlp directory. For more information, see Tableau Server Logs and Log File Locations.

The Elastic Server process is installed and configured automatically. The Elastic Server heap size can be configured by using the elasticserver.vmopts TSM configuration option. For more information, see tsm configuration set Options. Only one Elastic Server process can be running and it can optionally be moved to any node in the cluster.

Tableau Prep Conductor Server Process

Tableau Prep Conductor is a new server process that has been added to Tableau Server to support automation of running and managing flows. Tableau Prep Conductor leverages the scheduling and tracking functionality of Tableau Server so you can automate running flows to update the flow output instead of logging into Tableau Prep to manually run individual flows as your data changes. For more details, see Tableau Prep Conductor.

Tableau Prep Conductor is licensed through Tableau Data Management Add-on. For more information, see Licensing Tableau Prep Conductor(Link opens in a new window).

Tableau Data Management Add-On

The Data Management Add-on is a new licence that includes Tableau Prep Conductor. For more information, see Licensing Tableau Prep Conductor(Link opens in a new window).

Node roles for Backgrounder Process

A new tsm topology command that gives you the ability to specify the type of tasks that backgrounder can perform has been added. In 2019.1, using the new command, you can isolate certain nodes to run only flow tasks or run all tasks other than flows. This is useful if you are planning to use Tableau Prep Conductor to publish, run and schedule flows. For more information, see Workload Management through Node Roles and Tableau Prep Conductor.

SSL connection to Rserve external service

In previous versions, SSL connections to Rserve and TabPy were not supported. In Tableau Server 2018.3, you can configure SSL connections. In addition, connecting to external services is now enabling, disabling and configuring is now done with native tsm commands under tsm security.

Changed in 2019.1

Version 2019.1 includes the following changes you should know about before upgrading.

High-resolution thumbnails

In version 2019.1 and later, workbooks and views use higher resolution thumbnails. When you upgrade to Tableau Server version 2019.1 or later, the Backgrounder runs the Enqueue Thumbnails Upgrade job and the Upgrade Thumbnails job, which refreshes thumbnails for any views that have not been edited or published since Tableau version 2018.2 and converts them from low resolution thumbnail images (192 x192 pixels) to high resolution thumbnail images (300 x 300 pixels), as shown in the figure below.

When the Upgrade Thumbnails job refreshes the thumbnail images, the modified date of the view is changed to match the thumbnail update date. The Upgrade Thumbnails job does not change the modified date of workbooks when it updates the contained view's thumbnails.

Thumbnails may appear blurry until the Upgrade Thumbnails job is complete. Depending on the number of workbooks you have, this could a few minutes to a few hours. You may also notice that thumbnail images may appear in low resolution for up to a week after upgrading to Tableau Server 2019.1. For more information, see Upgrade Thumbnails Job(Link opens in a new window).

Project card images

In version 2019.1 and later, project card images will not appear on the project card unless they are added as the last item in the project description and encapsulated with ! (exclamation marks). For more information, see Add a Project Image(Link opens in a new window).

Version 2018.3

Added in 2018.3

Version 2018.3 includes the following new features.

Changes to Tableau Help

Search results within the product help have been expanded to include results for all Tableau products and help articles. Help layout and navigation, such as table of contents placement and breadcrumbs, have been updated to create a more consistent cross-product help experience.

User

Server or site administrator

Materialise calculations in extracts already published to Tableau Server

If you need to retroactively materialise calculations in extracts that have already been published to Tableau Server, you can use tabcmd to refresh the published extract with the --addcalculations option. For more information about materialising calculations in extracts, see Materialise Calculations in Your Extracts in the Tableau User Help. For more information about the tabcmd command option, see refreshextracts workbook-name or datasource-name.

Secure extract data at the row level

Secure your extract data at the row level using existing approaches for implementing row-level security in Tableau. For more information, see Restrict Access at the Data Row Level(Link opens in a new window) in the Tableau User Help.

Improved content browsing (in-release beta)

With Tableau Online and Tableau Server 2018.3, you and your web users can get a sneak preview of our reorganised content browsing experience. The new experience lets you see multiple content types – views, workbooks, data sources, flows, projects – in one grid or list. For example, you can now see all content inside a particular project and its sub-projects.

This new experience intends to make content discovery more intuitive, and it’s the first in a set of planned changes that are aimed at improving self-service and governance of your Tableau content.

To try the new browsing experience, enable the site-level setting we’ve provided for it. For more information, see Preview the Updated Content Browsing Experience.

After you enable the new experience, encourage your users to sign in to our Early Feedback(Link opens in a new window) site, share their thoughts with us, and see our regular development updates.

Support for Content Security Policy

Tableau Server supports the Content Security Policy (CSP) standard. CSP is intended to be an additional layer of security against cross-site scripting and other malicious web-based attacks. CSP is implemented as a HTTP response header that allows you to specify where external resources, such as scripts and images, can be safely loaded from.

See Content Security Policy.

Improved support for LDAP

Tableau Server 2018.3 includes improved support for LDAP, such as connection pooling, more flexible root configuration and commas in object class names. See the new topic, External Identity Store Configuration Reference.

Connections to external services support SSL

In previous versions, SSL connections to Rserve and TabPy were not supported. In Tableau Server 2018.3, you can configure SSL connections. In addition, connecting to external services is now enabling, disabling and configuring is now done with native tsm commands under tsm security.

SAML now supports PKCS#8 key files

You can now use password-protected key files with SAML. See Configure Server-Wide SAML. The passphrase is encrypted at rest along with other server secrets. See Manage Server Secrets.

Improved key and secrets refresh process

In previous versions of Tableau Server, refreshing server secrets, keys and tokens required that admins manually copied the keystore to each node in distributed deployments.

In Tableau Servefr 2018.3, the keystore is distributed to all nodes when you run the tsm security regenerate-internal-tokens command.

Backup without compression (added in version 2018.3.2)

Tableau Server version 2018.3.2 introduced a new option for the tsm maintenance backup command that allows you to disable compression when doing the backup. This can be beneficial for customers who have backups that take a long time. Using the option speeds up the time for the backup, but results in a larger backup file. If using this command option in a multi-node installation, we strongly recommend you have a File Store instance configured on your initial node to reduce the need to backup across nodes. To learn more about TSM backup, see tsm maintenance backup.

Changed in 2018.3

Version 2018.3 includes some changes you should know about before upgrading.

Connecting to secondary trusted Active Directory domains may result in error

A secondary domain is one that Tableau Server connects to for user synchronisation, but is a domain where Tableau Server is not installed. Tableau Server will attempt to connect to secondary domains for user and group synchronisation. But in some cases, Tableau Server will be unable to connect to the secondary domain, which will result in the error, "Domain not in allowlist (errorCode=101015)".

Setting the wgserver.domain.whitelist option in TSM is required by a fix for the security vulnerability, [Important] ADV-2020-003: Tableau Server Forced Authentication(Link opens in a new window). As of February 2020, the fix for this vulnerability is included in all latest versions and maintenance releases of Tableau Server. See wgserver.domain.allowlist.

Floating worksheet captions become transparent

To make a floating caption visible again, content authors will need to change the caption background to a colour.

Changes to some Data Engine tsm configuration set options

Two new configuration tsm set configuration options have been added: hyper.hard_concurrent_query_thread_limit and hyper.soft_concurrent_query_thread_limit

The new options replace the hyper.num_job_worker_threads and hyper.num_task_worker_threads options available in Tableau Server versions 2018.3 and earlier. The hyper.num_job_worker_threads and hyper.num_task_worker_threads have been deprecated and will no longer work in 2019.1 and later.

SSL Off-loading and SAML

Beginning with version 2018.3, Tableau Server validates SAML response message returned from the IdP. If your organisation terminates SSL connections from the IdP at a proxy server before sending the authentication request to Tableau Server, then users may be unable to login with SAML after you upgrade from 2018.2.

In this scenario, SSL is "off-loaded" at the proxy server, which means the https request is terminated at the proxy server and then forwarded to Tableau Server over http. Since SSL is off-loaded at the proxy, Tableau Server will validate with the protocol that it receives (http), but the IdP response is formatted with https, so validation will fail unless your proxy server includes the X-Forwarded-Proto header set to https. See Configuring Proxies for Tableau Server.

Version 2018.2

Added in 2018.2

Version 2018.2 includes the following new features.

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Include colleagues on data conversations with @mentions

To engage people in a conversation about compelling data you find in a view, @mention them in comments. As you begin to type a name, matching people with Tableau accounts at your organisation appear in a list you can choose from. For more information, see Comment on Views in Tableau User Help.

Site administrators can disable @mentions in the General section of site settings.

Tableau Services Manager

Tableau Server version 2018.2 introduced our new web-based server configuration and management application, Tableau Services Manager (TSM). TSM replaces tabadmin and the Server configuration utility from earlier versions. To learn more about TSM, see Tableau Services Manager Overview.

Dynamic topology support

The introduction of TSM enables support for dynamic, or "hot" topology changes. This allows you to change the number of Backgrounder and VizQL processes running on nodes that already have these processes – without the need to restart Tableau Server. To learn more about these and other Tableau Server processes, see Tableau Server Dynamic Topology Changes.

Lightweight Directory Access Protocol (LDAP) support

Tableau Server now supports Lightweight Directory Access Protocol (LDAP). To learn more about LDAP support in Tableau Server, see Identity Store.

Support for using SAML SSO with Kerberos database delegation

In a Windows Active Directory (AD) environment, you can enable SAML single sign-on (SSO) to Tableau Server, along with Kerberos database delegation. This provides authorised users direct access to Tableau Server, as well as to the underlying data defined in their published workbooks and data sources. See Use SAML SSO with Kerberos Database Delegation.

Manage Dashboard Extensions in Tableau Server

Dashboard extensions are web applications that provide users new ways to interact with data from other applications directly in Tableau. You can control the dashboard extensions that you allow to run in Tableau. You can manage an extension's access to data and can block extensions to prevent them from running. To learn more about controlling extensions, see Manage Dashboard Extensions in Tableau Server.

Changed in 2018.2

Version 2018.2 includes some significant changes you should know about before upgrading. The following sections summarise the significant changes to Tableau Server 2018.2 and provide links for additional information.

Tableau Services Manager

Beginning with version 2018.2, Tableau Server on Windows is available with Tableau Services Manager (TSM). TSM is the web-based server configuration and management utility that replaces the Server Configuration utility and the tabadmin command line utility. For server administrators who are familiar with earlier versions of Tableau, this means a lot of changes. You can learn about TSM and how it differs from the earlier configuration utility and tabadmin, by reading these topics:

Upgrading from an earlier version of Tableau Server (version 2018.1 or earlier) requires some special steps. If this is your situation, be sure to read this topic:

Moving the repository in a two-node cluster not supported

With the introduction of Tableau Services Manager (TSM), you can no longer move the repository off the initial (primary) node in a two-node cluster. In versions 2018.1 and earlier, you could add a second repository to your second node and then remove the first repository. With TSM you cannot add a second repository on a two-node cluster, and this means you cannot move the repository off the initial node.

Updates to Tableau Server Apache Logs

Apache log files stored in /logs/httpd now contain records with several formatting improvements, including the following:

  • Server names are shown according to the UseCanonicalName setting, which makes it easier to distinguish between nodes in a multi-node server deployment.
  • Date and time are now tracked in a single date-and-time string that can be readily recognised as a single value by a variety of data analysis tools, including Tableau Desktop.
  • Time zones are now easier to parse
    • On Linux, the numerical offset from UTC is provided.
    • On Windows, the name of the time zone is enclosed in quotes

Date, time and time zone formatting changes are illustrated by an example log entry from Tableau Server version 2018.1 and earlier releases:

::1 - - 2018-05-09 08:51:48.872 GMT Daylight Time 80 "POST /vizql/w/Regional/v/Obesity/sessions/A971A92AF77A4F4A9813065BDCEB24D6-0:0/commands/tabsrv/render-tooltip-server HTTP/1.1" "-" 200 445 "593" 135021 WvKolPH4UcM5KrzUbLi8EwAAA@E

For purposes of comparison, here is a log entry from Tableau Server version 2018.2:

10.210.24.3 127.0.0.1 - 2018-05-09T16:07:58.120 "GMT Daylight Time" 80 "POST /vizql/w/Superstore/v/Overview/bootstrapSession/sessions/185CCDC854A44765BB0298E93B403879-0:3 HTTP/1.1" "-" 200 136026 "784" 2370951 WvMOzgKIhfzh9kFWO@ow2gAAA1Y

The Read Only site role is now deprecated

The Read Only site role that was introduced in Tableau Server version 2018.1 is now deprecated. Any users assigned to the Read Only site role in version 2018.1 are reassigned to the Viewer site role after an upgrade to version 2018.2. To learn more about site roles, see Set Users’ Site Roles.

The tabcmd initialuser command prompts for password

In previous versions, the tabcmd initialuser command required a --password parameter to set the initial administrator password. In the tabcmd included with this version of Tableau Server, you can leave the --password parameter out of the command to be prompted in the shell instead. See initialuser.

Version 2018.1

Added in 2018.1

Version 2018.1 includes the following new features.

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Resize headers on the web

When editing a view on the web, you can resize the width of row headers and the height of column headers.

Streamline discussion threads by deleting comments

If a comment on a view is unnecessary or inaccurate, users can quickly delete it by clicking the X in the upper-right corner. For more information, see Comment on Views in Tableau User Help.

To disable the ability to delete comments, change the tsm configuration set option, vizportal.commenting.delete_enabled, to false.

New user-based term licences are now available

Tableau offers multiple types of user-based term licences that grant a range of web authoring and other capabilities at various price points, providing the flexibility for organisations to pay for the data analysis and data visualisation capabilities that each type of user in their organisation needs. To learn more, see User-based licences.

New and renamed site roles are now available

Starting in the version 2018.1 release, new and updated site roles are now available. To learn about these site roles, see Set Users’ Site Roles. To learn about changes in the REST API to accommodate new site roles, see What's New in the REST API.

Changed in 2018.1

Version 2018.1 includes some changes you should know about before upgrading. The following sections summarise the significant changes to Tableau Server 2018.1 and provide links for additional information.

Removed tabadmin command options

The previously deprecated --license and --administrator options are no longer available when using the tabcmd createsiteusers, tabcmd createusers and tabcmd syncgroup commands. These are breaking changes for any scripts that still use the --license or --administrator options. To update your scripts, use the --role option with these commands to specify the licence levels or site roles. For details, see tabcmd Commands.

Version 10.5

Added in 10.5

Version 10.5 includes the following new features.

User

New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users(Link opens in a new window) and Web Authoring and Tableau Desktop Feature Comparison(Link opens in a new window). For topics related to web authoring and interacting with views, see Using Tableau on the Web(Link opens in a new window).

Server or site administrator

Optimised server performance for data alerts

To improve overall performance, Tableau Server now rechecks failing data alerts only when it next checks data conditions for all alerts. You can revert to the previous setting, which checked failing alerts every 5 minutes, by changing the tabadmin set(Link opens in a new window) option, dataAlerts.retryFailedAlertsAfterCheckInterval, to false.

Nested projects

You can now create project hierarchies when you want to create content segments within a larger area. For example, create a project for each department, say Operations. In each of those top-level projects, separate content based on how the audience uses it, say connecting to certified data versus in-progress collaboration. For more information, see the following articles:

Filtered search hidden by default

Filtered search options are now located on the right side of pages, and are hidden by default. The toggle is a dark icon () when the Filters pane is open and a light icon () when the Filters pane is closed. For details on searching, see Search Content.

To use filtered search, click .

Tableau Data Engine with Hyper

Hyper is Tableau's new in-memory Data Engine technology optimised to bring faster extract and query performance, and increased scalability. You can now analyse large data sets faster and faster extract creation. For more information, see Tableau Server Data Engine.

Extracts use the new .hyper format

Beginning with version 10.5, new extracts use the new .hyper format. Extracts in the new format take advantage of the improved data engine, which supports the same analytical and query performance as the data engine before it, but for even larger extracts. Similarly, when an extract task is performed on a .tde extract using version 10.5, the extract is upgraded to a .hyper extract. For more information, see Extract Upgrade to .hyper Format.

Changes to the way values are computed

To improve data source efficiency and scalability, and produce results that are consistent with commercial databases, values in your data source can be computed differently in version 10.5. In some cases, these changes can cause differences with the values and marks in your view between version 10.4 (and earlier) and version 10.5 (and later). This applies to extract data sources, and can apply to multi-connection data sources, data sources that use live connections to file-based data, data sources that connect to Google Sheets data, cloud-based data sources, extract-only data sources and WDC data sources. For more information, see Changes to values and marks in the view in the Tableau User Help.

Changed in 10.5

Version 10.5 includes some changes you should know about before upgrading. The following sections summarise the significant changes to Tableau Server 10.5 and provide links for additional information.

Tableau Server configuration changes

Hyper powers the new Data Engine in Tableau Server 10.5 and introduces the changes described below. For more information, see Tableau Server Data Engine.

Beginning with version 10.5, Tableau Installer automatically installs Data Engine when you install file store, Vizportal, VizQLServer, data server or backgrounder and cannot be installed separately. Every node that has an instance of one of these processes will also have a single instance of the data engine process. You can no longer configure more than one instance of data engine on a node. To learn more about Tableau Server Processes see Tableau Server Processes.

Previously, in versions 10.4 and earlier, for distributed installations, the backgrounder process launched temporary instances of data engine (tdeserver64.exe) process during extract creation or refreshes. In Tableau Server 10.5, a single instance of data engine is installed automatically when you install backgrounder. The backgrounder process uses this single instance of data engine that is installed on the same node. For more information on configuration recommendations, see Distributed Installation Recommendations.

Upgrade may affect your current configuration for a multi-node cluster, especially if you have certain processes isolated on a separate node. For more information, see Tableau Server Data Engine.

Changes to extracts

Beginning with version 10.5, new extracts use the new .hyper format. The improved data engine can read both the .tde and .hyper file formats, so the latest version of Tableau Server can continue to view and read workbooks that are using .tde extracts.

Existing extracts will not automatically be upgraded to the new .hyper format during the Tableau Server or Tableau Desktop upgrade process. Only when certain extract tasks are performed on the .tde extract, the extract is upgraded to the .hyper format. For example, an automatic or scheduled refresh will upgrade a .tde extract to a .hyper extract.

NOTE: Use the Extract API 2.0 to create (.hyper) extracts, which requires Tableau 10.5 and later. If you are using Tableau 10.4 and earlier, continue to use the Tableau SDK to create .tde extracts. The Tableau SDK is no longer being maintained. For more information, see Extract API 2.0.

Version compatibility

Upgraded extracts are not backward compatible. After extracts are upgraded from .tde to .hyper format, they cannot be opened or refreshed in Tableau Desktop 10.4 and earlier. Tableau recommends that Tableau Server and all Tableau Desktops in your organisation be on the same version and be upgraded to 10.5 on the same schedule. For more information on specific extract compatibility scenarios, see Impact of extract upgrade

Viewer (can publish) and Unlicensed (can publish) site roles removed

The site roles Viewer (can publish) and Unlicensed (can publish) have been deprecated and are no longer available. Users who have either of these site roles on Tableau Server 10.4 or earlier will be reassigned in Tableau Server 10.5.

Deprecated site role In 10.5 is reassigned to
Viewer (can publish) Viewer
Unlicensed (can publish) Unlicensed

Nested projects and content navigation

You can now create project hierarchies when you want to segment content into sub-sections within a larger area. For example, you might create a project for each department. In each of those top-level projects, you can separate content based on how the audience uses it, such as connecting to certified data versus in-progress collaboration. For more information, see the following articles:

Nested projects and tabcmd

Using tabcmd, you can specify only a top-level project in a project hierarchy. To automate tasks you want to perform on a sub-project or content in a sub-project, you must use the equivalent Tableau REST API(Link opens in a new window) call.

Not all actions are available through the REST API. If you use Server on Windows and want to run an unscheduled extract refresh or append a file to an extract, a possible alternative is to use the Tableau Data Extract Command Line Utility(Link opens in a new window).

Filtered search hidden by default

Filtered search options are now located on the right side of pages, and are hidden by default. The toggle is a dark icon () when the Filters pane is open and a light icon () when the Filters pane is closed. For details on searching, see Search Content.

To use filtered search, click .

Thanks for your feedback!