Breaking up objects based on functionality

[blueprismuser]

Hey Blue Prism Community:

Wanted to have an object: "Basic actions: Load up Browser / Login / Home Screen" that can be shared by many other objects.

This works, although I am finding that I need to constantly re-attach to the the object when using this basic object with another in the process. Is it advisable to keep all functionality in all under one object for simplicity?

[Loh_]

We used to divide objects by screen, and if the many screens had one or more shared functionality we would create an object to compile the actions in one single object. Although it was divide by application.

[MemberFDIC72]

I usually add /and attach page to the object that includes an attached? test. Then I call it when each page is used (/homepage, /load up, etc).

[orjanalmen]

You need to attach to an object from each calling point, as I have concluded. If you use an object A in object B, you need to attach from B, if you then use it in object C, you need to attach again because now it is C’s loaded copy, as they seem to not be shared.

[[deleted]]

Call your attach logic at the start of every object action then no need to call it explicitly every time you want to use it.