Download Installation Guide

Installation Guide
APPENDIX E — UNICODE SUPPORT
The Metastorm Process Engine supports Unicode when running against a Unicode
database. When a Procedure is published, data is stored in the database in Unicode format.
All procedures and maps and the components that they contain are formulated as XML
files, XEP or XEL, that contain characters defined and stored in Unicode format.
The particular Unicode format that is employed is determined by the database, it is not
defined by the Designer. Designer determines the type of Unicode supported by the
database by examining the data type in the eServerName column in the eServer table. The
default value is Microsoft standard, UTF-16UCS-2.
Text and memo fields included in forms can contain data that is in Unicode format.
Windows Clients will convert Unicode Transaction Protocol custom variable strings to
their local code page equivalents. If a character does not exist in the Windows Client’s
code-page then it will be substituted and displayed incorrectly. If a field containing this
character is updated by the client (either manually by the user, or a client script), then the
incorrect character will be written back to the database. This issue will not arise for
Windows Client users that are using external HTML forms.
The Designer does not provide the facility to create scripts containing non-code-page
characters. If customers need this capability for example, using Japanese characters in a
script, then they will need to use an equivalent Unicode database.
See SMTP Setup for details of setting up code pages for e-mail.
This Appendix is relevant for Oracle and SQL Server.
Metastorm BPM Release 7.6
May 2008
Page 83