 | Running FileCatalyst Direct with Windows Vista | |
 | Windows VISTA includes a security feature called User Access Control (UAC), which is enabled by default. If UAC is disabled, FileCatalyst can be installed on Windows Vista like all previous Windows operating systems and you do not need to follow the inst |
|
|
| data too long for column 'RecipeintEmail' at row 1 | |
| With older versions of our web applications, users might enter a large number of recipients into their list (exceeding 256 characters), resulting in the error:
Error saving transaction, Exception saving job, Data truncation: Data too long for column 'R |
|
|
| Two-Way Applet: workaround for remote file listing failure (Linux) | |
| Scenario: FileCatalyst Server is deployed on a Linux / *nix machine that is localized and has its language set to a particular subset of UTF-8 encoding. When a client connects via the Two-Way Applet, they see an "option not understood" error in the log |
|
|
| Extend HotFolder with postURL | |
| Synopsis:
This tutorial shows how to use postURL to send transaction details to a PHP script at a specified URL for further processing.
Requirements:
FileCatalyst Server
FileCatalyst HotFolder or Applets
|
|
|
| FileCatalyst Server - port configuration (fix failing transfers) | |
| Overview: You have completed installation of both client and server apps, but are unable to transfer. It may be a port issue.
If the following scenario sounds familiar, this article may be for you:
Scenario: Y |
|
|
| FileCatalyst Webmail and Workflow Online Documentation | |
| If you are interested in browsing through the documentation that is available from a deployed version of FileCatalyst Webmail or FileCatalyst Workflow, we have created two special links that will let you do so without actually installing the applications: |
|
|
| UnlimitedFTP and use of UTF-8 encoded characters. | |
| The server needs to have UTF-8 supported. To enable this please check with yoru server operating system.
In uftpscript.js include this value to "var characterEncoding":
var characterEncoding = "UTF-8";
Further down the document, below this line: |
|
|
