Does it make sense to extend kb_knowledge table to task table?

JLeong
Mega Sage

Does it make sense to extend kb_knowledge table to task table?

One reason, the sysapproval_approver table does not show the:

  1. Approval for
  2. Short Description
  3. Entered

for Knowledge approval. That is because the 3 fields above are coming from the task table.

Instead of adding fields to the sysapproval_approver table, we are thinking of extending it to the task table. Will this cause issue?

Need your expert opinion please.

Thank you!

Regards,

Jocelyn

 

1 ACCEPTED SOLUTION

Alok Das
Tera Guru

Hi Jocelyn,

That's not a great idea. Task table is a core table and it's name is enough to say what records does it contain. A task which needs to be fulfill a requirement. Whereas the Knowledge table is there to share the knowledge. Both the things are differently configured. 

For the tables which do not extend the task table OOB we have document_id field which contains the sys_id of the approving record.

Kindly mark my answer as Correct and Helpful based on the Impact.

Regards,

Alok

View solution in original post

7 REPLIES 7

Thanks Alok for the very good explanation!

Regards,

Jocelyn

 

Sarup Paul
ServiceNow Employee
ServiceNow Employee

Knowledge Approval notifications will include the Short Description of the Article starting in Orlando. This is OOB behavior, however if your OOB notifications have been modified then the upgrade may skip that change. 

Thank you Sarup!