Update adding-a-workflowtype.md

[jonathoncove3]

Added information on adding settings to workflows

📋 Description

📎 Related Issues (if applicable)

✅ Contributor Checklist

I've followed the Umbraco Documentation Style Guide and can confirm that:

• Code blocks are correctly formatted.
• Sentences are short and clear (preferably under 25 words).
• Passive voice and first-person language (“we”, “I”) are avoided.
• Relevant pages are linked.
• All links work and point to the correct resources.
• Screenshots or diagrams are included if useful.
• Any code examples or instructions have been tested.
• Typos, broken links, and broken images are fixed.

Product & Version (if relevant)

Deadline (if relevant)

📚 Helpful Resources

• 🧾 Umbraco Contribution Guidelines
• ✍️ Umbraco Documentation Style Guide

[eshanrnh]

Thanks for the PR, @jonathoncove3 🙌We will review it asap.

[ronaldbarendse]

Looks like we already have documentation on adding settings to any supported type (e.g. field types, data sources, export types, prevalue sources, recordset actions and workflows) here: https://docs.umbraco.com/umbraco-forms/13.latest/developer/extending/adding-a-type#adding-settings-to-a-type. And all built-in setting views are listed here: https://docs.umbraco.com/umbraco-forms/13.latest/developer/extending/adding-a-type/setting-types.

However, the field type page provides more in-depth documentation about adding translations and the different configuration properties (like SupportsPlaceholders): https://docs.umbraco.com/umbraco-forms/13.latest/developer/extending/adding-a-fieldtype#field-settings.

So I'd recommend moving most of the setting documentation from the field type page to the 'Setting Types' page and adding a paragraph to all supported provider types with a minimal description/example and link to the generic setting types page...

[ronaldbarendse]

Also note that v14+ can benefit from the same improvements, but uses property editor UI aliases for the setting views (instead of the AngularJS file paths).