Claim operation failing because Potential Owner information is not getting persisted

[rahul7163]

Hi Team,

I'm using jBPM 6.1.0 version with spring local transaction and singleton session strategy. I am running the start process code through jUnit.

My start workflow code is as follows:

RuntimeEngine engine = runtimeManager.getRuntimeEngine(EmptyContext.get());

KieSession ksession = engine.getKieSession();

ProcessInstance processInstance = ksession.startProcess(processId, paramMap);

runtimeManager.disposeRuntimeEngine(engine);

I am able to see the process is getting created successfully. However, first task in the process is exist in ready state and the peopleassignment_potowners table does not have any potential owner information. I remember, in jBPM 5.4 there were some data exist in the potowners table for the task.

My claim code is as follows:

RuntimeEngine engine = runtimeManager.getRuntimeEngine(ProcessInstanceIdContext.get(processInstanceId));

TaskService service = engine.getTaskService();

service.claim(taskId, userId);

runtimeManager.disposeRuntimeEngine(engine);

Am i doing anything wrong here?

[swiderski.maciej]

make sure you register user group callback that is aware of your users otherwise task service will remove all potential owners unknown to the callback - default callback won't know your users and that's why you won't be able to assign tasks to those users.

User group callback is registered via runtime environment when you create runtime manager

HTH