leo li [https://community.jboss.org/people/leo87601] created the discussion "Re: [jbpm5.1]Can get the current nodeId,correctly??" To view the discussion, visit: https://community.jboss.org/message/646954#646954 -------------------------------------------------------------- Thanks for you suggestion and we had tried to implement them, but we found following problem: 3.X It works in the way you want out of the box. For the Process Versioning,  the process instance's data is working fine, but process Definition is stored in Kbase, and we try to add both version on the same Kbase,but the Ksession don't know which version they should work with. It always work with the last one which we added into the Kbase.Attachment is our testing casees for this problem. Do the Process Definition (Kbase) and Ksession mapping should be maintanced by ourselves? Should we share the Kbase for diferent version snapshot? If Yes, I'm worry the older process request and newer process request happen concurrently, how should we handle that? 2.you never need to fix that table, never touch that table because it contains internal information from the engine, users should never touch that. We found that the JBPM5 doesn't raise any exception when concurrent request and there are  different status in the Process Instance and Node Instance,and the work item cannot be completed any more. For this problem,I think we have some way to fix error, no matter we fix them by changing db or invoking JBPM's API.  Would you mind let me know how to do that in JBPM5? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/646954#646954] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]