Import MS Word Documents into CWM

[Averell]

Thousands of companies worldwide manage their SAP process documentation using SAP SolDoc, which is a functional part of the Solution Manager. However, the classic Solution Manager has been discontinued by SAP for 2027. An alternative is therefore being sought. Confluence is often used for this purpose. However, this leads to this ‘documentation island’ continuing to be operated in isolation. However, there would be immense value to be gained from a direct bidirectional connection to CMDB content and, of course, direct documentation access for all support processes.
Documentation is a dynamic and collaborative process. CWM is the ideal tool for a modern and agile replacement for SolDoc.
SolDoc is nothing more than a framework in which documents can be stored. It ensures that links are created and that meta information is stored to enable searches. All of this can be easily mapped in ServiceNow. A ServiceNow and SAP partner in Switzerland is already working on a ready-made solution.
Only one question remains: the documentation in SolDoc is done through MS Word documents. These can be taken over directly into ServiceNow and imported into the knowledge base. There are ready-made functions for this. But how can existing documents be converted into CWM documents for further processing?
Specifically: How is it possible to convert MS Word documents into CWM documents?

[Lillian]

Hi @Averell  Thank you for sharing this feedback. We understand the need for better importing capabilities and have this planned in our backlog. For now, our recommendation is to use copy & paste to import content. 

[Averell]

Thanks @Lillian, 

I think copy & paste is too time-consuming and error-prone for the use case described, i.e. taking over the existing process documentation. My current customer manages around 700 documents, which around 150 users have write access to and a further 800 have read access to.

It would be good if you could quickly implement at least the same functionality that already exists for Knowledge Management for CWM.

Until then, I will suggest as a workaround to take over the documents into KM and, if necessary, to transpose them into CWM using a script, in order to make them collaboratively editable and releaseable there again.

[Lillian · Accepted solution]

Hi Averell,

Thanks for sharing this use case. I completely understand that copy & paste is not a feasible solution when managing large volumes of documentation. We will share this feedback with the team.

Thanks,

Lillian