Creating a KB article could not able to see the Default text which is in body of article SOW.

[SatishSuray]

Creating a KB article could not be able to see the Default text which is in body of article in SOW. Kindly help how to get same in SOW article body.

[Ankur Bawiskar]

@SatishSuray 

is it working with admin user?

if yes and not working with non-admin then try giving them "snc_required_script_writer_permission" role and then logout and login and see

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[SatishSuray]

No for admin also it is not working also the screen sort mentioned is related to admin.

[Vikram Reddy]

Hi @SatishSuray,

I did some research based of a support article, That default text is being injected by an applyTemplate() call, either a Knowledge article template or a default template named to match the kb_knowledge table, and applyTemplate is a native Platform UI function that ServiceNow has confirmed is not supported inside Service Operations Workspace: it throws a ReferenceError client-side and just leaves Article body blank, which is exactly what your second screenshot shows.

Since it's a scripting gap and not a layout or permission issue, you need a workspace-safe replacement instead of the native call:

• Call GlideAjax against the AjaxClientHelper script include's getValues method, passing the template sys_id and g_form.getTableName()
• Loop the returned response items and push each value with g_form.setValue()
• Trigger it from an onLoad client script set to run in Workspace (UI type: All), replacing your applyTemplate() call

References

• Method "applyTemplate" does not work in Agent Workspace with ReferenceError: applyTemplate is not de...
• applyTemplate on Agent Workspace/Portal (workaround using AjaxClientHelper)

Thank you,
Vikram Karety
Octigo Solutions INC