Bug 1294689

Summary: Kie Server 6.2 Client API documentation should be updated
Product: [Retired] JBoss BRMS Platform 6 Reporter: William Antônio <wsiqueir>
Component: DocumentationAssignee: Dawn Eisner <deisner>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.0CC: alazarot, brms-docs, tradej
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: 2020-03-27 19:46:06 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:

Description William Antônio 2015-12-29 17:26:55 UTC 
Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.2/html/Development_Guide/sect-Running_in_KIE.html#sect-Supported_JBoss_BRMS_Commands

Section Number and Name: 

16.5.6. Available API
16.5.7. Supported JBoss BRMS Commands

Describe the issue: 

The BatchExecutionHelper should not be used against Decision Server 6.2 as mentioned by Maciej on [1];

The use of this class will lead to problem when generating requests - a new approach is required and it is described in this article created by Anton -> [2];

Also, the suggested sample JSON does not work anymore
-----
JSON:

{"batch-execution":{"lookup":"ksession1","commands":[{"insert":{"object":{"org.drools.compiler.test.Person":{"name":"john","age":25}}}},{"fire-all-rules":""}]}} 
-----


Suggestions for improvement: 

* Update the documentation according [2];
* Replace the sample JSON by a working one, which probably should be:


{"batch-execution":{"lookup":"ksession1","commands":[{"insert":{"object":{"org.drools.compiler.test.Person":{"name":"john","age":25}}}},{"fire-all-rules": {} }]}} 

(notice the change in the fire all rules command)

(the JSON above was not tested)


Additional information: 


Links:

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1293736#c4
[2] https://access.redhat.com/solutions/1486613