This has now been documented in the Process Instance section here [1].

Moving this to ON_QA.

[1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Administration_And_Configuration_Guide/index.html#Process_Instance

Vikram,

please see my comments below:
"With the release of the 6.1 version of Red Hat JBoss BPM Suite, this can be changed at runtime to allow the user to set locking on a per process basis and to allow it to be pessimistic. "

In fact, this setting can be applied on kie session level (or runtime manager level, if you want), not process.

inside example box:
"env.set(USE_PESSIMISTIC_LOCKING, true);" should be env.set(EnvironmentName.USE_PESSIMISTIC_LOCKING, true);

This line of code however shows little about how to use the setting. User can hardly guess where to put this "env". Another line where the environment is used to create a runtime manager or kie session would be helpful.

Thanks Radovan:

1. Since I added this in the section for Process Instance, I only mentioned about applying this setting to the Process. I have made a side note about applying this on a KIE Session or Runtime Manager Level as well.

2. Thanks for the fix regarding the missing EnvironmentName. I have fixed that.

3. Added another line to specify how to use this enviroment to create a Runtime Manager.

This can now be verified here [1].

Putting this back on to ON_QA.

[1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Administration_And_Configuration_Guide/index.html#Process_Instance

Verified with BPMS-6.1.0 ER6