{"version":"2.1.274","anchor":"quickstart-flow-gains-a-real-document-artifact-type-path","canonical_anchor":"quickstart-flow-gains-a-real-document-artifact-type-path","heading":"Quickstart flow gains a real 'document' Artifact type path","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/quickstart-flow-gains-a-real-document-artifact-type-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Quickstart flow gains a real 'document' Artifact type path\n\nArtifact quickstart for 'document' now looks up a real matching document type\n\n**What**\n\nWhen the Artifact tool's quickstart flow handles a request for a 'document', it now goes through the same type-lookup process already used for 'slides' and 'design': it looks up a matching artifact type, lists candidates if the request is ambiguous, and handles the case where no type catalog is available. Previously, 'document' requests were hard-coded to always fall back to a first-party Docs connector or a generic quickstart.\n\n**Why**\n\nThis makes document quickstarts behave consistently with slides and design, correctly picking a specific document type when one is available instead of always falling back to a generic path.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}