Topic | Bugs | Ticket (internal) | Layoutrobot | Expand |
---|
---|
title | Missing frame lines for server LAR |
---|
|
Error description:
Section |
---|
Column |
---|
|
Image Removed |
Column |
---|
|
A few frame lines are missing from the server-side layout robot |
Expected behaviour:
Section |
---|
Column |
---|
|
Image Removed |
The frame lines should be displayed.
#107534 . | Layoutrobot |
Expand |
---|
title | Additional vertical frame lines appear in the table |
---|
| Error description:
Section |
---|
Column |
---|
|
|
Column |
---|
| With the server-side layout robot, additional vertical frame lines appear. |
|
Expected behaviour: Section |
---|
Column |
---|
|
|
Column |
---|
| No additional frame lines should appear, as is the case with the client-side LAR. |
|
|
| #109025 | Factory | Expand |
---|
|
title | Change tracking mode in the sub-document does not work |
---|
|
Error description::
A Word snippet with changes cannot be checked in the sub-document. The following message appears:
Image RemovedTranslation: The file contains unconfirmed changes. Please accept or reject these changes before proceeding.
Expected behaviour:The change tracking mode should work as in the master.
#143852 | XBRL | Expand |
---|
title | Cells that are programmed with #l are evaluated as zeros and lead to errors. |
---|
|
Error description: The empty cells (#l) serve as header rows to keep the data view clear. The #l are apparently evaluated as zeros. This can be seen at the latest when the #l is deleted from Excel and Excel is checked in. No zero is displayed in the mapping dialogue and the cells are not tagged either. The error message "Error message: Unable to tag cell ..... Please check the format." Expected behaviour: Cells that are programmed with #l are not taken into account in the mapping dialogue because they do not contain any values and do not have to be tagged. Thus, there should be no error when the report is created. |
#142828 | HTML |
Expand |
---|
title | The space after the table and between marked paragraphs is not converted |
---|
| Error description: The spacing in(after) the table and between paragraphs is not converted. Expected behavior: The spacing after tables and between marked paragraphs should be maintained. |
| #137353 |
Word |
Expand |
---|
title | Footnote numbering consecutive instead of starting anew with 1 on each page |
---|
| Error description: In the word layoutmaster and in each supersnippet it is defined that the footnote numbering should start anew at 1 on each page. In the result document, the numbering is nevertheless continuous. Expected behavior: With this setting, the footnotes start anew with 1 on each page. |
| #121063 | Word | Expand |
---|
title | If a table has been highlighted in the course of a copy / roll forward, the highlighting will be lost the first time the table is reinserted. |
---|
| Error description: If a table has been highlighted in the course of a copy / roll forward, the highlighting will be lost the first time the table is reinserted. Expected behavior: The highlighting should also be retained when the table is inserted for the first time. |
#107602 |
Import |
Expand |
---|
title | Import: Oracle StoredProcedure not compatible with 2.9 |
---|
| Error description: The import via the Oracle StoredProcedure does not seem to work in 2.9. No numbers arrive and the process ends with "FinishedWithIssues".
Expected behavior: The data import should of course work.
|
| #127528 |
Layout Robot |
Expand |
---|
title | Layout robot: "German (Switzerland)" arrives user-def. number format incorrectly |
---|
| Error description: With German (Switzerland) as the stored language and this user format in Excel: # ##0\ _€;-# ##0\ _€ negative numbers arrive incorrectly in Word tables: In Word, negative numbers are shown in brackets. In Excel, however, there is a minus sign. Expected behavior: The numbers are displayed in Word in the same way as in Excel -> negative numbers with a minus sign.
|
| #117271 |
Layout Robot | Expand |
---|
title | Layout Robot: Updating the layout via the cockpit does not always update every table. |
---|
| Error description: Despite updating the layout via the cockpit, the layout of the tables remains incorrect and, for example, the German outarea is used instead of the English one. Expected behavior: The table layout and the outarea are displayed correctly. |
| #145806 |
Word |
Expand |
---|
title | Word: During the creation of result documents, defective Word files can be created due to too many styles |
---|
| Error description: The problem is that there are too many styles in the result document. Word only allows 4079, but in the case study over 5000 styles are defined in the result document. The document cannot be opened with Word - error message: /word/styles.xml is defective. After carrying out the Word repair, the document can be opened again. Expected behavior: The resulting document can be opened without Word repair. |
| #111935 |
Word |
Expand |
---|
title | Word: Footnote numbering consecutively instead of starting with 1 on each page |
---|
| Error description: In the layout master and in each supersnippet it is defined that the footnote numbering should start anew at 1 on each page. In the result document, the numbering is nevertheless continuous. Expected behavior: With this setting, the footnotes start anew with 1 on each page. |
| #120889 | Word | Expand |
---|
|
title | Word result document: result document cannot be created if "Remove content controls" is set |
---|
|
Error description:
If "Remove content controls" is checked in Word result document creation, this cannot be created.Expected behavior:
The result document is created.
Workaround:
In the Word result document, select the entire content with ctrl+a and right-click "Remove Content Control".
#136252 | XBRL |
Expand |
---|
title | XBRL: Tags end up in the wrong columns if the first tagged row contains joined rows |
---|
| Error description: There seems to be a problem if the first tagged row contains linked cells. If you dissolve the linked cells into individual cells, it also works with the transfer of the tags into the XHTML. It also works if you simply remove the tag on the first cell. Expected behavior: Tags should arrive correctly |
| #116484 |