>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3547210. --> Reported by: [isholgueras](https://www.drupal.org/user/733162) Related to !70 !64 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>When a user has used the Conductor application to generate content, a draft is created in their Conductor account. When they close the extension and then come back to it for the same piece of content, the draft should be loaded into the application with all relevant fields filled with their previously entered data.</p> <p>Need to associate the Conductor Draft ID with the piece of content it&rsquo;s being used on</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>We associate the <code>draftId</code> with the node_id in a new table. On every page load, the backend will put the <code>draftId</code> in <code>drupalSettings.conductor.draftId</code> (or a better place) so the client (javascript) is able to load all the draft in the different table using the Writing Assistant Draft API.</p>