I was in the working group of my firm, and we were onboarding UiPath Process Mining as a product. The use cases for the solution were sometimes driven by the management and sometimes by us. Three to four systems were involved in a team's daily tasks. The performance of these systems had been decreasing down the line. They were not performing as expected, causing delays in client deliverables.
We analyzed two of the applications in which we found major issues. We did some groundwork research and shortlisted two in-house applications developed by our firm's team. It was a hard journey to get the logs for those applications. We did some groundwork again to understand how the application is supposed to work and how it was designed.
We considered the efficiency points of UiPath Process Mining, which we can grab quickly. We generated the logs, linked the process graph, and understood three loopholes related to the log-in part and the user's behavior on the first attempt. There were some issues with the accuracy as well. For the login, there is a chain in which the prerequisites should be completed, and then the next task will be processed. However, the person processing the next task is logged in already.
When two people log in, as soon as the mail is ready, they'll process it. You should log in when required because of the load-balancing team. More than 20,000 people use one application. You should keep in mind that not everyone is supposed to log in and click somewhere to stay logged and avoid the time delay. Login will take time, according to human behavior, but that is not supposed to be the ideal behavior. The teams were educated to log in whenever required and sign off. This was one of the behavior changes, which may seem small. However, when more than 1,000 people do it, it would cause a considerable impact.
There were other issues related to the login. Sometimes, we have seen in the process graph that without going to the credential screen, the system would go to the main home page and log out. There was some bug, which was taken as a crucial security breach, and a build change was suggested to the application team. More than 100 instances in the last six months have been observed. After the user enters the username, it should ask for a password, but there is no linkage between them.