Parallel case - php error

[rohit-ambre-uno]

Hi,
While running parallel case, we encounter php fatal error for member function calling on null objects. Take a look at the error below

Fatal error: Call to a member function getStepMode() on null in /opt/processmaker/workflow/engine/methods/cases/cases_Step.php on line 352

Above error may not occur at first time, try refreshing the page few times

Fatal error: Call to a member function getTasDerivationScreenTpl() on null in /opt/processmaker/workflow/engine/methods/cases/cases_Step.php on line 1102

this is the parallel case process i am using in glpi

When i tried running it solely in processmaker-communtity release 3.2.1 it ran successfully.

[tomolimo]

Hello @rohit-ambre-uno
Which version of PM server are you using with GLPI PM plugin?
Thank you,
regards,
Tomolimo

[rohit-ambre-uno]

I am using processmaker community release 3.2.1 with processmaker plugin 3.2.8 and GLPI 9.2.4.
I tried above process with your version of processmaker server but it was throwing errors mentioned in #8

[tomolimo]

Hello @rohit-ambre-uno ,

You have to understand that the only version of PM server that is compatible with the current version of the PM plugin is the one I released here: https://github.com/tomolimo/processmaker-server/releases/latest. In which I made as little adaptation as possible to be compatible to GLPI PM plugin. So I cannot guarantie

And moreover, you have to understand that I wish to help you but for that I need help from your side :)

So to help me solving the issues, I generally need detailed steps in order to reproduce the issue along with screen copies. Otherwise, I will not be able to help you.

I close this issue as it is out of scope of current plugin version, please use tomolimo/processmaker-server#8 to continue on the topic.

Thank you,
Regards,
Tomolimo

[rohit-ambre-uno]

Hi,
I used this parallel process in your version processmaker-server.
It is throwing errors in processmaker server

Can you please try and confirm about this issue.

[tomolimo]

Hello @rohit-ambre-uno,
The error message is coming from a problem of configuration.
The URL rewrite rule of the web server is not correct.
Could you please check that it matches the one given in the wiki https://github.com/tomolimo/processmaker-server/wiki/Inbound-rewrite-rules
Thank you
Regards
Tomolimo

[rohit-ambre-uno]

Hi @tomolimo ,
URL rewrite rule did solve the above mentioned error.
But now it is giving following error in processmaker-server in debug mode

Non-static method G::array_merges() should not be called statically, assuming $this from incompatible context (line 1102):
Non-static method G::getSystemConstants() should not be called statically, assuming $this from incompatible context (line 1102):

same error as reported in #8

Steps to reproduce:

1. Import this parallel process in processmaker-server
2. enable debug mode on process and start a case.

[tomolimo]

Hello @rohit-ambre-uno

As mentioned in the readme of the process here https://sourceforge.net/p/pmcommunity/code/ci/master/tree/routing/loopBackFromParallelTasks/

this process has been written and tested in the 3.2.1 PM release, and such it cannot be imported into the 3.0.1.8 PM release, without the prior idea that it may be incompatible with it.

And I presume it is not compatible 😞

So what I can do to help you is to listen to your needs, and to help you creating a process in the 3.0.1.8 release. Do you agree?

Thank you
regards,
Tomolimo

[rohit-ambre-uno]

Yes, totally.
This parallel process is kinda important for me.
my colleague posted on processmaker forum for process here's a link for requirements.

Any plans on upgrading processmaker-server version?

[tomolimo]

Any plans on upgrading processmaker-server version?

Yes but not before autumn

For the process, I'm going to search for a solution for it and I'll keep you updated

[rohit-ambre-uno]

Ohk.
I will also search for it.
Thank you

[tomolimo]

Hello @rohit-ambre-uno

I can confirm that this process will not work in the 3.0.1.8, there are several issues:

1. the static issues: I made a fix for them, but anyway , the process doesn't behave like it does in the 3.2.1

2. when the process goes back to the first task 'Request resource' (after a rejection from one of the manager) then PM server creates clones of the first task assigned to the @@firstuser (this issue is called multiple-token creation).

3. Moreover, even if these issues were fixed, there is another issue which makes this process not compatible with the current way the GLPI PM plugin is working. The GLPI PM plugin is based on a match of the PM tasks and GLPI tasks. At each end of a task in GLPI, the plugin is calling the "derivate" function (like in the trigger), and is closing the current task. But in this process we may have several tasks that must be closed at the same time: this will not be managed by the plugin, and such, the GLPI tasks will stay open....
   For that, I'll need to review this mechanism, and that is not planed at all 😞

I'll keep you informed if I can find another solution.

Thank you
Regards,
Tomolimo

[tomolimo]

Hello again @rohit-ambre-uno

To be clear regarding the GLPI / PM task match: at any time, GLPI must the initiator of a case derivation, not PM server. If this happens, then we are going to have tasks that are not in synch with PM.

To answer your problem, I've two solutions:

1. a serial (not parallel) process like this (it does transform a little bit the problem, and this can be not completely satisfactory for you):
   
2. the idea here is to keep the defined process, but to not use the trigger (= to not derivate the case into the case itself). And to use a special feature that I developed last year which is not really documented, but fully used by us (internally), see: https://github.com/tomolimo/processmaker/wiki/Interaction-of-cases-between-tickets. If you agree I'll provide you with the new version of the process, and several explanations in order to make it running.

Thank you
Regards,
Tomolimo