Prevent data driven VTB

[felladin]

We have an issue where data driven VTB will make it possible for users to change field values on forms, that go against policy. The reason this is, is that a lot of limitations are bound to Client Scripts which are not honoured in VTB.

We removed the "Show Visual Task Board" option on tables (demands list v2), but in Istanbul there is now a button on the VTB start page that makes this even easier.

Are we the only ones that want to allow Freeform boards but not Data driven, as the latter is not locked down enough for end users?

Has anyone of you fixed the new "New" -button to only show Freeform option?

With regards

Anton Lindblad

[felladin]

Hello,

Afraid not. Been on vacation and have some more urgent matters than this (only a few users of VTB and they have been informed).

Will come back to this, but perhaps not until after Jakarta update.

If you find anything on your end or from ServiceNow, please update this thread or just message me.

Regards

Anton

[User666027]

Thanks for coming back to me.

We ended up on our end to create a business rule on insert that cancels the creation of the board. It checks if the user has an appropriate role before.

ServiceNow has not provided any solution to this so far (we raised a HI ticket to seek their advice).

Regards

Christophe

[valerie_gallot]

Hi all,

I have exactly the same requirement, and for the same reason (client script not honoured)

Here is what I did:

1) Read this thread to PREVENT the creation of guided board (only guided board must be forbidden as the lane field is a real field. Flexible boards are ok because lane field is independant of the data)

VTB's Can you hide only guided boards?

2) As the $vtb.do is not customizable at all, I just changed the messages to warn users :

BUT, as Anton, I would really like to HIDE some tables and some fields.

In the image below, all task tables are visible, even if the user does not have access to it.

I tried to define ACL but it seems that ACL are not called from this popup.

I also tried to change the "attribute" in the dictionary. By default it is: base_table=task,skip_root=false,base_start=true

I tried something else, but is had no effect at all.

Did you find a better way?

Thanks!

Valérie

[skfinch1984]

Hi Valerie,

How did you managed to rename the field on the pop up window?

Thanks

[skfinch1984]

I've managed to update the label by adding a new entry in the Message table with Field Lane being the key