When data from TIBCO BusinessWorks is sent to the TIBCO iProcess Engine, some of the decimal fields appear to be corrupted.

When data from TIBCO BusinessWorks is sent to the TIBCO iProcess Engine, some of the decimal fields appear to be corrupted.

book

Article ID: KB0090432

calendar_today

Updated On:

Products Versions
TIBCO iProcess Engine (Oracle) -
Not Applicable -

Description

Resolution:
Description:
============
When a TIBCO BusinessWorks Process (BW) calls a TIBCO iProcess Engine (iPE) procedure, the below error is seen in the sw_warn log file –

2012/06/04 14:57:14. 820230(BG:2:17320:2:::CR1:pro:/prodata.c:83187:1349): 1644-Invalid field Value: Procedure &ltMON>, Case &lt291589703>, Step &ltCR1>: &ltMON, 3740657,00>

In the BG Debug log -

[T=4084549824]120604145714.819241:c004: ==&gtput_a_variable(ID_PREMON_SW, 3740657,00, Assigned)
[T=4084549824]120604145714.819270:c001: putvar(MON,3740657,00) - invalid value

Environment:
============
All supported versions of the TIBCO iProcess Engine
All supported platforms

Resolution:
==========
If the BW process is deployed on an operating system whose locale settings are different from those set on the operating system for iPE, the decimal separator may be different.  In the above example, the BW operating system was set to Italian (which uses a comma separator) while iPE was set to an English locale (that uses period as a separator). The BW process needs to be modified to send data that uses the appropriate separator for the locale in use in iPE.

Issue/Introduction

When data from TIBCO BusinessWorks is sent to the TIBCO iProcess Engine, some of the decimal fields appear to be corrupted.