Hi,

No, this is not possible.

The K2 database uses an Identiy column to assign Process Instance Ids, and when a new process instance is created, the newest identity value will be assigned to the process and this value cannot be changed.

Regards,

Thanks very much for your reply Johan.

Hi JohanL,

Can you please clarify if there exists any chances where the process instance ids could be reset to previous values (if the connected Oracle database has been set to a new instance)?
And if so, what are the possibilities for such a situation to occur?

Thanks and Regards,
Chandrala

Hi Chandrala,

I guess a manual database modification (which is unsupported by K2) which resets the identity seed on the ProcInst table could cause the values to be reused, but that would cause a lot of problems with reporting and you would probably experience very strange behaviour.

Alternatively, if your solution was moved to a different K2 server, the new K2 server might have a lower counter on the ProcInst table and could use the same Ids as with the other K2 Server. Or alternatively if you have a QA server but someone incorrectly updated the environment fields of this server and had it point to your production Oracle database saving the incorrect Process Instance Ids to the tables.

Other than the above I don't know of any other way.

Regards,