I have a process model that has multiple sub processes for a project.
Each sub-process references the project name that was created at the beginning of the process.
The project name is retrieved by calling a rule that then saves to a process variable.
At a sub-process further down the life-cycle, there is a user task (a) and the process is waiting for the user to complete the task.
Outside of this process model, anyone can go and update the project name. The name is then updated in the database.
My issue is that at this point (a) while waiting for the user task, the project name is not being updated even though the database has a new name and the process variable being reference is calling a rule to get the project name. All further sub-processes after (a) gets the updated project name. Only at (a) where the task was waiting to be completed when the name change occured, is not updated.
Does anyone have any idea of how to resolve this?
Discussion posts and replies are publicly visible
Why not just store the projectId in the PV? Pass in the projectId as a PV to the User Input Task, query the DB for the project info using the project id and display it to the user?
Mathieu Drouin - we are doing this. However, the user input task that it is sitting at does not get the updated name. If this task is completed and the process moves on, the next task gets the correct name.
Only the task that was waiting to be actioned when the name change happened, is not picking up the updated name. The name change happens outside of the process model