Uploaded image for project: 'Nuxeo Studio'
  1. Nuxeo Studio
  2. NXS-3644

Remove contributions to deprecated JbpmService for recent target platforms

    XMLWordPrintable

    Details

    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      For target platforms 6.0 and higher, Studio document types will not hold jbpm workflow related-configurations anymore. To add it back, custom XML extensions can be contributed, example:

      <extension target="org.nuxeo.ecm.platform.jbpm.core.JbpmService" point="typeFilter">
      <type name="mydoc">
      <processDefinition>review_parallel</processDefinition>
      <processDefinition>review_approbation</processDefinition>
      </type>
      </extension>

      Show
      For target platforms 6.0 and higher, Studio document types will not hold jbpm workflow related-configurations anymore. To add it back, custom XML extensions can be contributed, example: <extension target="org.nuxeo.ecm.platform.jbpm.core.JbpmService" point="typeFilter"> <type name="mydoc"> <processDefinition>review_parallel</processDefinition> <processDefinition>review_approbation</processDefinition> </type> </extension>
    • Team:
      AT
    • Sprint:
      nxAT Sprint 8.10.2

      Description

      Changes for NXP-20911 reveal that Studio is still adding contributions to the JbpmService even if it's not there.

      This contribution (generated automatically on document types by Studio) should be removed for recent target platform versions (see NXP-12448: jbpm deprecated since 5.8).

      Functional implication is that default parallel and serial workflows will not be available on Studio-defined document types for target platform 6.0 and above, even if the jbpm compatibility package is installed, but these contributions can be added back (see example in upgrade notes).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: