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

execution.setVariable( "VarWithSameNameAsExistingLocalVar" , "GlobalValue" ); => next component throws Exception on ${VarWithSameNameAsExistingLocalVar}

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Won't Do
    • L3 - Default
    • None
    • 7.8.0
    • engine

    Description

      Consider the following scenario :

      I have one serviceTask with a input variable say "MyVariable"

       

      // Inside component's execute() methode

      execution.setVariable("MyVariable","Global variable value");

       

      In next component used ${MyVariable} somewhere 

      At runtime Exception will be thrown regarding "${MyVariable}" because MyVariable is not found there. 

       

      Reason :

      execution.setVariable("MyVariable","Global variable value"); this does't worked as expected.

      I expected that above line will create a global variable in execution.

      But the case might be that it overwritten the existing local variable. And the scope of the Variable remain Local. If there were no local variable with the same name; there would be no problem.

       

      Thanks,
      Pankaj Prabhakar Bhamare,

      Software Developer,

      Mobile : 9561199551

      email : pankajpbhamare@gmail.com

       

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                nikola.koevski Nikola Koevski
                pankajpbhamare Pankaj Prabhakar Bhamare
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce