Show all
When you sign on, Process Commander
uses the time zone and output locale setting in your
Windows workstation as default values when you sign on. Use
this tool to set temporary values for your current time zone
and currency, to control the display of numbers and dates, and
to control the dictionary used for spellchecking.
Changing the locale for your current
session
To override these settings for the current session:
- Select Tools > Locale Settings.
- If desired, click Settings to review current locale
settings.
- Complete the panel.
- Click Update .
- Close the window.
Changes are effective immediately and remain in force
until you log off or choose another locale.
Changing the locale with this tool affects use of Process
Commander only. It does not update the locale established in
your Internet Explorer or Windows setting.
Field
|
Description
|
Locale Settings
|
|
Base
Currency
|
Optional. Identify a base currency using
International Standards Organization codes, such as
USD for United States dollars,
UKB for British pounds or JPY
for Japanese yen. The system stores this value in the
pyBaseCurrency property on the requestor
page, but does not otherwise use it.
Ordinarily, Java JVMs compute a base currency code
from the country code portion of the locale.
|
Use
Locale
|
Optional. Select
a locale description to be used for date, time, and
number formats for the duration of this session, to
override the locale defined in Windows.
For example, when you choose English-(United
Kingdom) , Process Commander displays dates in
the format 22 October 2003 15:20:31 EST. If you choose
English-(United States) , dates appear in
the format October 22, 2003 3:20:31 P.M. EST. When you
choose French-(France) , numbers appear in
the format 10.234,00. If you choose
English-United States , numbers appear in
the format 10,234.10.
These date formats follow the Unicode CLDR 1.3
standard.
|
Use Time
Zone
|
Optional.
Identify a time zone by code, such as America/New
York for Eastern U.S. time or GMT for
coordinated universal time, formerly known as Greenwich
Mean Time. The system stores this value in the
pyUseTimeZone property on the requestor
page.
Daylight savings
time rules are supplied by Java JDK vendors. In a
multinode system, it is important that the same rules
are installed on each node. For details of vendor JDK
support of daylight savings time and downloads, consult
one of the following links:
http://www-128.ibm.com/developerworks/java/jdk/dst/
http://java.sun.com/javase/tzupdater_README.html
http://www.hp.com/products1/unix/java/TZupdater_license.html
http://edocs.bea.com/jrockit/geninfo/diagnos/tzupdate.html
|
Changing locale permanently
To change these settings permanently on your Windows
workstation, use the Windows Start menu item
Settings> Control Panel >Regional Options
>General to set the workstation locale. Similarly,
use the Windows DateTime control panel to review or set time
zones.
Changing locale programmatically
An activity can change a user locale temporarily by
calling the PublicAPI function setLocale(). For
example, a multilingual worker might switch between English
and Spanish rapidly, to match the speech of an incoming
caller, by clicking a button on the Process Work
workspace.
This lets your application implement a user selection of
local (as production users do not ordinarily have access to
the Locale Settings tool).
Using the Demo applet to understand locale
settings
Click
Demo to
experiment with input and display values in the new setting.
This opens a new window that demonstrates the effect of the
locale setting on date and amounts.
Click Submit to
open the form. Enter values and click Compute .
For example, if you choose France as the locale, enter a date
and time in the European format (DD/MM/YY), the applet
displays the results in various formats:
This demonstration
facility downloads and installs a Java applet on your
Windows workstation to fetch the workstation locale. Your
workstation must contain a Java JVM and your Internet
Explorer settings must allow Java applet to run. Other
Process Commander operations do not require Java applets.
When you click Compute. The JVM on
the server, not the JVM on the workstation, performs the
computation.
Tools, accelerators, and wizards