Knowledge block: Is this the right solution for us?

[amarks]

We've found that our users are submitting KB feedback for articles in lieu of opening tickets.

We'd like to add a section to the bottom of every knowledge article but we'd like to know the best way to accomplish this.

• Should we use a knowledge block?
• Should we use static text in a field in the article template?
• Should we use a knowledge block in a field in the article template?
• Something else?

Need Help?
Use the Submit button at the top of this article or click on this Submit link.

[Gregg Grose]

In our instance, we've used a knowledge block for a similar purpose - a disclaimer at the bottom of every article. And if the verbiage ever needs update, it's been easy to update the block once instead of updating every article.

Also, we do not have the ability to directly add blocks within a template so it's been useful to create a test article, add blocks to it and once finalized, copy the article body code of the article and then paste into the template.

[Arnaldo]

1. Block is a good opportunity especially if there will be need to modify/adapt  contents it in the future
2. Another option is to create a template that prefill fields in the form included HTML 
   Toggle the template bar
3. an finally you can configure in the database setting to prefill article body field witha a specific test for any new article See Create a knowledge base Set default knowledge field values
   
   Option 1 and  2 are manual activity that author must do 
   Option 3  is always automatically added  but author can remove it 
   
   

[qprinsloo]

I assume the issue is with end users and not in the fulfiller article form view. If so, we've had this same issue and put a custom widget in place on the Service Portal within the Knowledge Article container instead of handling this on each article.