When documents were added via query in the workflow, an attachment called "Document.pdf" with empty content was also sent, which should not be included in the email sent. This error has been fixed.
We aim to provide a better user experience with the new Xpoda Mobile Lite application. Xpoda users can start using the new application with version 3.2.
When using objects, if the object query contained $P and this field was a numeric field, the queries would produce errors. Therefore, the field within the object did not match the conditions and the flow did not continue with the decision selection. This error has been fixed.
When a file element (Add File) was used in a form, docx or xlsx was selected as the allowed file type, and the Mime Type Check setting was turned on in the Client settings, the Xpoda Client application became unresponsive and became unusable. This error has been corrected.
The error caused by the CSS changes made with the Chrome 120.* version update, which caused the window to not appear when copying the user menu from the admin panel, has been fixed.
When creating a public form link, a query can be written as $search=ValueField:TextToWrite in the URL query section. When this parameter is given, the fields with this name on the form receive initial values. This feature is used by many developers to select and load records as needed at the time of loading public forms.
However, when this URL was created as an embed and wanted to be used, this feature could not be used. You can now send search parameters when you use your public forms in embedded mode.
All you have to do is make the addition mentioned below in your embed code.
<script charset="utf-8" type="text/javascript" src="https://www.xpoda.com/xp-embed.js"></script>
<script>
xpodaforms.create(
{
fm: "MXFkWjBzRnlxZVax123kQxVFUmNUV3hlUm9ya1Z0MDhMdDdxSmNmQzFvcnU1&Search=Txt_1:deneme" ,
cl : "https://testxpo2.xpodacloud.com/" ,
search : "Txt_1:deneme"
}
);
</script>
An email confirmation link error was occurring in the Send E-Mail action.
The resulting confirmation link appeared as HTTP. Actually, this link should have been created as HTTPS. This error has been fixed.
When sending e-mail from the workflow or assistant, the design file specified in the client folder was not sent.
As in the Send Mail action sent from the form, a design file should have been sent, but this design file was not sent at all. The error has been fixed.