Bug 996887

Summary: Notification email on task escalation misses last character
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED NOTABUG QA Contact: Radovan Synek <rsynek>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.0CC: kverlaen, mrietvel, mswiders, rsynek, smcgowan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-04 13:20:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
escalation process definition none

Description Radovan Synek 2013-08-14 08:46:17 UTC
Created attachment 786457 [details]
escalation process definition

Description of problem:
Having a simple HT scenario (see an attachment) with defined notification & reassignment deployed & started in Business Central. After specified timeout email has been sent as configured in the notification property of task, but the email was missing the last character. The text is passed to process instance as parameter - with value "Escalation text". But the email I received contained body: "Escalation tex".
I have been using both GreenMail and Wiser libraries for email testing, so I guess there cannot be the same bug in both of them.


Version-Release number of selected component (if applicable):
community 6.0.0.CR1

Comment 1 Marco Rietveld 2013-08-23 14:23:42 UTC
Radovan and Maciej have established that this problem only happens via REST, and not via the UI, which is why I'm now investigating this problem.

Comment 2 Marco Rietveld 2013-08-23 15:02:42 UTC
Kris has categorized this as a low-priority bug. I'm stopping any work on it and probably won't get back to it for at least a week.

Comment 3 Radovan Synek 2013-08-23 15:16:45 UTC
tested with 6.0.0.ER1 again and the behaviour is different than in community 6.0.0.CR1 - whole content of the escalation email's body is missing.

Comment 4 Marco Rietveld 2013-08-29 20:41:00 UTC
Please retest this with ER3: there's info that indicates this problem may no longer exist with the ER3 release.

Comment 5 Radovan Synek 2013-10-01 09:13:47 UTC
Hi Marco,
indeed, this issue is not present in ER3 build. I am able to receive full email (I tried to start the process both via UI and REST)

Comment 6 Marco Rietveld 2013-10-04 13:20:26 UTC
Thanks, Radovan!

Setting this to CLOSED/NOTABUG since Radovan has confirmed that it works in ER3.