Wishing for "PSET_SCRIPT_VAR"

[Reed Byers]

Hi there!  Oregon State University is starting our migration from Application Manager to AWA, and we continue to be full of questions.

Today's problem:
We have a script variable which is holding the NAME of the variable that we then want to PSET.

The possible solutions we've thought of are:

1) Use the SET_SCRIPT_VAR command -- but that will merely SET it.  We want to PSET it.

2) Use RESOLVE_VAR to create a PSET command string... but we can't find a command to actually execute the string.

Anyone have any ideas?

------------------------------
Reed Byers
Programmer/Analyst
Oregon State University
------------------------------

[Pete Wirfs]

Check out GENERATE_SCRIPT_VARS too.

------------------------------
Pete
------------------------------

[Reed Byers]

Pete:

We thought of that, but it's still only SETting, not PSETting...



------------------------------
Reed Byers
Programmer/Analyst
Oregon State University
------------------------------

[Pete Wirfs]

I'm not an expert in the use of PSET; we never use it.  When we need to pass a value from one task to another, we define a variable in the workflow and let the tasks reference it from there.

------------------------------
Pete
------------------------------

[Joel Wiesmann]

You can use a VARA object that carries all the data during the workflow execution. Setting / getting data can be done using GET_VAR / PUT_VAR. If the workflow must be executed in parallel, you can make use of the scope feature of the VARA object.

------------------------------
Swisscom Automation Engineer & PE Membership Creator

Entfessle mehr Automic Wissen mehr Automic Tools
https://membership.philippelmer.com/
------------------------------

[Gary Chismar]

A few things....
1) Is the attribute "generate at runtime" selected on the attributes tab?  If not then the variable may be "set" before it actually gets to the section where it is being set.
2) If part of a workflow are all objects marked "generate at runtime" on the attributes page?  If not, Automic support recommends that it is selected.  Otherwise you can have issues..
3) Automic recommends (at least they did to us) that syntactically we should set the variables and then, PUBLISH them.  Example: PUBLISH &Variable,,"TOP"
4) As mentioned by someone else in this thread, if you defined the variables at the beginning of a workflow (variables and prompt tab) then they should be available downstream.

Generally, we have not had any issues with :PSET in scripts.  Only when the generate at runtime was not checked.  Then we would get an error when we kicked it off.




------------------------------
Cheers,

Gary Chismar
Manager, Automic, PeopleSoft HCM/FI
Florida State University
Florida
------------------------------

[Tim Quakulinsky]

Hi,
with regard to point 3: We got performance issues regarding the usage of :PSET in version 10.0 because :PSET sets the variable in all (sub) tasks of a workflow - and especially in bigger workflows this was a real problem. For this reason I can only recommend everyone to use :PUBLISH or write the variables into the Variables & Prompts tab. If you do both, however, the clarity suffers again...
with regard to point 4: You can configure in the Variables Page of a sub task, that the object does not inherit any variables or only defined variables from its parent object.
Kind regars,
Tim

------------------------------
Automation Evangelist
Fiducia & GAD IT AG
---
Mitglied des deutschsprachigen Automic-Anwendervereins FOKUS e.V.
Member of the German speaking Automic user association FOKUS e.V.
------------------------------