I would find it useful to have a general reflection API like one has in .NET / Java. In those environments, the use cases are broad because it is read (get) / write (invoke method) oriented. All of the logging use cases above would be solved. Off the cuff I could think of activities like GetCurrentActivityClass - which would have data for current activity name, id, …, GetCurrentWorkflowClass - return the first activity above in the graph that is a workflow item …
Mircea - it looks like much/all of the information is there internally, just a matter of making it reliably available.
Going through the thread, looks like we still don’t have a way to retrieve the xaml WorkflowName. Am i correct?
I am designing a custom activity and i don’t want studio user to specify the name of the workflow through properties. Instead i would like to get the name of the workflow that has that custom activity and report on it.
Would be awesome to get workflow name but I think also an identifier for activity would be useful. All in all, similar to a bread-crumb trail of where something went wrong all the way from Main, down to the activity level. I think combining this idea with something like this (Activity Uid in case of application exception) would be great