Create the global variable Concept

By Diogo Cordeiro on 21 Oct 2011
Sometimes there is the need to share the same variable across eSpaces.

EnterpriseManager had the global variables concept, but one would have to hardcode the name of the variable everywhere to get its value.

I've seen Static Entities used for this... (267 SUs for a producer eSpace with one static entity with one Id field and a name field, and a consumer with a user action)

I've see public actions with only one assign and one output text value for this...(24 SUs for both a producer and consumer eSpaces, where the consumer consumes the id in a user action)

I've also even seen Site properties used for this, with public actions to expose them...(but this one i would not advocate because site properties aren't the same as static variables)

Now, a good thing would really be a system static global variable concept at the action (dll) level or something like it.

This way you would have it centralized, wouldn't need to reach the DB for these, and wouldn't have to build an action to expose hardcoded values...and also, i believe we could reach a reasonable value with those SUs, less costy than static entities, but a little more than public actions exposing justify its use.
André Ramos22 Oct 2011
I like it. I think site properties should be referenceable.
J.25 Oct 2011
I don't like the idea.

You can kill multiple espaces in 1 go, because some muppet changed a global variable.
It's too much of an exposure imho.

Diogo Cordeiro25 Oct 2011
That you can do today also, while using anything that's public.
Kilian Hekhuis2 Nov 2011
Agreed. Similary, you could say "you can kill functionality spread across multiple eSpaces because some muppet forgot to change one of the 10 local variables".