As in previous generation of Xpoda (Octopod) sound alert added to client notifications.
The business intelligence reports you created using Microsoft Power BI are now available in Xpoda Studio.
You can reach the details from the following documentation:
https://docs.xpoda.com/hc/en-us/articles/7144182021020-Power-BI-Report
Calendar element Edit forms could only be called from its own module. This restriction has been removed and the ability to specify Calendar element Edit forms from other modules has been added.
It has been observed that the reports containing Sub Report, which are used in printout designs, do not work in Print actions or in Send Mail actions with an e-mail attachment.
This problem has been fixed with version 2.14.
Assistant ID and other information were not displayed in the error logs that occurred in Xpoda Assistant. This made it difficult to solve the problems that occurred in Assistant.
This problem was solved with version 2.14 and detailed information was provided in the records inserted to the XPODA_ERROR_LOGS table.
In projects which uses Create New Revision action, all form data is filled.
However, an error is received when trying to open the uploaded file.
When the revision is made again, the file is corrupted and cannot be viewed at all.
This error has been fixed with version 2.14.
In Change Properties action, Hide (No spaces when the field is hidden) and Visibility (It will show hidden area with space) Type fields were working problematic in Check box group and Radio group form elements.
Check box group and Radio group form elements hidden with these options at form opening, it has been observed that the elements are incorrectly positioned.
This problem has been fixed with version 2.14.
If the decision component used in the flow checks the value of a component in a different tab in the form, it has been detected that the flow is interrupted and does not progress.
This issue has been fixed in release 2.14.
An ("unterminated string passed...") error has been detected when an user clicks a list row and that row triggers "Open Form Detail" action and a record is present in list with any special character in it e.g #$!/ etc.
This issue has been fixed in release 2.14.
It has been determined that when logging into the Lite application from mobile devices, non-admin users give an error on the splash screen, the menu stays open and the menu open/close button does not work.
It has been observed that users with admin privilege do not encounter this situation. The problem has been resolved with version 2.14. Customers experiencing problems should update their Xpoda Client to version 2.14.
The sizing problem of the switch element on the horizontal axis has been solved with version 2.14.
The use of the parenthesis () special character in the queries written inside the Xpoda List element caused the data not to appear in the list.
This bug has been fixed with release 2.14.
It has been found that the Close Form operation does not work in the forms opened with In The Same Tab and In New Tab parameters.
The bug has been fixed with version 2.14.
Decision components used in the Xpoda flow which are set to control the numeric box field in the form don't work when the client language has been changed to another language.
This bug has been fixed with release 2.14.
In the tests performed, it was determined that the Xpoda Addon methods was called twice after the list records were filled using the value update operation. As a result, this problem, which creates performance and stability problems, has been fixed with release 2.14.
When the "Send Attached File" feature is used in the Flow Approvals, it has been found that the following error log is inserted in the XPODA_ERROR_LOGS table and the confirmation mail is not sent.
The error has been resolved with release 2.14.
Details of the error:
System.InvalidCastException: Unable to cast object of type 'System.String' to type 'System.Byte[]'.
For Assistant multi-recipient sendings, only semicolon ";" is used as a separator. The comma "," character is also added as accepted separator character. You can now also send recipient lists with comma characters.
It has been determined that the Before Recording action does not work in with any operation.
The problem has been fixed with version 2.14. Our customers who use the Before Recording action should consider that this action is not compatible with some operations. For example, operations such as value update may not work in compatible with this action. Operations such as Send Mail can work without any problem.