Aras TechDocs - how do I add the translations of documents?
Hi community, does anybody of you use TechDocs in combination with a language pack, so you can build a Technical Document in two languages? This question may sound silly. But how can I actually import the translated version of a document? In TechDocs I am just able to edit the default language (e.g. English) of a document. The secondary language (e.g. German) is always read-only and a so far didn´t find any way to actually start the translation of my document or to import the translated version. It´s really strange. TechDocs offers us buttons to change the documents´ language. We can make side-by-side comparison with the language variants. The user guide mentioned a Translation Process. That´s all fine. But there are no hints how to actually start the process of translation itself. I would be more than happy about any hints! Many thanks! Angela4.6KViews0likes3CommentsRead/write TechDoc content via REST (or similar) - where is the content stored?
Hi Community, does anybody know, where TechDocs actually stores the documents native data? E.g. is it possible to read the individual titles, sections or text elements? I have seen that native xml content of the document is stored in the content property of ItemType tp_Block. Is this the only location where the TechDoc document itself is stored? Or are there another ItemTypes involved? In the xml itself each entry has an own aras-id. But I wonder if this aras-id is really related to a existing item in the database? I want to connect to tech docs from am external data source via REST. The external source shall check if document content is still valid and maybe also write TechDoc content. In MPP we have individual items for Steps/Operation that store the data than will later render the process plan. Do we have something similar in TechDocs? Or do I need a separate ItemType to store these kind of content, so we later can use the data to generate the TechDoc from these item data? Thanks for any help! Angela7.7KViews0likes3CommentsTechDocs vs. Document ItemType - why not connected?
Hi, I made some tests with the Technical Document application. The latest version works very well and I like the idea of creating documents directly in Aras! But I struggle to understand, how TechDocs is intended to blend in into the regular lifecycle management. At the moment, TechDocs somehow looks like a standalone application for me! I completely miss some kind of revision handling for my technical document. To explain it more precise: Let´s take a short look at the regular Aras Document handling. Regular documents can be uploaded manually or created with help of the Office Connector or any other tool that fit the purpose. If we are honest, it doesn´t matter with authoring tool is used. It can be Word, Excel or something else. But in the end, all of these documents will share the same ItemType Document. From my POV, Aras TechDocs is just another Authoring Tool for the ItemType Document. I expected it to be integrated in a similar way then the Office Connector - but, it isn´t . Right now, I would be forced to download the published TechDoc PDF and then add it manually to the Document ItemType again. Only this way it can also be covered by regular change management. But this routine would completely kill all benefits that an integrated document application in Aras may have. That cannot be the solution! Is there some recommended way to handle TechDocs revisions? Do I miss something? Best regards! Angela5.3KViews0likes2Comments