Transmission of variables between two jobs.

[Frederic BERGERON]

Hi,

I have the following problem:

In a standard workflow, I have a first job updating a variable in the post-process:

:PUT_VAR VARA.1, "token", "test4"

The second job read this variable in tab process :
:SET &token# = GET_VAR(VARA.1, "token", 1)
:print &token#

At the end of workflow VARA.1 is up to date but the read variable have the value of at the start of the workflow !?
if in the job one, i updating  in process this work but i need to update after.

what the trick for sharing variable ?


Thx

[Frank Muffke]

Hi

Generate@Runtime
https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Executions/Exec_GenerateAtActivationRuntime.htm?Highlight=generate

Standard behavior if you start a Workflow with jobs in it:
Workflow + all include jobs are generated @ workflow start.

=> check the box in every job that follows your job with your post_process actions...

cheers, Wolfgang​

------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------

[Frederic BERGERON]

oh my god... it was so simple...

Thank you very much match !

[Frank Muffke]

welcome :-)

------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------

[JOE MURRAY]

​Still trips me up !!

[Frank Muffke]

?

------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------

[Alain Moisy]

This option should have been remove decades ago. Still not see why it is also the default for all objetcts. Goes against the basic logic of processing.

I guess that for historical reasons of performance it was interesting to load everything in the activity window. Not really necessary anymore regarding DB and system performance .... since beginning of the 2000 ....


Have fun with some options in some objects that works only if object is set without generate@runtime when manually submitted but needs to be generate@runtime when used in a workflow i.e. ....