6 Replies Latest reply on Mar 22, 2007 9:20 AM by Arjan van Bentem

    processdefinition and sub-process - autoupdate

    darren hartford Expert

      Hi all,
      I'm using the jbpm-console, so this may only be related to that webapp.

      When I deploy a 'parent' processDefinition with a sub-process, it works fine. When I update the sub-process, it looks like the 'parent' process only continues to use the last-known-good sub-process from when it was last deployed.

      This is fine by default, but would be nice to have an attribute to 'alwaysUseMostRecent' version of the sub-process, or on the flip side 'LastGoodSubProcessVersion' to true/false to keep the above described behaviour. I understand there exists a version attribute, but would be easier to have the jbpm understand the intent instead of always manually changing the version number.