Chris,
I don't use Global Task Sequences. It is much easier for me to write them in code and I rarely have task sequences that are exactly the same on different objects. That being said, I would recommend them for people who find it easier to use the GUI interface for creating task sequences. If you have a task sequence that is found on many different objects in your model and prefer code like myself, then I would put the task sequence in a user command before I would use the GUI to create a global task sequence. I don't want to suggest that they are bad, just that they are not for me.
As for global variables the main difference between them and a standard variable is that a standard variable goes out of scope when the trigger it was defined in ends. This means that the standard variable is gone from memory and can no longer be referenced by another object and the value that was stored in it is gone and can not be recovered. Global variables don't ever go out of scope and therefore can be referenced by any object and the value stored in the variable will remain there for all to see. So, the only reason to use a global variable is if you want to have a variable that will remain in scope for the duration of the model run and/or be accessible for more than one object/trigger.
Hope this helps,
Brandon
__________________
 thats not normal.
|
