What Activiti's state when process arrive Tasks, Gateway, Boundaries?

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

nhhao1996

I'm researching about Activiti. I've read User Guide and known that the process only stop when it arrived User Task, Timer Boundary. Moreover, I read the book Activiti in Action, it say the Activiti Engine is a state machine. So I want to know that when process arrive tasks, gateway, boundaries, what's it state? Does it pause or stop or something?

pault

Not an expert view, but based on my expereince of V5 and V6 at its simplest I'd describe it as follows.

Activiti Process Engines are only active when called via the API using the services they provide, e.g. to start a process instance, complete a task etc. At that point they perform whatever logic is required, call service tasks, make state transitions etc. They then persist the process state in the database, current activity, process variables etc. and are then inactive until the next API call.

Hope that helps.