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

Do not depend on hard coded variable name "processInstance"

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Minor
    • jBPM 5.4.0.Beta1
    • jBPM 5.2
    • None
    • None

    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".

      Attachments

        Activity

          People

            swiderski.maciej Maciej Swiderski (Inactive)
            tdtappe_jira Heiko Tappe (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: