Bug 1141185 - A HandleResponseErrors field is not present by default in the DataInputSet of REST Service Task
Summary: A HandleResponseErrors field is not present by default in the DataInputSet of...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Marián Macik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-12 11:57 UTC by Marián Macik
Modified: 2015-12-14 13:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-14 13:00:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marián Macik 2014-09-12 11:57:45 UTC
Description of problem: Missing a HandleResponseErrors field in DataInputSet of REST Service Task. It should be there because this option was implemented as a result of BZ1098137.

Name of the field: HandleResponseErrors

Type of the field: String

Actual values are strings but it is then parsed to Boolean so only true/false values are considered.

As it was said, reason for adding this field is BZ1098137.

Comment 1 Kris Verlaenen 2014-09-12 13:39:40 UTC
As a workaround, isn't it possible to simply add this parameter to the inputSet yourself in case you need it?

This is kinda an optional parameter, and rather low-level, so we were trying to hide it for default users.  But we don't have a mechanism (yet) to define required vs. optional parameters (so the required are shown by default but it's easy do select additional, optional parameters later).

Comment 2 Marián Macik 2014-09-15 07:48:31 UTC
The workaround you mentioned is working. However, I just wanted to be sure it will be there (in the future as you wrote), so user will know there is an option to turn Exception Handling on/off. Right now, user has to know it from somewhere else.

Comment 3 Marián Macik 2015-12-14 13:00:23 UTC
I am closing it as not a bug and instead will create a documentation JIRA.


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