Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Changing the Long Date Format

For information on using the long date and time format in an iProcess step definition, see “Using Embedded and Ampersanded Fields” in TIBCO iProcess Modeler Basic Design.

The `staffw.mes` file, which is located in the SWDIR`\etc\language.lng` directory, determines how the long date is displayed by iProcess Workspace. The long date information is returned from the `staffw.mes` file, which is located in the SWDIR`\etc\language.lng` directory, instead of the `staffpms` file, which is located in the SWDIR`\etc\language.lng` directory, because it enables different users on the same system to have different long date displays depending on their `LANGUAGE` attribute.

Note | See “Setting Pre-defined Attributes” in TIBCO iProcess Workspace (Windows): Manager's Guide for more information about how to set a user’s `LANGUAGE` attribute.

To ensure the date is displayed consistently in both TIBCO iProcess Workspace and iProcess Engine, the information in the `staffw.mes` and `staff.mes` files, which are located in the SWDIR`\etc\language.lng` directory, must be the same. This means that any changes must be made in both files.

The following example is an extract from the `staffw.mes` file, which is located in the SWDIR`\etc\language.lng` directory:

    0004:W:\\%s %s, %s\\dmy\\\ AM\ PM\Week
    0013:W:Sunday\Monday\Tuesday\Wednesday\Thursday\Friday\Saturday$
    0014:W:January\February\March\April\May\June\July\August\September\October\November\December

The file is divided into one message per line. The messages that determine how the long date is displayed are:

| • | `0004` specifies each component of the long date.

| • | `0013` specifies the days of the week.

| • | `0014` specifies the months of the year.

Each message is in the format:

`number:type:data`

where:

| • | `number` is the identifier for this message. For example, `0004`.

| • | `type` is either `W`, indicating that the message is used by TIBCO iProcess Workspace, or blank, indicating that the message is used by iProcess Engine.

| • | `data` is one or more data entries associated with this message. If there are multiple data entries, each entry is separated by a backslash (\) character.

For example, the following table describes the data entries for message `0004`.

Position | Data | Description
1 |  | Not used.
2 |  | Not used.
3 | `%s %s, %s` | The number of components used to specify each part of the long date format. Each component represents the date, month, and year. For example, `10 March, 2004`.
4 |  | Not used.
5 | `dmy` | The order of the date format.
6 |  | Not used.
7 |  | Not used.
8 | `AM` | Used for 12 hr time format. For example, `09:10 AM`.
9 | `PM` | Used for 12 hr time format. For example, `03:12 PM`.
10 | `Week` | Not used.

To change the long date format, for example, to `Wednesday 12 Dec, 2012`:

| 1. | Edit message `0004` of the `staff.mes` file located in the SWDIR`\etc\language.lng` directory as follows:

- Add `%s` to position 3 to represent the day of the week, as shown .

- Add `w` to position 5 to represent the day of the week, as shown .

- Edit message `0014` to use short month names rather than long ones. For example, `Dec` instead of `December`.

    0004:W:\\%s %s %s, %s\\wdmy\\\ AM\ PM\Week
    0013:W:Sunday\Monday\Tuesday\Wednesday\Thursday\Friday\Saturday$
    0014:W:Jan\Feb\Mar\Apr\May\Jun\Jul\Aug\Sept\Oct\Nov\Dec

| 2. | Replicate the changes made in the `staffw.mes` and the `staff.mes` files, which are located in the SWDIR`\etc\language.lng` directory.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.