Localization issue on BDM data

Q&A
1

Hi all,

I am working on BonitaBPM 7.0 and find there’s a localization issue when referring BDM data in my forms, which cannot display Chinese characters properly.

BDM data is initiated with proper value, and I can see from clobvalue column in “data_instance” table (Postgresql DB) as below:
{“accountid”:“1”,“token”:“rAXRRuapwDsO5A”,“initialContent”:{“wxUserId”:“o9-uWuNuTZgTW2p_FYzzZ5E2dGuA”,“productType”:“1”,“description”:“我有一个问题”,“serverPhotoIds”:“kwI_EhxsId_Dr5cWOcT-QxdgNQaYyvvwcfHdFF816djDaSjaEi3go1W6WPcwLYKu”}}

However, when I refer to this data in my form with variable serviceRequestDetails which link to “…/{{context.serviceRequest_ref.link}}” and bind serviceRequestDetails.description to a text widget, the value shows in this text box become unreadable.

And I checked bdm REST API (http://192.168.100.121:8080/bonita/API/bdm/businessData/com.company.model.ServiceRequest/143) which returns unreadable characters too. So I believe this issue is caused by this REST API.

2

OK,

I would submit a formal Bug report on the Atlassian site: https://bonita.atlassian.net/secure/Dashboard.jspa

Pointing to this thread as well.

You should, if possible provide the bos file as well so they can look at it and, hopefully, figure out what’s going on.

regards
Seán

PS: I know this isn’t the answer you were hoping for, but I think it’s the nearest to a resolution you’ll get without getting a bug fix out of it…if you can mark as resolved it helps keep the database clean.

3

Things have moved on since 7.0.x have you tried this in 7.2.2 to verify if the problem still exists.

Note that Bonitasofts policy is to release fixes to the next release only - so 7.2.3 or 7.3.0 - unless you have a support contract (subscription).

If you still have the problem in 7.2.2 then I would submit a Bug report…

regards
Seán

4

Hi Sean,

Confirm 7.2.2 has same problem.

Both migrated BDM data and newly created data have same problem when I access them via bdm REST API.

The way I initial BDM variable is using a process variable. When I start a new case, I pass a JSON data to process variable, and then set to BDM variable.

Here is one example, description has this issue.

Unreadable result from BDM API:
{“persistenceId”:164,“persistenceId_string”:“164”,“persistenceVersion”:0,“persistenceVersion_string”:“0”,“accountID”:“1”,
“token”:“rAXRRuapwDsO5A”,“requestDescription”:“�9�”,“productCode”:“2”,“imageURLs”:,“raisedBy”:“o9-uWuNuTZgTW2p_FYzzZ5E2dGuA”,“raisedDate”:1461223565182}

======================================
Correct result from BPM caseVariable API:
{“case_id”:“3001”,“name”:“initialContent”,“description”:“”,“type”:“java.lang.String”,“value”:“{"accountid":"1","token":"rAXRRuapwDsO5A","initialContent":{"wxUserId":"o9-uWuNuTZgTW2p_FYzzZ5E2dGuA","productType":"2","description":"福费廷","serverPhotoIds":"TcpoFajEtVKoCXOnw2p7uf1p-OTnOE41x9yFWLRx4Zx8_PX1kKgn9MB6Xcmj2dcK"}}”}

5

error

 

6

keep it up

7

The localization issue on BDM data is a major problem in many countries. This issue has been discussed in many forums and a solution has been found. You can check roblox developer salary to get more information about marketing. But it is still not working properly due to some technical difficulties.

8

You could download bos file from here: http://pan.baidu.com/s/1dE1q4pj
This process has to use REST API to start and it must have one process variable “initialContent” with values of
{ "accountid":"1", "token":"rAXRRuapwDsO5A", "initialContent":{ "wxUserId":"o9-uWuNuTZgTW2p_FYzzZ5E2dGuA", "productType":"2", "description":"福费廷", "serverPhotoIds":"TcpoFajEtVKoCXOnw2p7uf1p-OTnOE41x9yFWLRx4Zx8_PX1kKgn9MB6Xcmj2dcK" } }