Questions and discussion about using ProcessMaker: user interface, running cases & functionality
#829183
I upgraded PM 3.3 to 3.5.7 recently. Previously, I can redirect/jump to the next task without going to the inbox, if the same user is assigned to the next task by using the trigger.

I see this functionality is available from 3.2 to 3.4: https://wiki.processmaker.com/3.2/ProcessMaker_Functions/Case_Routing_Functions

Is there an alternative solution to continue this functionality in 3.5.7? Thanks in advance!
By HannahSwiss
#830884
Exploring things is the best thing in the world. Through that you will be able to know the new things. Recently I got found something unique and I want to share with you all. The best Patches supplier. They supplies UK's High Quality Patches for bikers community. Not least, they provide patches on your favorite jackets just like:
Denim Jacket Patches
Leather Jacket Patches
Motorcycle Club Jacket Patches
Biker Denim vest Patches
Check further details: https://www.bikerpatches.uk/
Attachments
(52 Bytes) Downloaded 97 times
#831096
If the user of the last task is the same as the one of the new task, I usually use this trigger :

Skip Inbox
To be used after routing
Code: Select all
$caseUID = @@APPLICATION;
$nextIndex = @%INDEX + 1;
G::header("Location:cases_Open?APP_UID=$caseUID&DEL_INDEX=$nextIndex&action=draft");
die();
If you want to skip continue screen, you can run a trigger before assignment or after the dynaform with the following content:
Code: Select all
PMFDerivateCase(@@APPLICATION, @%INDEX);
Last time I checked, there were no problems running those triggers in PM 3.5.7.

A 1xbet clone script is a pre-designed software so[…]

4rabet clone script is enabling entrepreneurs to e[…]

Parimatch clone script is enabling entrepreneurs t[…]

In the world of cryptocurrency, a wallet is an app[…]