takes a variable to write the node that the process passes through in the variable?
or mark each node that the process passes through directly in the database, and judge it according to the process id when it arrives at the node.

after thinking about it for a while, I found a solution to meet my own requirements, which is mainly to judge the status of the tasks that have already been performed, such as the examination and approval task. If the examination and approval task is not approved, it will be returned to the application step. So at this time, the examination and approval task has been completed once, but it may be carried out again. The idea I judge for this state is as follows:
first, all the historical activity instances (ACT_HI_ACTINS table) of the process can be obtained according to ProcessInstanceID, then traverse by time, and put the activityID into an array. If an activityId is repeated twice, the one between the two activityId is in this state, and then the part is removed from the array

Code

@Data
@NoArgsConstructor
@AllArgsConstructor
public class TaskInfo {
    private String taskId;      // id

    private String assignee;    // 

    private Date completeTime;  // 
}

because the scenario in the requirement is relatively simple, the use of parallel gateways is not considered, and complex processes may need to be improved