Using variables in xml source of a project area process
In RTC (version 4.0.6), does the project area xml schema support the use of variables?
I mean this: I would really appreciate if the project area-related information (e.g.: PA name, process template, ...) was saved in (predefined and implicit) variables that can be accessed in specific points of the process xml.
Suppose, for instance, that there is a variable such as ${project-area-name}.
I would like to access its value in, say, a precondition or a followup configuration.
Is this possible?
I mean this: I would really appreciate if the project area-related information (e.g.: PA name, process template, ...) was saved in (predefined and implicit) variables that can be accessed in specific points of the process xml.
Suppose, for instance, that there is a variable such as ${project-area-name}.
I would like to access its value in, say, a precondition or a followup configuration.
Is this possible?
Accepted answer
Preconditions and follow up actions have a special configuration capability that allows to specify configuration values. Without special means, they only have access to these configuration parameters. (See the Extensions Workshop for details). I am not aware that you can, in general, store variables in the process XML.
Since the operational behavior is always working within the context of a special project area, they have also access to all that context information via the item they are triggered by.
Since the operational behavior is always working within the context of a special project area, they have also access to all that context information via the item they are triggered by.
Comments
