Uploaded image for project: 'Magnolia Workflow Module'
  1. Magnolia Workflow Module
  2. MGNLWORKFLOW-94

Prefer jcr defined workflow definitions over the one in the files

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 5.0
    • 5.0
    • jBPM
    • None

      Currently, upon installation, the jbpm definitions will not go into jcr but stay in the file system. When loading workflows values from jcr are considered but will always be replaced by the ones from the filesystem. Both should be changed - much like it's implemented in 4.5. Like that users:

      • would be able to use e.g. the jpbm Eclipse plugin to modify their flow files but still have it bootstrapped into jcr
      • directly adapt flows in jcr without having to fiddle around with the file system

        Acceptance criteria

              dlipp Daniel Lipp
              dlipp Daniel Lipp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: