Well, Q's to start with, at least, but looking for some A's...
Assuming one or more Drafts exist that refer to "Custom Form A", what is intended to happen ("As Designed") to the custom data entered on those Drafts if:
Topics help categorize Community content and increase your ability to discover relevant content.
For your second part, I can't answer what is intended to happen "as designed" but my (sometimes high) expectations would be:
Thank you for the questions.
Heather, thank you as well for the answers. They are all correct and that's how it works now, except for the last one. If an additional custom form is attached to the topic/queue for which there is already a draft created, next time the user opens the draft to submit the request, the request form will show the newly added custom form.
Doug, as for the first 2 questions:
Let me know if you have any other questions or feedback.
We implemented the drafts in an "auto draft" way so that users don't take any extra actions and if they do want to just submit the request, they can ignore the draft and it will be deleted when sent. So, there isn't an extra action required from the user if they don't want to deal with the draft.
Let me know if this answers your concern.
Thanks Doug! I am glad we clarified the first part.
For the API, let me check couple of thinks with the development team and get back to you.
Sorry for the delay in getting back to you on this. There is a way to access the drafts via API now, but it can be done by the logged in user only. We currently don't plan to make it widely available via our API.
I should note for anyone who uses layout templates and New Request is NOT in the first tab position under the Requests (issues) global nav. We have a request dashboard as the first tab and the New Request as the second tab, for example.
If you move the New Request button from the first position, then clicking on the name of the draft will not open that draft, it will open whatever dashboard is in the first position. OOPS!
Support is working on this. Putting the New Request button back to the first tab fixes the issue, though we haven't because the dashboard is more important than the draft mode right now.
I apologise for the inconvenience caused by that issue. It has been already fixed and should reach production with this week's patch.
No worries Anna. I had intended to circle-back and update my comment after finding out the patch coming soon; think it goes in overnight tonight?
I only posted here in case someone else ran into this "surprise."