Printing knowledge articles

[JD Barlow]

Does anyone else have issues printing knowledge articles directly from Employee Center? We have a requirement to be able to print articles from the front-end of Employee Center. I have tried in both my PDI and our company's site and below is what I get. Everything is OOB configuration for Xanadu. The article is just text.

I have seen some solutions recommended on the community but they all require backend access to ServiceNow. We need something that front-end users can use. I would think this would be OOB functionality that doesn't require much setup, but maybe I am missing something.

(It seems to be an issue when printing any page in Employee Center - not just knowledge articles)

Any recommendations are welcome. Thank you!

[RaghavSh]

Agreed!

[JD Barlow · Accepted solution]

To close this loop, I opened a support case with ServiceNow. They sent the following solution which fixed the issue in our instance....

Under the EC Theme for the ESC portal, go to the CSS Variables section and add the below code:

@media print {
.sp-page-root { container-type: normal; }
}

Hopefully this works for others, too.

[David Lundy]

Hey @JD Barlow,

We have similar problems printing out of EC.  I tried adding the CSS modification you cited, but it didn't make a difference.  Is it supposed to add anything to the page?  A "print" button for example?

I tested by just right-clicking and choosing "Print" through Chrome.

Dave

[JD Barlow]

@David Lundy No, the print CSS snippet just makes the pages printable using the native browser print option. A print button is not created and there are no visible changes to the pages. This originally fixed our issue on Xanadu and it still works on our current Yokohama instance, but I can't speak to other family releases. Hopefully it doesn't break. Ideally, I'm hoping ServiceNow just adds this code to the system so customers don't need to modify it themselves.

[David Lundy]

Hmm.  Well, we're on Zurich and it didn't help there.  I was able to code up a widget that resolved the problem pretty cleanly, but I was hoping to not have to resort to that.  Still, it works, so that's all that matters.  🙂