Honestly? Google and Stack Overflow are two of my best friends. Though when it comes to modifying an office application specifically, I'll also refer to their VBA guide. The Excel and Word VBOs are atypical compared to how you would extend the other VBOs, so I've also in the past just copied and modified an existing code stage that seemed somewhat similar.
The short of it is: "How do I do [x] in [y] language?" So if that comes to "How do I modify a column of a collection in C#", I'll search "C# datatable modify column" and see what I can find. If it's something like shared inboxes in outlook, I'll literally just search "outlook vba shared mailbox" and go from there.
Best practice if you're modifying an out of the box VBO, is to create a separate one and label it "Extended", so you can import new releases of the originals later on without losing any data.
Personally, I prefer to develop anything new in C# because that's where my coding background prior to Blue Prism mostly is. The only major downside is that it makes it more difficult when trying to share actions to people who are trying to combine them with the base VBOs, because those are in VB. But really, it's all personal preference.
------------------------------
Ami Barrett
Sr Product Consultant
Blue Prism
Plano, TX
------------------------------
