How to get the current running Xaml file name dynamically.
How to get dynamically physical Xaml file name of currently running
How to get Flowchart or Squence name
How to get the workflow(xaml file) File
Don’t think it can be done.
But one thing you might consider is storing all the .xaml filepaths that you wish to invoke into variables or an array, then you can use that in your Invoke Workflow to call it and you can tell which part of the process you are currently at.
You can also use System.Environment.CurrentDirectory (or Directory.GetCurrentDirectory) and Directory.GetFiles() to gather the .xamls located in the folder. And, if your filenames are named where they are in the order of the process, you can store them into a list and use that list in your Invokes.
Another tip is you can get the filename only by using Path.GetFileName(), but requires a fullpath I think. Or you can also use a .Split like
Thank you for your reply. I will try it.
Could you check with this one? Activity name GetRootActivity
GetParent.1.0.5.nupkg (5.3 KB)
Not sure if this is what you’d need, but tests looked good yesterday.
Based on this and modified a little.
Don’t mind the package/activity name, I was actually trying to do something else and ended up with getting the xaml name… happens
Get File Name of the xaml file which is currently running
How to get current xaml name
For some reason your .nupkg will not load into my Activity Packages to install, even though I placed it in the same folder as the other ones I have installed.
Uncheck filter activities.
Just one small correction - this returns the class name of the root (IIRC correctly), so if you rename the workflow it may not be accurate.
I didn’t not check the package yet will do in sometime, is it the x:Class attribute that you mentioned. I tried to read that value multiple times in the past , but failed.
I had issues with getting to it in the past as well directly from xaml, but in the end managed to by checking attributes with names extended with namespaces. Don’t have access to that one right now, but I’ll try to send you some pointers tomorrow.
The package though uses WorkflowInstance as you can check in the link. I don’t guarantee that it will not collide with something Uipath does internally, as I don’t have visibility over that, but in short tests it worked correctly.
If it will be functionally ok, I’ll clean it up and add to my repo. Still need to setup builds and feed for that one, but never enough time…
Cool, it worked. But I tried renaming Workflow and it still worked for me bringing in correct name.
Now, how do you get Arguments passed when the workflow throws an error? If that part can work, I’ll be happier, since you can’t pass the Workflow name if it errors.
Interesting… I thought it wouldnt. I’ll need to investigate further on that one. But that’s even better
With the arguments it’s tough. There is a trick with double reference, but that is hackish as hell, since arguments not passing is by design.
Or that may be a case for app resources… @vvaidya?
Possible, but we need to refer the values twice (Arguments and App Resources). As far as @ClaytonM 's question is concerned , why not save the Page name using your activity in App Resources at the beginning of of every workflow ( as 1st activity) that way we always have the page name of Last accessed Workflow.
System.Windows.Application.Current.Resources("wfname") = wfName
In the catch Block you can get the workflow name as below
strErrorWf = System.Windows.Application.Current.Resources("wfname").ToString
Set current Directory issue
Running bot details
Hi Andrzej, would you be kind enough to share the source code?
(please do excuse me for shamelessly asking for this … )
This is brilliant I have been looking for it for quite sometime now. I am building a custom activity that needs to retrieve the name of the workflow for some reporting. Do you mind sharing the code?
Hi could one of you please share the code this is exactly what I need?
Which is the best solution to get the Workflow name dynamically.
The “best solution” can be debatable I think.
First, we must define what we mean by “dynamic”.
Essentially, you will have a series of workflows being implemented in your process. A good practice would have these filepaths to these workflows stored in a global variable (or config file). Now, you have the workflow names because they are stored in a variable.
However, do you want the workflow name(s) or do you want the name of the task being performed so you can log this information? So, the workflow name won’t necessarily give you the name of the task being performed if you have multiple tasks in one workflow. But, then again, it might not be good practice to have multiple tasks in one workflow anyway.
So, simply put, you can store the task names for a process in some array or variable which you can reference before you invoke each workflow file that you want to log. For example, you can log that the particular task is starting.
^That is one approach, which I find a little more flexible to be honest
The other approach would be to look in andrzej’s and vvaidya’s posts above as they provide you a way to store the current workflow file being run into a variable. If you take this approach you must surround the workflow’s main sequence with a Try/Catch. Therefore, the Error Handling becomes redundant since any framework used to invoke that workflow would also be handling the errors. —arguments can not be passed when an exception is thrown, so you wouldn’t be able to pass the workflow name without it going through a Try/Catch. This also requires that all reusable workflow components that you might want to return the workflow name from include a Try/Catch, which means any RPA devs would need to know this and a lack of versatility I think anyway.
@baskaran.c Hi, so those are a couple ideas on how to handle workflow or task name(s) storage dynamically in order to provide that info in your logging.
- store a list of tasks in an array that will be performed; store the current task into a variable before each workflow task is invoked so when an exception is thrown on that workflow, you have the current task that was being performed
- use vb.net code to return the .Current.Resources(“wfname”) -as shown earlier in this topic- at the start of each workflow and pass it as argument by using a Try/Catch around that workflow’s main sequence; also pass the exception in the Catch so your framework main can see that an exception occurred.