👉 Find all the Hindi UiPath Video Here kzbin.info/aero/PLEYSwx3duQ2BSbJTsWADFggPgurO0kdhM
@royroshan8212 жыл бұрын
Hello Mukesh...love the way of your teaching. please keep adding more videos.
@MukeshKala2 жыл бұрын
Thank you, I will
@AnilKumar-mo3pr Жыл бұрын
You are an amazing teacher. Very nicely explained. Thanks, it was very helpful to understand.
@MukeshKala Жыл бұрын
Glad to hear that!
@asifshekh73209 ай бұрын
amazing sir Thank you so much
@MukeshKala9 ай бұрын
Glad you liked it 😃
@sridhare1534 Жыл бұрын
Amazing
@MukeshKala Жыл бұрын
Glad your liked 🤝
@user-wj5xv9yt6n6 ай бұрын
Hi Mukesh, I used 70 Try catch activity in my process xaml which is SAP based automation and to handle each exception I used this multiple try catch and now my process is working fine no issue it captured all exceptions but now my manager said my coding is super bad? I am very disappointed because of his statement
@MukeshKala6 ай бұрын
Yes putting too many try catches is not a good practice …. You should group activities inside a sequence and put a try catch on the sequence or flow chart and then handle them . This would happen if you have properly segregated the automation into modules , then one try catch for one module