Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12594

Introduce the Framework Agnostic Plugin Interface to Tasklist

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.15.0-alpha4, 7.15.0
    • None
    • None
    • None

      We currently have different Plugin Systems in our Webapps, which can cause confusion for the users. It is intuitive that 2 apps in the same UI use different user-facing technologies to extend them. This can lead to frustration when reusing or developing new plugins when we assume that it is the same for all of the camunda webapps.

      We should introduce the framework-agnostic Framework from Cockpit to the other Webapps. We can do this without migrating to react by replacing the existing Plugin System with the new one. This will only change the user-facing behavior, such as config.js structure and plugins.

      CAUTON: I know from experience that some (many?) Tasklist plugins use the global event bus to listen to changes and change state in other tasklist components. This would not work with the new Plugin system, where all plugins are isolated from each other.

      AT

      • I can use the new "cockpit" plugin system in Tasklist
      • I can use legacy Plugins with the same syntax as CAM-12978

        This is the controller panel for Smart Panels app

              hariharan.parasuraman Hariharan Parasuraman
              martin.stamm Martin Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: