How to remove the add card button from visual task board?

[Ravi Chandra_K · Accepted solution]

Hi @Abinash10 

Currently, out of box there is no way to disable the 'Add Card' button. 

refer: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717253

please hit the Thumb Icon and mark solution as Correct if it helped !!

Regards,

Ravi Chandra.

[Ravi Chandra_K · Accepted solution]

Hi @Abinash10 

Currently, out of box there is no way to disable the 'Add Card' button. 

refer: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717253

please hit the Thumb Icon and mark solution as Correct if it helped !!

Regards,

Ravi Chandra.

[jasonhansen]

When you say out of the box, do you mean the default configuration prevents it, but can the application be configured to disable the button?

[Dr Atul G- LNG]

Hi @Abinash10 

Greetings!!

VTB is OOTB and there is no way to remove the button also i am not sure what use case you have for this. By removing the Add Card, you are going to violate the basic purpose of VTB.

Please mark this response as correct or helpful or solution accepted if it assisted you with your question.

Regards
Atul G.
Learn N Grow With Atul G

[jonathanurie2]

It really depends on how invasive you want to be in your system. As the previous folks have stated, removing the "Add Card" button is kind of counter productive to the VTB. The closest way to achieve what you're looking for is to add an ACL to the target table and prevent the user from creating records on in from any context (including VTB) as detailed in this KB referenced above by Ravi: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717253

So, for example, you might create an ACL on the STRY table that prevents users with an executive view role from creating new records in the table. 

This is an okay solution, but it's not a great user experience if your users are supposed to create tasks in other contexts. 

I wouldn't recommend it, but you could try to create a global UI Script to do some DOM manipulation. It's an old-school solution that might work but I would NOT RECOMMEND IT. 

If you ignored my advice and did it, though, your global UI script would look something like this: 

if (window.location.href.indexOf("vtb.do") > -1) {
    var vtb_add_card_buttons_collection = document.getElementsByClassName("lane-add-card-btn");
    for (let i = 0; i < vtb_add_card_buttons_collection.length; i++) {
        vtb_add_card_buttons_collection[i].style.visibility = "hidden";
    }
}

To be clear, that would be a LAST RESORT. There's a couple of good reasons to not do this:

1) Polaris blocks global UI scripts, so it's not going to work in all contexts of ServiceNow. In general, Global UI scripts have been not recommended since like 2010 🙂 

2) Users that are decent at CSS and browser developer tools can just go in and show the button again. 

3) UI scripts will run on every page load and so there will be a performance hit to your instance. 

At any rate, your best bet is to tell your stakeholders that it's not possible. Short of that, you should restrict access to the VTB or create an ACL to prevent creation. 

Good luck!