If I need to use the Invoke Workflow File activity (UiPath.Core.Activities.InvokeWorkflowFile), I can drag and drop the Xaml file and it will be named ----.xaml - Invoke Workflow File
Please see the image below.
What is the best practise for this activity (Namening Conversation)?
Hi @chethan.b
Check out this thread
You can also use Annotation and give the details about the workflow that you are invoking
Regards
Gokul
Hi @chethan.b
We can change the names for understanding purpose .
So,Depending on the flow of the sequence ,you can give the name to it.
you can use fn+f2 keyboard shortcut or right click the activity and give the rename of the flow.
Hope it helps!!
In most cases, that name is descriptive enough. If not, perhaps the workflow you are invoking is not named in a descriptive way? You might want to add some extra details, if for instance input arguments affect the way the invoked workflow behaves.
My question is whether we should keep .xaml as it is or remove it.
You can remove .xaml from that activity
In this case, you might want to add details about which folder you are creating. The reason for this is that in case of an exception, the activity name would also contain details about which invoke it was about.
If you query is about Activity Name then, yes you can remove the .xaml from the activity name where as in workflow file name field you should not remove the .xaml.
Regards
Hi @chethan.b
It depens upon you. if you need you can keep it or remove it.
Basically the Naming conversion and Adding Annotation is to understand your workflow and code standard
If I keep, I want to keep that one in my process. Right now, .xaml is not interfering with best practices.
Hi @chethan.b
Why do you want to remove the .XAML from the header? Do you have any reason?
In my point of u I will not remove any from the Invoke workflow activity. It all depens upon the user
You can add Annotation to expain the workflow.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
