This is a simple tip for beginners that will speed up your build time and stop your arm from aching after long periods in Studio. Use your non-mouse hand to operate F2 and F3 on the keyboard, in order to flip between the Pointer and Link modes. With ...
Sometimes during development you'll have a long list of field names to enter into BP that you know will be painful to type in and you're likely to make mistakes. But knowing that BP diagrams are based on XML, there are workarounds for faster and accu...
The BP DB contains a lot of information that could useful for admin/BAU/audit/upgrade yet much of it cannot be extracted into a report. It would be nice to have a suite of reports made available. For example:
Asset inventory
All objects, pages, input...
We already have things like GetResourceName() but it would useful for a process/object to know other details such as:
GetMyName() - eg what's this process calledGetMyParentName() - eg which parent called this objectGetMyPage() - eg what's the name of...
When creating a new process or object, make the default behaviour be that the user selects a template. This will promote Best Practice, a 'house' style and discourage 'one of a kind' developments.Granted this is already possible via Save As but encou...
One workaround is to launch the browser via the Utility - Environment VBO then use the Wait for Process action to wait for BluePrism.MessagingHost.exe. Then once you know the browser and the messaging host are ready, use Attach.
Hi @michaeloneil the action I posted should work 'as is' and will not need anything from the original Excel VBO. It's a 'lightweight' way of adding new Excel functionality without having to mimic the complexity of the default VBO.
Hi Joanne - it's best not to edit the original Excel VBO, so make a new VBO for your bespoke actions. Add a code stage like this, with workbook name, worksheet name and new worksheet name as inputs. The logic below makes the workbook and worksheet na...
A starting point would be to record a macro of you doing this manually, then take a look at the resulting macro VBA code. That should indicate what the equivalent .Net code would look like. And from there you can try creating a VBO with that .Net cod...
