One use case is to automate single sign-on for different applications with the Active Directory. When people change roles within the company, we need to alter the permissions for multiple users. Another use case is assigning tickets to technicians. We classify what the customer needs and then automatically transfer the ticket to the person in our company who will handle this case. We also have some financial automation dealing with bank transactions.
We sometimes use Automate to help us with data migration. When we have a new CRN that is a hotspot, we make a little robot for data migration because the company has accumulated a lot of data in 30 years. We only did this once and changed the bot after three months. These are some of our use cases. We have had 40 different automation cases in three years.
We like to deploy on-premises because we have many related programs. When our customers make some tickets, we prefer to have everything in-house rather than on the cloud. We have servers in our office. One of the principal applications is on the server, and we have five bots in different areas, including finance, human resources, and operations.
Since adopting Automate, we have spent much less time on general tasks. In the past, we had one person writing all the emails and assigning them to the people who would handle the case. Now, that is not necessary. Another example is data migration. Migrating a large volume of data sometimes involves repetitive tasks. It's easier and faster for us to develop a little robot to do all that.
It's pretty easy for us to use a bot for single sign-on. When people join the company, we can add them to the bot and set all their permissions based on the Active Directory. Our employees spend less time on these tasks and are more productive.
It also reduces human error. When you have a human dealing with ticketing, they must collect customer information like names, phone numbers, ticket numbers, etc. It's always possible for the employee to mix up customer information or input the wrong numbers, but the bot never makes these mistakes unless they are broken.
Automate has over a hundred connections with email, PDFs, Excel, the web, and various areas. It's like Excel, which has functions, so you don't need to know how to code or be a developer. People need to understand how to use all these connections and functions to customize the solution. Having a little technical knowledge is better because it's faster and easier to use, but you don't need to know how to code.
All the applications that we need are drag and drop. A lot of functions can be implemented quickly with only some tiny adjustments. They change only one value and the name, then drag and drop. It's essential for us.
Our employers have strong technical backgrounds, and we have a standard training course for Automate that takes about 10 hours. Usually, we have four sessions that are about two and a half hours. It's crucial when you have a training session that you have some time in between to apply the knowledge and improve. After the next session, you take a week to test and improve. After about 10 hours, you can understand how to use the system well.
They also have Automate Academy, where you can learn best practices. The problem with RPA is that it's impossible to know everything about data and SAP. The standard training is high quality, and you can improve as you go. If you need something special, you can check the bots the community has produced and see how users have built bots using data from ServiceNow or many other solutions.