Just a thought...
With several years of working in BP RPA, my experience in our shop is that RPA developer vacancies are filled by business analysists but rarely programmers, with myself being the only exception to this 'rule'. As such I avoid creating too much code stages containing my code in the various languages allowed by BP. Instead, I try to stick to the building blocks handed to me by the good folks at BluePrism and try and build my stuff with them.
Sometimes however, you come across a challenge that would either be quite unsolvable without a code stage, or where sticking to the BP building blocks would just be overkill. In such cases I find code stages a perfectly viable alternative.
As a programmer, I have this strange rule that whatever I make, should be maintainable by whoever gets to work on it next. So, I stick to the rules, write readable and code in a structured manner, and in general do my best for the guy/gal next working on it.
In this view, making a new code stage to provide for something trivial that BP has already provided for makes not so much sense to me, neither why time should be spent on it nor what it could contribute to.
Again, just a thought...
...I am aware that we already had this discussion earlier, search for 'to code or not to code'.
------------------------------
Happy coding!
Paul
Sweden
------------------------------
Happy coding!
Paul, Sweden
(By all means, do not mark this as the best answer!)