OK that was tricky but I finally found out that: - I have to update table ACT_RU_ACTINST as well - the UPDATE ACT_RU_EXECUTION is actually: UPDATE ACT_RU_EXECUTION SET PROC_DEF_ID_ = 'userWorkflow:X:XXXX' WHERE PROC_INST_ID_ = <PROC_INST>;
It seems to work like this
Sorry for the noise, best regards
Lionel
----- Le 5 Oct 23, à 17:15, Lionel SCHWARZ lionel.schw...@in2p3.fr a écrit :
> Dear all,
>
> After deploying a new userWorkflow definition (PUT
> /flowable/bpmnProcesses/userWorkflow), I tried to upgrade a user to this new
> workflow, executing the following steps:
>
> - stop Syncope
> - connect to DB
> - get the definition id of the new workflow:
> SELECT ID_ FROM ACT_RE_PROCDEF WHERE KEY_ = 'userWorkflow' ORDER BY VERSION_
> DESC;
> - get the process instance of the user:
> SELECT ID_ FROM ACT_RU_EXECUTION BUSINESS_KEY_ = concat('userWorkflow:',
> <USERKEY>)
> - update both with the new definition id
> UPDATE ACT_RU_EXECUTION SET PROC_DEF_ID_ = 'userWorkflow:X:XXXX' WHERE ID_ =
> <PROC_INST>;
> UPDATE ACT_RU_TASK SET PROC_DEF_ID_ = 'userWorkflow:X:XXXX' WHERE ID_ IS NOT
> NULL AND PROC_INST_ID_ = <PROC_INST>;
> - restart Syncope
>
> But it seems something is still missing because updating the user does seem to
> use the new workflow...
> Is there another table to update?
>
>
> Regards
> Lionel
smime.p7s
Description: S/MIME Cryptographic Signature
