Developer at a tech consulting company with 51-200 employees
Real User
2023-08-02T01:42:44Z
Aug 2, 2023
Hello @Avigayil Henderson , first let me explain that the log implementation is a plus across the organization. In fact, let's talk about only for log automation process. Imagine for a while you have the capability to know what's happening with every bot or application right now, so you have many opportunities to implement a great transversal solution. For example if you use UiPath you could write an understandable message on Orchestrator and the EventViever write a technical detail message of your windows or if you want to. But if you want to create a more sophisticated and organized and cross platform functional you need to think perhaps something like this: you need implement a DB Model that satisfies the requirements (Project, ProjectType, ProjectArea, MasterLog and DetailLog tables). The Project table stores the project type, project area and details of the project plus using a state. The MasterLog stores the project you want to store, the state of the log project (enabled or disabled), and the user-friendly message. The DetailLog stores the technical message obviously the datetime that it's occurred. Remember the all tables needs to use audit fields (lot of fields). By other way you need to expose the APIs to lets the applications to write on it. Don't forget to secure the use of the APIs using for example OTP (JWT). This is a brief (high level) idea that you should implement. I hope this helps!
Search for a product comparison in Robotic Process Automation (RPA)
There are all kinds of compliance requirements out there, so you're posing a pretty broad question, but generally speaking, security compliance requirements are going to involve continuous monitoring, access management, encryption, endpoint and network security, and patch management.
It's going to come down to a log management solution, many of which provide reports that help you prove compliance. But because compliance usually has governance requirements, meaning that upper management is aware of risk issues and can provide proper direction, your log management solution needs to be able to present the technical details in a way that is meaningful to potentially non-technical people. So it's important to vet the solutions well, so that you know they work for your environment and your C-suite.
There are also compliance consultants who can bring expertise to the table. And if you're not sure where to begin, consider implementing a risk assessment so that you know what areas are most applicable to your business.
Find out what your peers are saying about UiPath, Microsoft, Automation Anywhere and others in Robotic Process Automation (RPA). Updated: February 2025.
What is RPA? Robotic process automation (RPA) is a software technology that enables enterprises to build, deploy, and manage a virtual workforce made up of software robots (“bots”) that emulate the actions of humans in interactions with software and digital systems.
Hello @Avigayil Henderson , first let me explain that the log implementation is a plus across the organization. In fact, let's talk about only for log automation process. Imagine for a while you have the capability to know what's happening with every bot or application right now, so you have many opportunities to implement a great transversal solution. For example if you use UiPath you could write an understandable message on Orchestrator and the EventViever write a technical detail message of your windows or if you want to. But if you want to create a more sophisticated and organized and cross platform functional you need to think perhaps something like this: you need implement a DB Model that satisfies the requirements (Project, ProjectType, ProjectArea, MasterLog and DetailLog tables). The Project table stores the project type, project area and details of the project plus using a state. The MasterLog stores the project you want to store, the state of the log project (enabled or disabled), and the user-friendly message. The DetailLog stores the technical message obviously the datetime that it's occurred. Remember the all tables needs to use audit fields (lot of fields). By other way you need to expose the APIs to lets the applications to write on it. Don't forget to secure the use of the APIs using for example OTP (JWT). This is a brief (high level) idea that you should implement. I hope this helps!
There are all kinds of compliance requirements out there, so you're posing a pretty broad question, but generally speaking, security compliance requirements are going to involve continuous monitoring, access management, encryption, endpoint and network security, and patch management.
It's going to come down to a log management solution, many of which provide reports that help you prove compliance. But because compliance usually has governance requirements, meaning that upper management is aware of risk issues and can provide proper direction, your log management solution needs to be able to present the technical details in a way that is meaningful to potentially non-technical people. So it's important to vet the solutions well, so that you know they work for your environment and your C-suite.
There are also compliance consultants who can bring expertise to the table. And if you're not sure where to begin, consider implementing a risk assessment so that you know what areas are most applicable to your business.