nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Activiti as an engine for 'conversational' web workflows?

excaliber

I'd like to use Activiti as part of an in-house platform for diagnostic workflows. Our preferred approach:

- Activiti included as a jar or jars within a java web application deployed on tomcat 6
- XML ideally deployed separately, outside war files
- ajax/rest-driven interactions on a single view/page (per workflow)
- after initial page load, ajax-based DOM updates handled by a Spring rest controller.

Workflows would consist mostly of automated tasks modelled as a series of real-time ajax interactions and would probably require only a small subset of BPMN. Currently I use my own simple state machine but I imagine Activiti might allow development to proceed more quickly and scale better to new and larger workflows.

I'm reviewing the demo and docs. Thoughts are welcome.

Find more posts tagged with

Comments

ronald_van_kuij

modelled as a series of real-time ajax interactions

Can you elaborate a little…

jbarrez

I don't know if it is a good idea, because Activiti is really tailored towards database usage.
You could run it in an in-memory database, but that would introduce stange things I guess (never tried), ie is the database shared, what if there are concurrency issues … etc.