Hospital São João Client Info
| Version | Date | Notes | By |
|---|---|---|---|
| 0.1 | 2025-07-15 | Initial commit | Bruno Borges |
How to recover a Processes Engine task
In IMS, go to Processes Engine » Task history, search for the Process code indicated by the client and get the ID from the checkbox.
Note: the search may not always work with the simple filter and you might have to travel manually through the pages (use 100 records).
In DBeaver, open the following tables:
- t20_token_process - this contains the process case
- t20_token_process_object - this contains the process case's tasks
In t20_token_process, you might have to change the status_id, in this case we'll change it from 6 (canceled) to 1 (executing):
Copy the ID value and go to t20_token_process_object, filter for token_process_id and check the associated tasks.
In this case, you can see that the last task has the status_id 6, which means it's cancelled. You can check the status table to know all the different existing statuses:
All we have to do now is change both status_id in both tables to 1 (executing) and the task will now be presented in Processes engine » My tasks to be executed.
Now that the task is in execution, it's editable.
In cases where the client wants to move the process back to a certain step when it's already concluded, you'll have to change the status_id of all the following tasks to 1 (executing) as well.
First, you can check the history of the process case in the Processes Engine » Task History, pay attention to the blue numbers for each step, you can use them to compare with the DBeaver table listing of all the t20_token_process_objects. By using this, you can know precisely from which step you need to put in execution.
In this case, if we wanted to revert the process to step 8 "Parecer de internato médico", we'd need to change the status_id of that step 1 (executing) and delete the following steps.
You may also have to delete associated records in t20_token_process_connectors.