Developer Blog |
We're happy to announce that Appway 6.3.2 is now available for download. It contains 1 new feature, 4 changes and 21 bug fixes in the core.
Version 6.3.4 of the ComponentExtension has also been released. This version contains 1 new feature, 1 change and 5 bug fixes.
Highlights of this release include:
Text Editor [CK]
We have upgraded the 3rd party JavaScript library "CK Editor" used to implement the Text Editor screen component. This solves several browser compatibility bugs we have seen with this component.
Workspace
Appway now always generates a Viewport definition for every screen. This improves the user experience when accessing an Appway solution from a mobile device.
IMPORTANT: PDF Rendering
Appway now sets the current translation language to the text language defined in the PDF document action or PDF render configuration when rendering a PDF Output. This fixes issues we have seen when using catalogs with a translation filter. Previously, the labels in such a catalog have been translated based on the current user's translation language, completely ignoring the text language defined by the Appway developer. As a result, labels have been translated to different languages depending on how they have been referenced from within the PDF Output or PDF Output Table business object. The new behavior is now consistent with all language-related features of PDF generation in Appway.
However, this change may also have an effect on the format of dates in PDF documents.
If you did not specify a format explicitly, the PDF renderer may have selected a date format based on the current user's translation language. The user's translation language could be different from the language of the PDF Output Business Object, and different from the language specified as "text language" in the PDF document action or PDF render configuration.
As a result, different users may have seen dates printed in different formats for the same PDF Output. After this change, the date format selected by Appway always depends on the text language you have specified in the PDF document action, or PDF render configuration. This leads to a consistent result, no matter which user is printing a PDF document.
This change does not have any impact on single-language solutions, or in cases where the date format is explicitly defined when printing dates on PDF documents (e.g. with the function "DATEFORMAT").
---
No special actions are required when upgrading from Appway 6.3.1 to 6.3.2.
For more comprehensive information, please consult the Appway 6.3.2 Release Notes (PDF).
Version 6.3.4 of the ComponentExtension has also been released. This version contains 1 new feature, 1 change and 5 bug fixes.
Highlights of this release include:
Text Editor [CK]
We have upgraded the 3rd party JavaScript library "CK Editor" used to implement the Text Editor screen component. This solves several browser compatibility bugs we have seen with this component.
Workspace
Appway now always generates a Viewport definition for every screen. This improves the user experience when accessing an Appway solution from a mobile device.
IMPORTANT: PDF Rendering
Appway now sets the current translation language to the text language defined in the PDF document action or PDF render configuration when rendering a PDF Output. This fixes issues we have seen when using catalogs with a translation filter. Previously, the labels in such a catalog have been translated based on the current user's translation language, completely ignoring the text language defined by the Appway developer. As a result, labels have been translated to different languages depending on how they have been referenced from within the PDF Output or PDF Output Table business object. The new behavior is now consistent with all language-related features of PDF generation in Appway.
However, this change may also have an effect on the format of dates in PDF documents.
If you did not specify a format explicitly, the PDF renderer may have selected a date format based on the current user's translation language. The user's translation language could be different from the language of the PDF Output Business Object, and different from the language specified as "text language" in the PDF document action or PDF render configuration.
As a result, different users may have seen dates printed in different formats for the same PDF Output. After this change, the date format selected by Appway always depends on the text language you have specified in the PDF document action, or PDF render configuration. This leads to a consistent result, no matter which user is printing a PDF document.
This change does not have any impact on single-language solutions, or in cases where the date format is explicitly defined when printing dates on PDF documents (e.g. with the function "DATEFORMAT").
---
No special actions are required when upgrading from Appway 6.3.1 to 6.3.2.
For more comprehensive information, please consult the Appway 6.3.2 Release Notes (PDF).

Comments (0)
