The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Import of Word Documents to ServiceNow Knowledge base

welterp
Giga Contributor

I am trying to import Word Documents to ServiceNow Knowledge Articles with out losing any images. I have tried using the Word Cleaner and SED installs without any success. Is there any fix that works?

1 ACCEPTED SOLUTION

IMPORTANT UPDATE   - 03/03/2016:



I updated the entire script as I ran into some errors. And now it can also be used with journal fields!


See my reply: Re: Import of Word Documents to ServiceNow Knowledge base



You can also read more about it here: Create Knowledge Base Article (HTML field) or Comments (Journal field) from Email





you corrected the thrown exception errors on 4 of the lines in the script.



example on your line 18 with the part:


while(match == regex.exec(searchBody)){



the actual script is


while(match = regex.exec(searchBody)){



I know it throws an errors, but that's somehow required for the script to work. Because later you're going to use the value in the variable 'match' that has been set in line 18... If somebody has any idea how to formulate this correctly, you're welcome to help out.



Here is the full script that I use:


var gdt = new GlideDate();


gdt.addDays(2);


//current.valid_to = gdt;


var desc = email.subject;


desc = desc.replace("Knowledge:","");


current.short_description = desc.trim();


current.workflow_state = "draft";


current.topic = "General";


//current.category = "";


current.roles = "knowledge";




//Find and replace the image tags with the proper source.


//Get the number of attachments so the loop can be exited


//so it will stop no mater what.


var currentCount = 0;


var newBody = email.body_html;


var searchBody = email.body_html.replace(/\n/g, " ");




var regex = /<img(.*?)>/ig;


var match;


var match2;


while(match = regex.exec(searchBody)){


  //Add a style float tag next to the align tag.


  var alignText = match[0].replace(/align=['"]?left['"]?/gi, 'align="left" style="FLOAT: left"');


  alignText = alignText.replace(/align=['"]?right['"]?/gi, 'align="right" style="FLOAT: right"');


  searchBody = searchBody.replace(match[0], alignText);


  var regex2 = /src=("(.)*?"|'(.)*?'|(.)*?\s+$)?/ig;


  while(match2 = regex2.exec(alignText)){


  findAndReplaceImage(match2[1].replace(/\s+$/,"").replace(/"+/g,"").replace(/'+/g,""));


  }


  currentCount += 1;


  if(currentCount >= 100)


  break;


}


searchBody = searchBody.replace(/<o:p>(.*?)<\/o:p>/ig, "");


currentCount = 0;


var regex2 = /<!--\[if(.*?)<!\[endif\]-->/ig;


while(match = regex2.exec(searchBody)){


  searchBody = searchBody.replace(match[0], "");


  currentCount += 1;


  if(currentCount >= 100)


  break;


}


currentCount = 0;


var regex2 = /<!\[if !vml\]>(.*?)<!\[endif\]>/ig;


while(match = regex2.exec(searchBody)){


  searchBody = searchBody.replace(match[0], match[1]);


  currentCount += 1;


  if(currentCount >= 100)


  break;


}




//gs.log("Create Morning Post: " + searchBody);




current.text = searchBody;




current.insert();




event.state="stop_processing";




function getEmailSYSID(emailuid) {


  var em = new GlideRecord('sys_email');


  em.addQuery('uid', emailuid);


  em.query();


  while(em.next()) {


  //we execute the return only within a certain time difference between the creation of the attachment and now (in seconds)


  var dif = gs.dateDiff(em.sys_created_on, gs.nowNoTZ(), true);


  //gs.log("difference: " + dif + "eid: " + em.sys_id + " uid: " + em.uid); //debug


  if(dif < 300 && dif > -300){


  //gs.log('passed dif if: ' + em.sys_id + " uid: " + em.uid); //debug


  return em.sys_id;


  }


  }


  return "";


}





function findAndReplaceImage(imageText){


  var img = imageText;


  var imgName = img.substring(4, img.search(/@/i));


  var imgCode = "sys_attachment.do?sys_id=";


  //Get the sys_id of the attachment


  var gr = new GlideRecord("sys_attachment");


  gr.addQuery("file_name", imgName);


  gr.addQuery("table_sys_id", getEmailSYSID(email.uid));


  gr.query();


  if (gr.next()) {


  imgCode += gr.sys_id;


  }


  searchBody = searchBody.replace(img, imgCode);


}


View solution in original post

76 REPLIES 76

As explained, I updated the getEmailSYSID() function of his initial script, just see my comment above. Replace the initial function with my updated one and it should work.


Hi,



We have applied the same script which you updated in the function getEmailSYSID()



The function getEmailSYSID() is getting called but no records are returned by the query.



Although Querying the sys_email table manually with emailUID   is returning the correct email.



FYI the instance is domain separated.


I guess it's this one


var dif = gs.dateDiff(em.sys_created_on, gs.nowNoTZ(), true);



I used 'gs.nowNoTZ()' because it's in the same format as 'sys_created_on'... but it may be different for other locale settings. Add a log just before that variable:


gs.log(em.subject + " - created: " + em.sys_created_on + " - nowNoTZ: " + gs.nowNoTZ());



Does the 'sys_created_on' date match the nowNoTZ()?


If not, you need to play around with the GlideDateTime: https://wiki.servicenow.com/index.php?title=GlideDateTime



To be honest, I don't think that this method is really proper, but it works for us and I currently have no time to play around. As already mentioned, a much better method for querying the email in my opinion probably the 'message_id'. So if you want, try to adapt the script to be able to grab not only the 'uid' but also the 'message_id', something like:



function getEmailSYSID(emailuid, emailmsgid) {  


  var em = new GlideRecord('sys_email');


  em.addQuery('uid', emailuid);


  em.addQuery('message_id', emailmsgid);


  em.query();


  while(em.....


Have you found a cleaner way to do this process? I will need to do hundreds if not thousands and was hoping someone found an easier method of uploading the content.



Many Thanks for any assistance you can provide.


Well once I implemented this with my corrections it worked pretty well. We have used this now for a lot of articles and not even once did we encounter major issues. Some minor displacements, but they are quickly fixed once imported.