Visual Task Boards - Guided issues

ryan_cox · ‎01-26-2015

So I started working with VTB and noticed that when you are using a Guided board it will change the values on records and ignore any rules. For instance on Incident if you do a guided board on state, it will allow you to change the state to whatever you like without requiring the required fields to be filled out.

Anyone else seen this or is it just me?

This is a BIG problem as I cannot find a way to limit users ability to use the guided task boards.

Thoguhts?

ryan_cox · ‎01-28-2015

Thanks all. I upgrade an instance to Eureka Patch 7 and have validated that this issue has been resolved. It now brings the record up in the original values before you tried to make the change with a warning, so you can fill out the form with the fields that would be required.

View solution in original post

Syaharruddin · ‎01-29-2015

Not sure if you will get this since the discussion is closed. Anyway, we are not using it yet. We've tested it in sandbox and found issues with guided task board so it's on hold for now. The freeform & flexible is great. We're currently on Eureka Patch 5. We will probably restart after upgrading to the latest patch.

HugoFirst · ‎01-29-2015

Thank you for the reply Syaharruddin.

Can you share the issues you found? I think we're in the same situtation. We're going to Patch 7, but will not enable VTB's because of the problems presented by guided task boards. I'll share the issue that's putting us off at the moment.

Using a guided VTB on the change request table (using the state column) allows an individual to create a change request in any state. Our normal process is to submit it, have it pass a preCAB review, then a CAB review and then go to a scheduled state. Someone using the VTB just mentioned can create a change request and put it in a scheduled state without going through any of the precursor steps.

I put in a business rule to prohibit inserts of the change_request table unless the state is Draft or Open. But I haven't had time to thoroughly test it yet.

A related, but less threatening issue is the fact that anyone can create a task record which is usually considered a catalog task, but without the parental requested_item record. Haven't pursued this one in detail yet, but I want to understand the implications before turning VTBs on.

That said, I'm a REAL FAN of VTB's and I REALLY WANT to have them available. We just need to be sure there are no land-mines in the code that will blow up on an unsuspecting user. I'm going to file some enhancement requests to ServiceNow to make these more manageable.