Prevent data driven VTB

felladin
Tera Guru

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

16 REPLIES 16

felladin
Tera Guru

Update on this,



I have a case open with Hi regarding the "New"-button in Istanbul. Unfortunately it appears the new functionality has been hard coded into the system. This means that any use of Visual Task Board involves allowing Data Driven board unless you create a new function for creating Freeform board and remove the "New"-button.



A few problems we've found so far:


  • "Create Data Driven" will provide the end user with a reference field showing all Task -tables.
  • Having picked a table, end user will be presented with all fields on that table.
  • Reference fields inside Visual Task Board has no reference qualifier (as far as I have found).
    • For example, setting up a VTB with service offering as lane and clicking "+Add Lane", the new reference field will provide all CI's in the CMDB, regardless of class.
    • Another example, the user picker reference fields will provide all users in the system.
  • Visual Task Board does not honour Client Script.
  • Lanes will show all available options.
    • For example, we have states not visible on form. These are presented as lanes.


This would not be such a big issue if there was e.g a sys property where you could set tables and fields to, by default, not be available in Data Driven Visual Task Boards. That way time could be spent securing the few cases where they are to be available.


As it stands now, should we allow Visual Task Boards at all (as there is no option to disable Data Driven but provide Freeform) we need to go through all Task -tables and their fields, as well as all referenced tables.


Chris__Silva
Kilo Guru

Hello Anton,



So far we found two ways, one using   acls and modifying the include scripts or   the other an onbefore busines rule - that delete the record .


The problem is that its nto as clean as we want, we even tried a new page but the problem is to "block "   the use of the new data driven board.


The problem being that even if the end users VTB record is deleted, they will get the first option buttons, right?


The ACL, where did you add it and with what settings?


Hi Anton,



Just curious if you found a way around this, as we are facing the same issue.



Thanks



Christophe