docs: document "version tag" binding for linked resources

[jfriedenstab]

Description

Add documentation on the new versionTag binding type for linked resources (introduced with 8.6.0-alpha5).

Closes #4221.
Part of https://github.com/camunda/product-hub/issues/435.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[jfriedenstab]

@HanselIdes Two points from from the "Documentation Planning" section in https://github.com/camunda/product-hub/issues/435#issuecomment-1241783885 are still missing:

The user learns where to find the version tag in the Modeler for BPMN, form, and DMN

=> For DMN, I could add a section on the version tag to https://docs.camunda.io/docs/next/components/modeler/dmn/decision-table/, but there's no equivalent page for BPMN and Forms (yet).

The user learns where to look for the version tag in Operate for call activities. The version tag of forms and decisions cannot be found in Operate

=> I haven't mentioned Operate yet, because the implementation will not be done for the upcoming alpha.

[HanselIdes]

I added 2 non-blocking comments. I didn't see any updates to the Operate docs. Are these coming in a different PR? I saw your comment

[HanselIdes]

The user learns where to find the version tag in the Modeler for BPMN, form, and DMN
=> For DMN, I could add a section on the version tag to https://docs.camunda.io/docs/next/components/modeler/dmn/decision-table/, but there's no equivalent page for BPMN and Forms (yet).

@jfriedenstab I think a description of where to find the version tag field is sufficient - a screenshot is not necessary.

It's important to me that the user learns that the power of version tag and that it comes with a different kind of risk. That's why I suggested a reminder when choosing the version binding in my PR review

[mesellings]

@jfriedenstab Do you require a TW review on this for the alpha 5 release?

[jfriedenstab]

@mesellings Yes, I do :) I just wanted to address the other comments first.

[jfriedenstab]

I think a description of where to find the version tag field is sufficient

@HanselIdes: I've added a short sentence on where to set the version tag to the description of the versionTag type now, so that it's mentioned somewhere at least.

I'd say we should still further improve the docs and add a page that explains the general properties of a process (id, name, version tag) under the BPMN section (similar to the DMN page I linked above), but that could be done as a follow-up.

[mesellings]

@jfriedenstab I'll review this now for you 👍

[mesellings]

@jfriedenstab Due to the size of the PR can I make edits/commits directly to the branch?

[jfriedenstab]

@jfriedenstab Due to the size of the PR can I make edits/commits directly to the branch?

Sure, go ahead 🙂

[HanselIdes]

LGTM

[mesellings]

@jfriedenstab Reviewed and approved, just a few minor text edits, mostly for passive voice > active voice. Lgtm 👍

[jfriedenstab]

Thanks a lot, @mesellings! 👍🏻