But....here's the bad thing, GLPI_DATA is lost when you do the following:
We use many tasks with 3 steps:
Step 1. form
Step 2. We generate PDF with the form data from step 1. But this step is not shown to the user. We jump to step 3. We do it with a trigger in the "after output document" section, with this code.
$result = executeQuery("SELECT STEP_UID_OBJ FROM STEP WHERE TAS_UID='".@@task. "' and STEP_POSITION = 3");
@@stepUID_OBJ= $result[1]["STEP_UID_OBJ"];
Step 3. We show the PDF file to the user so they can sign it digitally.
If we jump to step 3 from step 2, GLPI_DATA is lost.
Why do we skip to step 3?
Because we believe that it is an auxiliary step that does not give the user any special information. At least, in our process.
I don't know if this can be controlled in the processmaker plugin or server. Could it be controlled so that it does not lose GLPI_DATA?
Hello @tomolimo:
I have good news and bad news.
The good news is: Version 5.0.2, works correctly.
But....here's the bad thing, GLPI_DATA is lost when you do the following:
We use many tasks with 3 steps:
Step 1. form Step 2. We generate PDF with the form data from step 1. But this step is not shown to the user. We jump to step 3. We do it with a trigger in the "after output document" section, with this code.
$result = executeQuery("SELECT STEP_UID_OBJ FROM STEP WHERE TAS_UID='".@@task. "' and STEP_POSITION = 3"); @@stepUID_OBJ= $result[1]["STEP_UID_OBJ"];
PMFRedirectToStep(@https://github.com/Application, @%INDEX, 'DYNAFORM', @@stepUIDObj);
Step 3. We show the PDF file to the user so they can sign it digitally.
If we jump to step 3 from step 2, GLPI_DATA is lost. Why do we skip to step 3? Because we believe that it is an auxiliary step that does not give the user any special information. At least, in our process.
I don't know if this can be controlled in the processmaker plugin or server. Could it be controlled so that it does not lose GLPI_DATA?
As a solution, I can always not do the jump.
Thank you. Jorge