While UTF-8 encoding is more versatile than its alternatives, there are some issues which you should be aware of when deciding whether to use this encoding:
•
Some other multi-byte character encoding systems are more efficient than UTF-8, in terms of the number of bytes they use per character. This means that converting from such a system, for example from Big5 encoding of Chinese characters to UTF-8, will result in a larger database. Perhaps more importantly, some items may overflow the space designed for them. For example, an increase from using 2 bytes to represent a character to 3 bytes means that a case description limited to 24 bytes can only contain 8 characters rather than 12 characters.
•
The TIBCO iProcess Workspace (Windows) client does not itself use UTF-8 encoding. It converts data from the native character encoding for its locale to UTF-8 to send to the iProcess Engine, and similarly converts data it receives from the iProcess Engine from UTF-8. It is therefore possible that the same issue of space mentioned in the previous point could arise. Data entered in a native character encoding could end up being stored in the iProcess database as a larger number of bytes.
For these reasons, if you are using UTF-8 encoding, TIBCO recommends using TIBCO Business Studio for modeling processes, and either TIBCO iProcess Workspace (Browser), or an application that utilizes SSO for processing work items.
•
With multiple TIBCO iProcess Workspace (Windows) clients that use different locales, you must ensure that you do not address work items to users in different locales to prevent unpredictable results.