Creating a general Work Task, is there an OOTB table for this?

[Mickey_Cegon]

We are in the middle of a zBoot, and in our previous instance, we created a Work Task table extended off the Task table, to house general tasks that are not a good fit for being a Request/Requested Item/Catalog task, and are not related to a specific Incident, Change, etc. They are just...work. But, now we've been told that extending the Task table or other tables is actually thought of as creating a custom application, and falls under the Platform Runtime subscription process or the Extension Application process. We are not creating a custom app, we just couldn't find a place to put work tasks into. 

Has anyone come across this gap, and if so, what was your solution? I was going to just use the Task table, but I believe I saw a wiki article that stated that emails should not be generated from the Task table, so we went down the extended table route. We have lots of Record Producers that just create a Work Task to a team to do operational tasks, and we're at the point in our zBoot where I need to find the solution to how we are going to address these. It just seems such a waste to put them into the Service Request area. Could we do a Record Producer, and just create stand-alone Catalog tasks?

Any ideas would be appreciated!

Mickey Cegon - FBL Financial Group, Inc.

[SanjivMeher]

You can actually use the task (not Catalog Task) table and map it from a record producer table.

In lot of cases, people also use visual task board which uses a different table. You can also utilize that table.

Is ServiceNow charging you if you extend a task table? Did you also check with ServiceNow for that?

[Mickey_Cegon]

We've been given a document by our SNOW rep that states the rules on extending the tables, and we just want to make sure we are doing the right thing. That document clearly states that if you extend Task, you are supposed to have Platform Runtime subcription, if you extend Incident, Change, etc, you are supposed to have Extension Application subscription. 

Mickey

[SanjivMeher · Accepted solution]

Ok. In that case, I would suggest using Task(task) table or Visual Task board (vtb_task) table, which should be good enough.

[sachin_namjoshi]

We have encountered similar issue for tasks which doesn't fall under catalog task, requested item, change tasks etc.

We have used private task to capture these kind of tasks.

Private task is an OOB table (vtb_task) which is used in visual task board tasks.But, you can use vtb_task OOB table to capture rest of tasks.

Regards,

Sachin