Opened 6 years ago
Closed 6 years ago
#1064 closed defect (fixed)
The temporary case used for holding consent information blocks registration of the real case
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | critical | Milestone: | Reggie v4.19.1 |
Component: | net.sf.basedb.reggie | Keywords: | |
Cc: |
Description
When the consent form is the first form to arrive a temporary case is created. In some cases the temporary case is deleted and merged with a new case item when the referral form is registered. It seems like the new and stricter check for duplicate names is triggered by the temporary case and preventing the registration of the real case.
Change History (2)
comment:1 by , 6 years ago
Milestone: | Reggie v4.x → Reggie v4.19.1 |
---|---|
Status: | new → assigned |
comment:2 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [4959]) Fixes #1064: The temporary case used for holding consent information blocks registration of the real case
The problem was related to the temporary case, but in a slightly different way than initially expected. It works when the temporary case needs to be deleted since then there is already another existing case that will take it's place and no name check is performed.
The problem was when the temporary case "simply" should be kept and converted to a real case. This followed the same execution path as the "new case" path which includes a name check. The name check should not be performed when the temporary case already exists and no new case item is created.