https://www.aras.com/community/f/applications/4985/techdocs-vs-document-itemtype---why-not-connectedHi, 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 lifecycleja-JPTelligent Community 12https://www.aras.com/community/thread/2440?ContentTypeID=1Fri, 18 Jan 2019 10:45:17 GMT916d3f7e-8ddc-42f8-8d45-380822f51406:f1c33124-b679-4ed2-bf8b-00ed557d4dd5AngelaIp<p>I made a quick test of the concept and it&acute;s quite easy to pass the TechDoc publishing result to a regular Document.&nbsp;It even would be possible, to use the same code for published MPP process plans. But I still would be happy about any additional ideas!&nbsp;</p><div style="clear:both;"></div>https://www.aras.com/community/thread/2414?ContentTypeID=1Wed, 16 Jan 2019 16:12:48 GMT916d3f7e-8ddc-42f8-8d45-380822f51406:bbffb6b6-b19f-45f7-8e91-d9f0c122f640AngelaIp<p>I looked at the tp publishing service and maybe have an idea. How about this one?</p> <p>The tp_PublishingDialogApi is luckily not an internal Method. We can fully customize it and also the corresponding Form. Would it be possible to extend the dialog to add a Document binding? Right now, when publishing a TechDoc we can choose &quot;View in browser&quot; and &quot;Save as file&quot;. Why not adding an optional field for &quot;add/update in Document&quot;? We could also add some rules to prevent that a released Document is overwritten&nbsp;or directly create a new Document revision.</p> <p>In the Document it self we could add &quot;Tech Docs&quot; in the Authoring Tools lista and also add a backling to the tech doc.&nbsp;This way TechDocs would be more like the regular Office Connector.</p> <p>What&acute;s your opinion?</p><div style="clear:both;"></div>