Pete Wirfs said:
Interesting. Promptsets are always processed before scripts begin executing, so the state of their variables are more stable/dependable at script execution time. But it seems unnecessarily strict of the VARA to not also accept script variables(?)
Yes, prompt set variables do appear to be special. The different behaviors of different types of variables is a frequent source of confusion and frustration. Perhaps someday some kind soul will document a list of all of the different types, how they are set/inherited, and where & when they can be used.
(We aren't using backend variables so I don't have any personal experience with this)
If you can believe it, this was the first time I had ever created a BACKEND VARA for actual use, as opposed to just testing. Seems like s good idea, but only partially implemented. I guess object/script variables are simply not meant to work in this context.
I have already begun to convert this BACKEND VARA to a JOBS + EXEC VARA combo, by generalizing the approach I used to make
a similar conversion of an SQL VARA. With the advent of EXEC VARAs, most of the other dynamic VARA types seem comparatively limited.