Added Note in Workflow Licensing article about using underscore instead of period #7281
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📋 Description
A customer experienced validation issues with their Workflow license. According to their feedback:
"I changed the license value from UMBRACO_LICENSES_UMBRACO_WORKFLOW to UMBRACO_LICENSES_Umbraco_Workflow (case sensitive) and instead of using Umbraco.Workflow as the key, I used Umbraco_Workflow (underscore instead of period). The key change is not necessary but changed it for consistency (both ways work).
I'm providing this information in the hopes that the documentation is updated. This issue applies to Umbraco Engage as well. I experienced it when setting it up a couple of days/weeks ago."
Umbraco Engage v13 and v16 already have this Note. So no changes there.
📎 Related Issues (if applicable)
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
Workflow v10, 13, 14, 15, 16
Deadline (if relevant)
Anytime
📚 Helpful Resources