Question
Accenture
TR
Last activity: 2 Jul 2018 10:02 EDT
Opening an Existing Case Work Item from Flow Activity - pyCommitError DB Save using an insert failed
Hello,
We need to open an existing case from within another case using an activity but we are getting database insert error. It seems to be doing a Commit Action when we try to open the case.
Is there a way to NOT make a commit action or any possible solutions to this problem?
Thnx in advance. Please find the detailed problem description below:
Pega platform: 7.1.7
Problem: Opening an existing non resolved case with a known case ID in Perform mode. Main Case which will open the existing one is called UW, and case to be opened is ELM
- UW case calls the flow “ElmForUW” as sub process
- ElmForUW flow checks for existing elmas inquiry and if exists, gets the case ID and calls an activity to open existing work with case ID (pyID)
- In open existing case activity, We use Obj-Open with Class of the case: XX-FW-ELM-Work-ELMInqCase, also use stepPage directly with pyWorkPage which is also of the same class.
- When I run the flow ElmForUW, i get the following error: .pyCommitError: ** Database save using an insert failed
When Tracer is checked, we see that after finding related existing case, system is trying to do a commit action and gets an error, there are no previous errors.
Tracer errors are as follows:
Hello,
We need to open an existing case from within another case using an activity but we are getting database insert error. It seems to be doing a Commit Action when we try to open the case.
Is there a way to NOT make a commit action or any possible solutions to this problem?
Thnx in advance. Please find the detailed problem description below:
Pega platform: 7.1.7
Problem: Opening an existing non resolved case with a known case ID in Perform mode. Main Case which will open the existing one is called UW, and case to be opened is ELM
- UW case calls the flow “ElmForUW” as sub process
- ElmForUW flow checks for existing elmas inquiry and if exists, gets the case ID and calls an activity to open existing work with case ID (pyID)
- In open existing case activity, We use Obj-Open with Class of the case: XX-FW-ELM-Work-ELMInqCase, also use stepPage directly with pyWorkPage which is also of the same class.
- When I run the flow ElmForUW, i get the following error: .pyCommitError: ** Database save using an insert failed
When Tracer is checked, we see that after finding related existing case, system is trying to do a commit action and gets an error, there are no previous errors.
Tracer errors are as follows:
| 1332 | TABTHREAD4 | 1027 | 14 | Activity End | 7.4380 | @baseclass doUIAction | Pega-UIEngine 07-10-15 | |||||
| 1331 | TABTHREAD4 | 1027 | 14 | java | 21 | FAIL | Step End | 7.4120 | @baseclass doUIAction | Pega-UIEngine 07-10-15 | ||
| 1330 | TABTHREAD4 | 1027 | 16 | Activity End | 7.4110 | Work- NewFromFlow | Pega-ProcessEngine 07-10-11 | |||||
| 1329 | TABTHREAD4 | 1027 | 16 | Call New | 5 | FAIL | Step End | 7.4100 | Work- NewFromFlow | Pega-ProcessEngine 07-10-11 | ||
| 1328 | TABTHREAD4 | 1027 | 17 | Activity End | 7.4100 | Work- New | Pega-ProCom 07-10-15 | |||||
| 1327 | TABTHREAD4 | 1027 | 17 | Call Add | pyWorkPage | 12 | FAIL | Step End | 7.0020 | Work- New | Pega-ProCom 07-10-15 | |
| 1326 | TABTHREAD4 | 1027 | 26 | pyWorkPage | Activity End | 6.9860 | Work-Cover- Add | Pega-ProcessEngine 07-10-15 | ||||
| 1325 | TABTHREAD4 | 1027 | 26 | Call WorkCommit | pyWorkPage | 5 | FAIL | Step End | 4.5330 | Work-Cover- Add | Pega-ProcessEngine 07-10-15 | |
| 1324 | TABTHREAD4 | 1027 | 48 | pyWorkPage | Activity End | 4.5010 | Work- WorkCommit | Pega-ProcessEngine 07-10-01 | ||||
| 1323 | TABTHREAD4 | 1027 | 48 | Call HandleCommitFailure | pyWorkPage | 7 | GOOD | Step End | 2.7800 | Work- WorkCommit | Pega-ProcessEngine 07-10-01 | |
| 1322 | TABTHREAD4 | 1027 | 53 | pyWorkPage | Activity End | 2.7480 | Work- HandleCommitFailure | Pega-ProCom 07-10-01 | ||||
| 1321 | TABTHREAD4 | 1027 | 53 | Activity-End | pyWorkPage | 5 | GOOD | Step End | 0.0160 | Work- HandleCommitFailure | Pega-ProCom 07-10-01 | |
| 1320 | TABTHREAD4 | 1027 | 53 | Activity-End | pyWorkPage | 5 | Step Begin | Work- HandleCommitFailure | Pega-ProCom 07-10-01 | |||
| 1319 | TABTHREAD4 | 1027 | 53 | Call DisplayHarness | pyWorkPage | 4 | GOOD | Step End | 2.5060 | Work- HandleCommitFailure | Pega-ProCom 07-10-01 | |
| 1318 | TABTHREAD4 | 1027 | 54 | pyWorkPage | Activity End | 2.4740 | Work- DisplayHarness | Pega-ProcessEngine 07-10-01 | ||||
| 1317 | TABTHREAD4 | 1027 | 54 | Branch Show-Harness | pyWorkPage | 2 | GOOD | Step End | 2.3770 | Work- DisplayHarness | Pega-ProcessEngine 07-10-01 | |
| 1316 | TABTHREAD4 | 1027 | 55 | pyWorkPage | Activity End | 2.3120 | @baseclass Show-Harness | Pega-UIEngine 07-10-15 | ||||
| 1315 | TABTHREAD4 | 1027 | 55 | java | pyWorkPage | 6 | GOOD | Step End | 2.0190 | @baseclass Show-Harness | Pega-UIEngine 07-10-15 | |
| 1314 | TABTHREAD4 | 1027 | 55 | When Rule Evaluation | pyWorkPage | False | When End | 0.0160 | @baseclass recordEvent | Pega-UIEngine 07-10-01 | ||
| 1313 | TABTHREAD4 | 1027 | 55 | When Rule Evaluation | pyWorkPage | When Begin | @baseclass recordEvent | Pega-UIEngine 07-10-01 | ||||
| 1312 | TABTHREAD4 | 1027 | 55 | When Rule Evaluation | pxThread | True | When End | 0.0020 | Code-Pega-Thread IsUserThread | Pega-WB 07-10-01 | ||
| 1311 | TABTHREAD4 | 1027 | 55 | When Rule Evaluation | pxThread | When Begin | Code-Pega-Thread IsUserThread |
Pega-WB 07-10-01
|
| Activity Name | COMMITWITHERRORHANDLING |
| Activity Number | 49 |
| Parameter Page Name | =unnamed= |
| Primary Page Class | XX-FW-ELM-Work-ELMInqCase |
| Primary Page Name | pyWorkPage |
| Step Method | Commit |
| Step Number | 4 |
| Step Status | FAIL |
| Step Status Info |
Database save using an insert failed |
Accenture
TR
If i use the lock option checked, i get this error and if i uncheck the lock option, I get the error saying "lock is not held" but I can see the Owner is my account
I also tried to Call ReleaseLock after using Obj-Open but if I do that, the lock goes to administrator account and again i get lock is not held error.
Obj-Open-By-Handle also acts the same, giving same errors in same conditions
Pegasystems Inc.
US
Hi,
You mentioned that you're specifying pyWorkPage as the page when opening the 2nd case. Is the 1st case on the same thread in which you're opening the 2nd? If it is, try using a different page name for the 2nd case and see if that changes the behavior at all. Since flow processing is likely already using pyWorkPage for the 1st case, opening the 2nd case onto pyWorkPage is likely to cause problems.
Hope this helps!
-Kurt
Accenture
TR
Directly using pyWorkPage and addressing the case instance key was the main problem of reopening the case. Now that we are able to open the old case, we face a new problem: When we reopen the ELM case in a new window, we are unable to continue to UW case as it overwrites the pyWorkPage to its own class.
Is there a way to use two separate pages? remember that we are not trying to open ELM case in review mode. We need to be able to edit it and when we are finished, we need to be able to continue to work on UW.