cancel
Showing results for 
Search instead for 
Did you mean: 

Component Object Best Practice

Jobskie
Level 3

Hi, I really need clarity on when I should create a component object for an application. I'm planning to set a standard on this multi layer approach and this means creating a component object for all objects even if they are small and not reusable such as setting values in excel using ExcelVBO. If a process interacts with 3 applications, it means 3 coponent objects that are non reusable. Will this have any negative effect on the performance of the bot in the long run that I should watch out for?



------------------------------
Jose Norberto Manrique
------------------------------
2 REPLIES 2

kishorKumar
Level 2

creating a component object should be based on the frequency of use and the complexity of the process. Too many non-reusable component objects can lead to performance issues, but reusable and complex component objects can improve modularity and maintainability. When deciding whether to create a component object, consider these factors and choose what's best for the specific use case.



------------------------------
kishor Kumar
------------------------------
Kishor Kumar Blue prism Developer Infosys Ltd.

Asilarow
MVP

I'd say don't.
That opens a can of worms that is difficult to close later.
KISS rule applies 😉
Reusable objects all the way.



------------------------------
Andrzej Silarow
Principal Consultant
RPA Guru
Europe/London
------------------------------
Andrzej Silarow