KB-Entries 20.3.0: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Keine Bearbeitungszusammenfassung |
Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
== New Features == | == New Features == | ||
{{ | {{ | ||
| Zeile 18: | Zeile 8: | ||
|TextKB=A button has been created to clean up duplicate range names with reference to the dictionary that have been caused by copying worksheets. These prevent the correct translation on the respective worksheets. | |TextKB=A button has been created to clean up duplicate range names with reference to the dictionary that have been caused by copying worksheets. These prevent the correct translation on the respective worksheets. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 27: | Zeile 18: | ||
|TextKB=The decimal places of the data in continuous text can now be freely selected. Previously, this was only possible by multiplying or dividing by the factors one thousand, one million or one billion; thanks to the newly introduced factor 1, conversion is no longer necessary. | |TextKB=The decimal places of the data in continuous text can now be freely selected. Previously, this was only possible by multiplying or dividing by the factors one thousand, one million or one billion; thanks to the newly introduced factor 1, conversion is no longer necessary. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 36: | Zeile 28: | ||
|TextKB=A table is automatically created with imported data from the MeetingPoint, so that time can be saved through the prescribed table structure. Account group and key dates are selected, whereupon the appropriate values are inserted by firesys from the MeetingPoint. | |TextKB=A table is automatically created with imported data from the MeetingPoint, so that time can be saved through the prescribed table structure. Account group and key dates are selected, whereupon the appropriate values are inserted by firesys from the MeetingPoint. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 45: | Zeile 38: | ||
|TextKB=In the Data import manager, the first 500 data records will be displayed in the list view in future. | |TextKB=In the Data import manager, the first 500 data records will be displayed in the list view in future. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 54: | Zeile 48: | ||
|TextKB=If a new Import definition is created, it is assigned the status "?" (Undefined) because the records have not yet been imported. | |TextKB=If a new Import definition is created, it is assigned the status "?" (Undefined) because the records have not yet been imported. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 74: | Zeile 69: | ||
|TextKB=Assigning a color scheme reset the format of an unconnected graphic to "Default". This error was fixed with the release of version 20.3.0. | |TextKB=Assigning a color scheme reset the format of an unconnected graphic to "Default". This error was fixed with the release of version 20.3.0. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 83: | Zeile 79: | ||
|TextKB=The "Align Elements" application of the *firesys layout and the "Adjust Type Area" application of the Layout functions could not be applied to tables or marginalia temporarily. This bug was fixed with the release of version 20.3.0. | |TextKB=The "Align Elements" application of the *firesys layout and the "Adjust Type Area" application of the Layout functions could not be applied to tables or marginalia temporarily. This bug was fixed with the release of version 20.3.0. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 92: | Zeile 89: | ||
|TextKB=When designing tables using the Table assistant, every second row was printed in bold. This bug was fixed with the release of version 20.3.0. | |TextKB=When designing tables using the Table assistant, every second row was printed in bold. This bug was fixed with the release of version 20.3.0. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 101: | Zeile 99: | ||
|TextKB=When opening the Page Layout function, the current state of the opened document was not displayed until now. This bug has been fixed with version 20.3.0. | |TextKB=When opening the Page Layout function, the current state of the opened document was not displayed until now. This bug has been fixed with version 20.3.0. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 110: | Zeile 109: | ||
|TextKB=It could happen that documents with firesys layout started slower in certain documents and certain situations. This error was fixed with the release of version 20.3.0. | |TextKB=It could happen that documents with firesys layout started slower in certain documents and certain situations. This error was fixed with the release of version 20.3.0. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 119: | Zeile 119: | ||
|TextKB=After updating the software, the correct version is now displayed. | |TextKB=After updating the software, the correct version is now displayed. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 128: | Zeile 129: | ||
|TextKB=Several topics in the HTML code have been adapted regarding the Web version. | |TextKB=Several topics in the HTML code have been adapted regarding the Web version. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 137: | Zeile 139: | ||
|TextKB=Until now, the drop-down menu did not clearly indicate that the key date in the Data import manager could not only be selected, but also entered manually. Now this option is also visually recognizable. | |TextKB=Until now, the drop-down menu did not clearly indicate that the key date in the Data import manager could not only be selected, but also entered manually. Now this option is also visually recognizable. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 146: | Zeile 149: | ||
|TextKB=A created story no longer takes all tags from the master, but only tags associated with the particle. | |TextKB=A created story no longer takes all tags from the master, but only tags associated with the particle. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 155: | Zeile 159: | ||
|TextKB=Tables linked via toolsxbrl have lost their connection after being edited in Word. | |TextKB=Tables linked via toolsxbrl have lost their connection after being edited in Word. | ||
}} | }} | ||
{{ | {{ | ||
| Zeile 165: | Zeile 170: | ||
}} | }} | ||
== See also == | == See also == | ||
Version vom 6. Oktober 2020, 09:25 Uhr
New Features
Button was created for removing duplicate range names
| |
|---|---|
 |
 | 
|
A button has been created to clean up duplicate range names with reference to the dictionary that have been caused by copying worksheets. These prevent the correct translation on the respective worksheets.
|
Select decimal places for data in continuous text
| |
|---|---|
|
 | 
|
The decimal places of the data in continuous text can now be freely selected. Previously, this was only possible by multiplying or dividing by the factors one thousand, one million or one billion; thanks to the newly introduced factor 1, conversion is no longer necessary.
|
Automated worksheets
| |
|---|---|
|
 |
|
A table is automatically created with imported data from the MeetingPoint, so that time can be saved through the prescribed table structure. Account group and key dates are selected, whereupon the appropriate values are inserted by firesys from the MeetingPoint.
|
Number of records in the Data import manager increased in the preview
| |
|---|---|
|
|
|
In the Data import manager, the first 500 data records will be displayed in the list view in future.
|
Newly created definition is assigned the status "question mark"
| |
|---|---|
|
|
|
If a new Import definition is created, it is assigned the status "?" (Undefined) because the records have not yet been imported.
|
Highlight master values
| |
|---|---|
|
|
|
Master values are numbers from the MeetingPoint that have been inserted into Excel by using "Insert values". These can be highlighted by underlining, whereby underlining in the workbook is consequently only reserved for this highlighting.
|
Bugfixes
Color scheme changes the format of graphics
| |
|---|---|
|
 |
|
Assigning a color scheme reset the format of an unconnected graphic to "Default". This error was fixed with the release of version 20.3.0.
|
Tables and marginalia could not be aligned
| |
|---|---|
|
|
|
The "Align Elements" application of the *firesys layout and the "Adjust Type Area" application of the Layout functions could not be applied to tables or marginalia temporarily. This bug was fixed with the release of version 20.3.0.
|
Error in table module of firesys layout
| |
|---|---|
|
|
|
When designing tables using the Table assistant, every second row was printed in bold. This bug was fixed with the release of version 20.3.0.
|
The page layout dialog did not show the current state
| |
|---|---|
|
 |
|
When opening the Page Layout function, the current state of the opened document was not displayed until now. This bug has been fixed with version 20.3.0.
|
firesys started slower in some cases
| |
|---|---|
|
|
|
It could happen that documents with firesys layout started slower in certain documents and certain situations. This error was fixed with the release of version 20.3.0.
|
Wrong firesys version was displayed
| |
|---|---|
|
|
|
After updating the software, the correct version is now displayed.
|
Changes in HTML code
| |
|---|---|
|
 |
|
Several topics in the HTML code have been adapted regarding the Web version.
|
Watermark for key date in the Data import manager
| |
|---|---|
|
|
|
Until now, the drop-down menu did not clearly indicate that the key date in the Data import manager could not only be selected, but also entered manually. Now this option is also visually recognizable.
|
Story adopted tags from the master
| |
|---|---|
|
 |
|
A created story no longer takes all tags from the master, but only tags associated with the particle.
|
Tables linked by tagger lost connection
| |
|---|---|
|
|
|
Tables linked via toolsxbrl have lost their connection after being edited in Word.
|
Status information of stories was not displayed
| |
|---|---|
|
|
|
It was not possible to see the status of a story in the Content manager. Starting with version 20.3.0 the status info is displayed in the Content manager.
|
See also
The firesys Knowledge Base
The new features of version 20.2.2
The new features of version 20.3.1