Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1201900 - Task metadata being improperly stored in I18NText database table
Task metadata being improperly stored in I18NText database table
Status: VERIFIED
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core (Show other bugs)
6.0.3
Unspecified Unspecified
medium Severity medium
: ER4
: 6.2.0
Assigned To: Maciej Swiderski
Marián Macik
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-13 14:18 EDT by Amana
Modified: 2016-03-23 11:45 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1382483 None None None Never

  None (edit)
Description Amana 2015-03-13 14:18:25 EDT
Description of problem:

It seems like the metadata about a user task is not stored correctly in database. If setting a data to “Comment” property in “Extra properties” for a user task in bpm desginer, it stores the same text for “subject” and “description” fields in “I18NText” table after starting that task. 

By using Rest task query, it is possible to see that both fields are populated with the same data setup in Comment property:

(rest call) -> http://localhost:8080/business-central/rest/task/12

(output) -> <task><id>12</id><priority>0</priority><name><id>35</id><text>HT1 </text><lang>en-UK</lang></name><subject><id>36</id><text>summer</text><lang>en-UK</lang></subject><description><id>34</id><text>summer</text><lang>en-UK</lang></description>...

There don’t seem to be fields called “description” or “subject” in the BPM designer, so that it could be stored properly in database. It should be possible if those fields could be set separately. Otherwise, should they be used for what?


Version-Release number of selected component (if applicable):

6

How reproducible:

Always

Steps to Reproduce:
1. Create a really simple test containing a User Task;
2. In Extra Properties, add a data to Comment property and save all;
3. After deploying the process, start it and start the User task;
4. Before completing the task, use rest call or check I18NText table as above... the same data is populated to both fields!!

Actual results:

the same data is populated to both fields!!

Expected results:

same field should be populated with a different data, and it should be possible to set that from bpm desginer.


Additional info:
Comment 3 Kris Verlaenen 2015-03-13 17:04:34 EDT
This is how it was designer to work, there's only one property (Comment) in the process, this is translated to both Description and Subject in the WS_HT model.  We could extend the handler to support more properties, so you could set these separately.
Comment 12 Marián Macik 2015-10-26 10:17:09 EDT
Verified with 6.2.0.ER4 using REST.

Note You need to log in before you can comment on or make changes to this bug.