Reads the StackTrace and returns useful information, including the name of the executing Action, eSpace name, Screen name, Web Service name, whether the action is being executed by reference or in a mobile context, and more.

Examples of use

• Creating logging/auditing data which has Action name or Screen name and previously had those fields hardcoded.
• Execute different logic in the same Action when running inside a Timer (such as setting different timeouts for service requests, doing more resource-intensive tasks, etc).
• Identifying when the Action has been triggered by a Client Action from a mobile application and skipping part of the flow in order to make the response faster.