[Vysakh]

Hi ,
I just upgraded my PM 3.2.1 to PM 3.5.7. But after the upgrade I noticed that sql property of textboxes is not working in some Dynaforms. It was working fine in 3.2.1. Also some cases are getting properly assigned to the next user. The case just disappears but can find the case in participated as it is in your inbox. But it is not in the inbox. In this case we are getting an error in __ERROR__ variable. Please see the error below.

The "Symfony\Component\Debug\Exception\FatalErrorException" class is deprecated since Symfony 4.4, use "Symfony\Component\ErrorHandler\Error\FatalError" instead.

MYSQL Version 5.7
PHP Version 7.3

[Vysakh]

Any update on this?

[JonathanMiller]

I've had cases disappear from the inbox before. They could still be seen in participated just as you've described. I believe in my situations it was caused by an error in some trigger code being executed in the Routing section. Could you be having a similar issue? Have you checked the processmaker logs in shared/sites/workflow/log?

In order to fix my cases I had to manually reassign the case to the previous user by modifying APP_DELEGATION and APP_CACHE_VIEW. Deleting them is easier and safer though...

[Vysakh]

@JonathanMiller Case disappearing issue was solved by changing the triggers location. I changed the triggers location to after dynaform from after routing. But SQL issue still there. But SQL is working fine on a Dynaform and it is not working on the other. Anyone knows the solution ?

[sanglaremgg]

Without more context or details about the issue you're encountering, it's difficult to provide a precise answer.

In general, "SQL not working" could refer to a variety of issues such as syntax errors, incorrect table or column names, or issues with data or connection to the database.

Regarding the "case disappearing" issue, could you please provide additional information on what specifically you mean by "case"? If you're referring to the capitalization of data stored in a database, please note that SQL is case-insensitive for most DBMS (unless specifically defined otherwise) and it may change the case of your data for storage purposes.

It's recommended to provide more information about the error message or specific issue you're facing so we can better assist you.

[JonathanMiller]

In the context of ProcessMaker a Case is an individual document of a ProcessMaker Process. Documents that users are submitting were disappearing. I believe they have this fixed.

Vysakh, can you post some of the SQL statements your using in the control sql properties that aren't working?