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

# $ difference when dynamically resolving expresion of a calledElement of a callActivity

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.1.0, 7.1.0-alpha2
    • None
    • engine

      When dynamically resolving the name of a subprocess it turns out that Version 1 doesn't work whereas Version 2 works as expected:

      1. <callActivity id="callProcess" name="Execute some process" calledElement="#

      {processDefinition}" />
      2. <callActivity id="callProcess" name="Execute some process" calledElement="${processDefinition}" />

      In case of 1 the expression I get the error message:

      no processes deployed with key '#{processDefinition}

      '
      Line | Method
      69 | findDeployedLatestProcessDefinitionByKey in org.camunda.bpm.engine.impl.persistence.deploy.DeploymentCache

        This is the controller panel for Smart Panels app

            [CAM-1490] # $ difference when dynamically resolving expresion of a calledElement of a callActivity

            Also check out similar experiences with Activiti: http://stackoverflow.com/questions/19711105/activiti-dynamic-called-element

            Martin Schimak added a comment - Also check out similar experiences with Activiti: http://stackoverflow.com/questions/19711105/activiti-dynamic-called-element

            Hi Martin,

            thanks for reporting, we will look into this in contect of the 7.1 release.

            Cheers
            Robert

            Robert Gimbel added a comment - Hi Martin, thanks for reporting, we will look into this in contect of the 7.1 release. Cheers Robert

              smirnov Roman Smirnov
              martin@schimak.at Martin Schimak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: