Ext.data.JsonP.p931E21B6_A88E_4D4C_9498_E249747240F5({"guide":"<h1 id='p931E21B6_A88E_4D4C_9498_E249747240F5-section-update-document'>Update document</h1>\n\n\n<p><a\nhref=\"#!/guide/p2F6C9FC4_91A9_4C37_B107_05A466B7C906\">Document templates</a> contain placeholders that are replaced by information from the contract when the document is created. If <span\nstyle='font-weight:bold;font-style:italic'>content controls</span> are used as placeholders in Microsoft Word, the information contained within them can be updated later.</p>\n\n\n<blockquote>\n<p><span\nstyle='font-style:italic'>A new contract document is created for a contract. In the document header, the contacts and the contract partner's address are filled in automatically. During negotiations, the contact changes since the company has relocated. Using the &quot;Update document&quot; action, placeholders in the Word document can be updated automatically.</span></p>\n</blockquote>\n\n\n<p>The following figure shows a content control in Microsoft Word.</p>\n\n\n<p><p><img src=\"guides/p931E21B6_A88E_4D4C_9498_E249747240F5/img1.png\" alt=\"\" width=\"1101\" height=\"649\"></p></p>\n\n\n<p><span class=\"tag_warning\">The action updates all content controls defining valid ELO tags. Manual changes made after creating the document are updated accordingly in these fields.</span></p>\n\n\n<h2 id='p931E21B6_A88E_4D4C_9498_E249747240F5-section-action%3A-update-document'>Action: Update document</h2>\n\n\n<p>This action can be accessed on the <code>Contracts</code> tab in the ribbon. </p>\n\n\n<p><p><img src=\"guides/p931E21B6_A88E_4D4C_9498_E249747240F5/img3.png\" alt=\"\" width=\"1439\" height=\"169\"></p></p>\n\n\n<h3 id='p931E21B6_A88E_4D4C_9498_E249747240F5-section-requirements'>Requirements</h3>\n\n\n<ul>\n<li>The user logged onto the client is in a contract document.</li>\n<li><span\nstyle='font-weight:bold'>A document containing placeholders has been selected.</span></li>\n</ul>\n\n\n<h3 id='p931E21B6_A88E_4D4C_9498_E249747240F5-section-implementation'>Implementation</h3>\n\n\n<p><span class=\"tag_warning\"><span\nstyle='font-weight:bold'>Action definitions:</span> Definitions of the actions for the clients are located in the <code>sol.contract.documents.UpdateDocument</code> configuration.</span></p>\n\n\n<p>The <span\nstyle='font-weight:bold'>technical workflow</span> is implemented by ELOas action <code><a href=\"#!/api/sol.contract.as.actions.CreateDocument\" rel=\"sol.contract.as.actions.CreateDocument\" class=\"docClass\">sol.contract.as.actions.CreateDocument</a></code>.</p>\n\n\n<p>If successful, the following events are transferred to the client:</p>\n\n\n<table><thead><tr><td>Event</td><td>Description</td><td>Status</td></tr></thead><tbody><tr><td>GOTO</td><td>Shows the newly created element in the client.</td><td></td></tr></tbody></table>\n\n","title":"Update document"});