Is there a way for users to copy a VTB?

[SusanWinKY]

We have a group who would like to create a VTB as a template, then copy that to create other VTBs when needed.   Is that possible?  

If not, is that functionality planned for a future release?

[Shahed Shah1]

Hi Susan

I don't know of a way within a Visual Task Board itself to clone it, but I am definitely interested to hear from the product management (or anyone in the know) about this being on the roadmap or not.

But, you can do this on the form itself (the vtb_board table) by creating a UI Action to do the clone, including the respective lanes (vtb_lane). I quickly hacked together a sample   Script Include as a proof of concept which I have attached.

You can then create the UI Action and call the utility with a script like:

// Clone the board
var originalBoard = current.name;
var clonedBoard = (new VTBCloneUtil()).cloneBoard(current);


// Redirect to the new board
action.setRedirectURL(clonedBoard);
gs.addInfoMessage(gs.getMessage("Cloned from {0} board", originalBoard));

I hope this helps you achieve your requirements

Regards

Shahid

[SusanWinKY]

Shahid, thanks for your reply!   We'll give this a try.

[Danielle Shingi]

Is there a way to clone the labels and the VTB members? The code above worked great for the board and the lanes.

[Uncle Rob]

So ... getting access to a VTB is as "simple" as being added to it.   The problem with VTB's is that ServiceNow needs to re-assess what kind of companies its selling to.   The informal "one user adds another" dynamic works very well for (very) small teams.   But ServiceNow sells to large enterprises, and that requires a more structured approach to VTB distribution.   Back when I was driving adoption for them, the big problem was that you couldn't make a VTB "for a group" - automatically add everyone to it, or automatically update its memberships based on group memberships.

The problem with Cloning the board is that they're absolutely *IDENTICAL* and you can have two teams working the same records in the same way... but not have visibility to each other?   Ideally everyone who works with (1) that body of records (2) in that way, should be equal participants on the VTB