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.

How to write an Activiti Cycle plugin

daramcguinness

Hi,

I realize that Cycle is still beta, but I was wondering is there any "beta" documentation (Wiki, blog … ) that gives pointers on how to write a Cycle plugin (annotations, Plugin APIs ecc.). I've had a look around and I didn't find anything - apologies in advance if it's obvious and I missed it!

thanks,
Dara

Find more posts tagged with

Comments

bernd_ruecker

Hi Dara.

Actually we don't have dedicated Docs for the Plug-In Development yet. Best is to use the JavaDoc or have a look in the source code. I think the SVN Connector is a good example, because it is pretty isolated: https://svn.camunda.com/fox/trunk/cycle-plugins/fox-cycle-plugin-svn/ (or what kind of Plugin do you want to write?).

But please note, that the Plug-In API is not yet stable, so maybe it changes a bit in future (that's why we are "beta").

What Plug-In do you plan?

Cheers
Bernd

daramcguinness

Hi Bernd,

thanks for the reply and the pointers. We like the business concept behind Cycle (different stakeholders using different artifacts, linking of artifacts, the “mini-social” network that automatically gets built around initiatives etc.). And, whereas BPM is an obvious area to use this (the model is an “obvious” part of a project that goes up and down between the business, development, operations etc.) Cycle has (we believe) potential for most types of software project as it gives nonintrusive loosely coupled “networking” of ideas from inception through to deployment.

That said, we want to have a closer look at the plugin API to find out how to extend it and get some know-how so that if we propose it to clients we can respond to the inevitable requests to do something specific that isn’t supported with the “out of the box” version (maybe they’ll want to connect to JIRA to pull in an Issue, or to a custom repository to pull out a document, or to a ticket management system such as Remedy etc. etc.). So we want to “play” with it to see how to extend it.

Another question (if I may) before I dig into the API docs and the source - Is it correct to say that Cycle has two main types of plugin – Connectors (to get access to artifacts and show them in the Artifact Browser) and plugins to “manipulate” artifacts (different views, actions on a single artifact available in the Work Area)? Perhaps there are other “classifications” of Plugins (for example maybe you can plug the security model to get access to user details from an existing LDAP etc.)?

Thanks,
Dara

bernd_ruecker

Hi Dara.

You are right about the types of Plug-Ins, that's what we concentrated on first: Connectors, Views and Actions. And if you watch this screencast (http://www.bpm-guide.de/2011/03/22/the-bpm-roundtrip-with-activiti-cycle/) you see the process solution concept. The process behind that should be pluggable as well (but isn't yet).

For JIRA we already have a connector by the way, it is just not open sources but we provide a commercial license for it. Send me a mail (bernd.ruecker@camunda.com) if that is interesting for you. And let me know if you want to write own Plug-Ins, since i am in contact with some parties thinking about connectors, so we can maybe coordinate that a bit to avoid duplicate work 🙂

Cheers
Bernd

P.S: Good to get positive feedback about the core idea of Cycle 🙂

daramcguinness

Bernd,

Thanks for the information - I will definitely keep you in the loop for any plugin development initiatives!

Dara