Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3626

Do not depend on hard coded variable name "processInstance"

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: jBPM 5.2
    • Fix Version/s: jBPM 5.4.0.Beta1
    • Component/s: None
    • Labels:
      None
    • Environment:

      JBoss 7.1.1

      Description

      If there is a conditional intermediate catch event in a process definition like this:

      processInstance: WorkflowProcessInstance()
      objectId: Long() from processInstance.getVariable("workflowObjectId")
      o: MyObject(id == objectId, name == "My name")

      and it is triggered by updating a fact (MyObject) in the knowledge base it might happen that more than just the one process proceed if the process instance variable isn't named "processInstance". There seems to be some hard coded magic about the variable name "processInstance".

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                swiderski.maciej Maciej Swiderski
                Reporter:
                tdtappe Heiko Tappe
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: