Graphical Representation, Signavio Activity, Activiti Explor

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-admin

The more complex - respectively, long-running - processes are, the more end users (actors) want to be informed about the current process' state. They need detailed information about which activities are to be resolved, which actors will be responsible for progressing a critical process (in order to talk to them in the real world), and they need to estimate when a process might be finished.

In other words: Formalized business processes also need to assist in managing informal aspects. - A graphical process overview - with detail information as onmouseover tooltips - might be indeed helpful.

- The Signavio folks, that are partnering with Activiti by providing Activiti Modeler, already have a solution at their fingertips (well, almost): The Signavio Modeler is a derivate of the Oryx Edtitor, and the latter does provide a specialized API for visualizing a process model:
http://bpt.hpi.uni-potsdam.de/Oryx/MOVISightings

The next question was, would the Signavio folks be willing to engage in that topic? - From an end user's point of view, this feature would be really central and hot.

However, there's already been a milestone in Activiti's roadmap that Activiti hasn't been able to reach, that "BPMN import" feature: It's simply not implemented in the current Activiti / Signavio Modeler release.
Looking at Signavio's ancestor, the Oryx editor, that feature is already implemented, but more than buggy (doesn't work at all, even with simplicistic process models).

I wonder if the Signavio folks should engage more, and contribute back to their roots (Oryx), and to Activiti.

- Another issue, concerning the practice, I'm wondering about, is Activiti Explorer. - That's a really smart application in terms of AJAX integration and cursory user experience.

However, in real applications, in real life, that application would need to be extended and customized by software providers. There'd be requests for features like "who's to be kicked in the ass in order to get some progress to this freaking process", or, "what does my subordinate currently do".

While Activiti Explorer would - surely - need to be customized in real-life applications, there's absolutely no documentation on that. - There's a mixture of JavaScript, an Activiti REST API, and a Java server backend, - however, that domain is not documented, at all.

- In my own small imagination, the modeler and, of course, the process engine are basics (that just need to work, no need for a discussion). They don't need to provide all possible features (as there are so many), but should be consistent with the basic features. (For example, we don't urgently need a "Java Task" as this could be accomplished by implementing ActivityBehavior, as well.)

In contrast, to me, it appears crucial to implement (a) importing plain BPMN files into the Signavio Modeler, and (b) providing documentation and plugin APIs for Activiti modeler.

Thanks

activiti-admin

and (b) providing documentation and plugin APIs for Activiti modeler.

Sorry, typo. - Not Actititi Modeler needs to be documented for that matter, but Activiti Explorer.

That's because almost any software provider that's using Activiti Explorer will want to customize that application.

Thanks