| Table of Contents |
|---|
...
This is the list of important limitations that are either being solved by the development team or are being addressed by Tableau:
HTTP/2 Zero-Day Vulnerability
| Info |
|---|
We are aware of the recently HTTP/2 Zero-Day Vulnerability (CVE-2023-44487) and Write-Back is not affected by this vulnerability. More info: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-44487 Starting on Write-Back 4.1, a proxy server is now included alongside the installation, so, by default, Write-Back is automatically protected against this type of attack, including this one. More on this here: https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html |
Springboot Vulnerability
| Info |
|---|
We are aware of the recently disclosed Springboot vulnerability (CVE-2022-22965) and Write-Back is not affected by this vulnerability. More info: https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement |
Log4j Vulnerability Fixed
| Info |
|---|
We are aware of the recently disclosed Apache Log4j2 vulnerability (CVE-2021-44228) and we have already provided fixes for Write-Back 3.1 and 3.2 available on Support & Resources. Please ensure you upgrade to latest versions. |
...
As of now, all dates submitted with the Write-Back data and time field don't have a timezone defined this means a single timezone should be agreed and users should do the conversion before entering the values. We have an improvement for this issue on the roadmap. Dates created automatically by Write-Back, for instance for auditing purposes, are stored on the server timezone and UTC.
Worksheet limitations
- Tableau forecasting model
When using the Tableau forecast model, due to the way that the Tableau API sends the data from the worksheet, some values can show up inconsistent or null. For the same field, there are different values (normal and forecast) and it is not possible to distinguish them on Write-Back and ensure data is correctly added.
You can read more about Tableau forecast models here.
- Multiple types of marks
Due to the way the Tableau API sends information, Write-Back cannot properly work when you have multiple types of marks on the same worksheet using the same field. It can happen that the same fields will have different values for each mark, or even, each mark can have a different set of fields.
- High volume of marks
If you want to use the form to add data with the option of selecting marks please do so without any limitation, however, if you do not want to select marks on the form or use the tabular screen please limit this configuration to sheets with up to 1000 marks on the visualization (shapes, bars, lines, etc). In these usage scenarios, we need to process all data and therefore beyond this value, you might notice a decrease in performance.
...