Set Limits to the DX Team's VBO Builds?

[stepher]

This is really meant to be a general question to Eric and the DX team.

Michael was kind enough to tag me in his November Community wrap up.  This got me thinking a bit about the topic, renaming a worksheet tab in Excel.  If it was something I was doing manually I would right-click or double-click the tab and enter the new text.  My proffered method works, as I am sure does the coding options others offered.

But this then lead me to the question, could the [fairly common] action of renaming a worksheet tab be added to the existing Excel VBO?  The obvious answer is, of course it could, but would the DX team build it?  It is not strictly an Excel function/action found on the ribbon.

So, that kind of frames my question.  When the Blue Prism DX development team are building a VBO specifically against an application, are there defined limits as to what would be considered 'in scope' versus up to the end-user to develop as a one-off?

Much thanks,

Red

[GeoffHirst]

Hi Red,

I will give you my perceptions and then perhaps @EricWilson1 could chip in with the facts. We tend to build things based on customer requests on our ideation pages. Those, depending on votes, are then decided on what we can do, can't do and ultimately will do. So, it really is guided by our customers, we might well think that wow an integration to xyz would be really popular, but how do we know that if customers haven't asked for it? Yes, xyz might be very popular, but is it also popular with Blue Prism users? I guess its finding the overlap and if enough customers want it, then it gets priority and then duly scheduled.

Like I said earlier, this is my perception, I am sure Eric can add more to this.

regards

[ewilson]

First, wrong tag. 😂 I'm @ewilson. The other tag is for my old Community Developer account, and I generally don't check messages for it.  

As for what we develop, Geoff has pretty well covered it. Ultimately, we want to build what our customers need, if we're able to. I caveat that because there are times when a connector is asked for that we simply can't build due to logistical issues like no access to the specific platform.

Normally, I would direct you to our Ideation page, but we're having issues with it due to internal platform updates. So, I would suggest posting to the DX community and tagging me. I capture ideas all the time and add them to our backlog. If the idea makes sense and it's something we can fulfill we'll make every effort to get it done.

Cheers,
Eric

[Neel1]

Hello @stepher  i am a great advocate of submitting the DX ideas on below link [this is not working as of now]. You can submit your feature request which you want to see in the DX VBO. you can track your request and other can also see/add comment and upvote there.

Ideas for new Assets on the Blue Prism Digital Exchange

Few of my enhancement request were easy and were in-corporate quickly  in the Assets. Thanks to @ewilson  and team. 

Saying all this @ewilson - i raised two ideas 😁  . i am starting a new conversation  so that your team can check those

[stepher]

First, thanks to @GeoffHirst and @ewilson for their responses.  And, just to make sure I have it correctly in my head... if an idea or request makes sense and has enough interest from the Community, then it could be considered a viable candidate for an application VBO, even though it may not be supported by base functionality within the application.

I have submitted a handful of suggestions to the Ideation page and been happy with the results.  In some cases, they have addressed my needs before I even submitted the requests.  But that comes more from me not checking the latest iteration of a VBO.

Again, my deep appreciation to Eric, Geoff, and the team.

Thanks, everyone.

Red