You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.

Identifier

Component

Issue

Solution

CSD-4049

 

Cases are locked in the database when a task is started. Unlocking the case and checking if a case is locked happens by consulting the Hibernate model. We know that Hibernate does not always synchronize with the database when we expect it, which may cause inconsistencies between case being locked/unlocked (a case may appear to be locked while it is not and vice versa).

Like acquiring the lock, unlocking/checking if the lock exists happens through the database instead of Hibernate. Also, when a case is unlocked that was not locked, an exception is thrown indicating this. Lastly, logging was added when a case is unlocked so we can see when this action happens in the log.
 
The changes may result in different behaviour of your application. Specifically, it may be more strict than before, as it is not possible anymore to for instance complete a task with case locking enabled, without a case lock being present. While this is a good thing, know that it is still possible to revert to the legacy behavior using the legacy toggle blueriq.legacy.use-legacy-case-unlocking.

CSD-4037

versionmanagement

Deleting a branch would not allow tags in that branch to be reused again

When a branch is deleted, all tags that correspond with revisions that are specific to that branch are now also deleted.
  • No labels

Didn't find the answer you were looking for? Try the advanced search!