Access to variables - When - Where - What

norgan — Fri, 16 Oct 2009 17:51:35 GMT

Good evening everybody, I am a bit at a loss working with the workflow variables: The questions is rather simple - Which variable is accessible where - and how. I learned there are * task-related variables : The variables from the task form ?* process-related variables: The variables from the workfl

Re: Access to variables - When - Where - What

jayjayecl — Mon, 19 Oct 2009 07:47:12 GMT

I'm surprised that you could do that.
In 3.1, You cannot declare several variables in a script with the "write" access.

Re: Access to variables - When - Where - What

norgan — Mon, 19 Oct 2009 08:21:16 GMT

It says that in the Alfrescolog, when I use AlfrescoJavascript, with jBPL Beanshell, it seems to be ok.

Norgan

Re: Access to variables - When - Where - What

norgan — Fri, 23 Oct 2009 21:26:50 GMT

Hi,
I had some time to look into this again and I tried following code with following strange result. Is anybody using the beanshell and javascript to work with task & process variables at all - or shlud I just move to java actions ?

Two times the same debug lines, trying to find out what values are stored or accessibale at all. The output is completely different, however, depending on event task-end and node-leave. Can anyone explain this to me ?

<start-state name="Auftrag erfassen">
      <task name="chkwf:enterEAdata" >
          <event type="task-end">
              <script>
                  System.out.println("========================================================");
                  System.out.println("=============== task-end ===================");
                  System.out.println("========================================================");
                  if (bpm_workflowPriority != void) {
                     chkwf_EApriority = bpm_workflowPriority;
                     System.out.println("bpm_workflowPriority: " + bpm_workflowPriority);
                  }
                  if (taskInstance.description != void) {
                     bpm_description = taskInstance.description ;
                     System.out.println("taskInstance.description : " + taskInstance.description );
                  }
                  if (bpm_description != void) {
                     chkwf_EAdescription = bpm_description;
                     System.out.println("bpm_description: " + bpm_description);
                  }
                  if (bpm_workflowDuedate != void) {
                     chkwf_Deadline = bpm_workflowDueDate;
                     System.out.println("bpm_workflowDuedate: " + bpm_workflowDuedate);
                  }              </script>
           </event>
      </task>
      <event type="node-leave">
         <script>
                  System.out.println("========================================================");
                  System.out.println("=============== node-leave ===================");
                  System.out.println("========================================================");
                  if (bpm_workflowPriority != void) {
                     chkwf_EApriority = bpm_workflowPriority;
                     bpm_priority = bpm_workflowPriority;
                     System.out.println("bpm_workflowPriority: " + bpm_workflowPriority);
                  }
                  if (bpm_description != void) {
                     chkwf_EAdescription = bpm_description;
                     System.out.println("bpm_description: " + bpm_description);
                  }
                  if (bpm_workflowDuedate != void) {
                     chkwf_Deadline = bpm_workflowDueDate;
                     System.out.println("bpm_workflowDuedate: " + bpm_workflowDuedate);
                  }
         </script></event>
      <transition to="gogogo" name="toGoGoGo"></transition>
   </start-state>

Following 9 lines from my log:

========================================================
=============== task-end ===================
========================================================
taskInstance.description : Anfrage mit EA-Nr und EA-Namen erfassen
bpm_description: Anfrage mit EA-Nr und EA-Namen erfassen
========================================================
===============node-leave ===================
========================================================
bpm_workflowPriority: 1

Re: Access to variables - When - Where - What

jayjayecl — Mon, 26 Oct 2009 08:23:29 GMT

Hi Norgan, here is one of the mainproblems I had with scripting.
I don't know if it was me or scripting API in workflows, but many times, I could notice that accessing and/or logging variables in scripting API could "alter" them.

topic Re: Access to variables - When - Where - What in Alfresco Archive

Access to variables - When - Where - What

Re: Access to variables - When - Where - What

Re: Access to variables - When - Where - What

Re: Access to variables - When - Where - What

Re: Access to variables - When - Where - What