Advanced Workflow versioning

[remis]

I faced one challange. Maybe somebody can enlighten me on this.

JBPM supports versioning. This is the main reason I like and value jBPM. Main purpose of process definition versioning is to be able to modify, extend and evolve of current processes. As example, after process definition been updated, jbpm engine create new version of process definition, that lets old running processees to be completed by old process definition and newly started processes will be based on the latest version. This is clear and easy. Problem comes with custom alfresco ui, jsp pages, managed beans and other configuration files.

How can I have all these alfresco specific things, jsp, managed bean classes, configuration and graphic files available for all previous versions of advanced workflow (jbpm process definition)?

What strategy could be used to solve this problem?

Thanks in advance.
Remis

[birgir]

Not sure if I understand your problem or what you are trying to achieve.

How can I have all these alfresco specific things, jsp, managed bean classes, configuration and graphic files available for all previous versions of advanced workflow (jbpm process definition)?‍

When you deploy a workflow you are only submitting your statemachine and any associtated logic. You dont deploy a complete system with jsp's,configuration files and the whole lot (which I think you are referring to). The process definition simply defines your rules of how you move the workflow tasks around. You can aslo include versioning of your associated programming logic. See http://www.jboss.com/products/jbpm/docs/jpdl.

Hope this is of any help.

[remis]

Yes I know that I'm aware of it, this is jbpm side and everything is fine here.

Here is a scenario where problem should become very clear. I have a step in my workflow which asks to select space, where file have to be moved or user to whom task should be assigned. In order to do that I have to have alfresco's dialog or workflow configuration file. After some time we thought to improve, update process definition which has changes in the UI.  JBPM definition updated and deployed and here is no problem. The real question is, what and how should i do to keep different alfresco config files in sync with new different process versions. There is no reference in jbpm process definition version from alfresco xml config file, neither I have a choice to have different versions of alfresco configuration files. There is too much questions and options that I can rise, but that is the point to keep them rising if even small questions is not answered.

There is another even more interesting question which I would like to rise. JBPM updates on runtime is just fine, it works, they do have everything needed to keep it working 24x7, but alfresco is not here yet I'm permanently referenced to restart. Could I expect to have that improved or even fixed.

Remis