[jayandrewryan]

After upgrading from 2.5.1 to 3.0 we have had some odd issues. This one has been a bit of a pain the past few days and I'm hoping someone can help me out.

When going to Advanced Search and searching for a case #, if the Current User is [UNASSIGNED] because it is in a task that is set to Self Service, clicking open on the case comes up with the error:

row '' in table USER doesn't exist!

There are also two alerts (javascript popup)
1) cases_Resume
2) cases_Resume_Current_Task

It seems to be getting the USR_UID from the current task and attempting to get data about the user from the USER table before displaying the case information. Unfortunately, as there is no user assigned, that is not possible.

Does anyone have an idea on the best way to handle this?

[jayandrewryan]

I found it:

[‎4/‎6/‎2017 2:04 PM] Ryan, Jay:
i figured out how to fix the
row '' in table USER doesn't exist!
error
In /opt/processmaker/workflow/engine/methods/cases/cases_Resume.php
I need to modify the file to look like this at line 285
[‎4/‎6/‎2017 2:05 PM] Ryan, Jay:

Code: Select all

      $FieldsPar['USR_UID'] = $row['USR_UID'];

        // JAR ADDED to prevent "row '' in table USER doesn't exist!" error

        if ($FieldsPar['USR_UID'] == '') {

                $aUser['USR_FULLNAME'] = "Unassigned";
        } else {

                $aUser = $objUser->loadDetails ($row['USR_UID']);

        }

      $FieldsPar['CURRENT_USER'] = $aUser['USR_FULLNAME']; 

Then cases that are currently unassigned open with no errors

Posting in case someone else needs it.

[amosbatto]

Glad you found the problem.

Here is the corresponding code in PM 3.2 (the next version of PM):

Code: Select all

      $FieldsPar['USR_UID'] = $row['USR_UID'];
      if(isset($row['USR_UID']) && !empty($row['USR_UID'])) {
        $aUser = $objUser->loadDetails ($row['USR_UID']);
        $FieldsPar['CURRENT_USER'] = $aUser['USR_FULLNAME'];
      } 

It looks like the Dev team already fixed this for the next version of PM. Which version of PM are you using?

[jayandrewryan]

We are currently using 3.0. We just upgraded from 2.5.1.