Output Mappings (Revised)
Deleting the section on how variables are handled when output mappings are present, as this behavior is misleading for common use cases.
Description
When should this change go live?
- [ ] This is a bug fix, security concern, or something that needs urgent release support. (add
bugorsupportlabel) - [ ] This is already available but undocumented and should be released within a week. (add
available & undocumentedlabel) - [ ] This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add
holdlabel) - [ ] This is part of a scheduled alpha or minor. (add alpha or minor label)
- [x] There is no urgency with this change (add
low priolabel)
PR Checklist
- [ ] The commit history of this PR is cleaned up, using
{type}(scope): {description}commit message(s)
- [ ] My changes are for an upcoming minor release and are in the
/docsdirectory (version 8.8). - [x] My changes are for an already released minor and are in a
/versioned_docsdirectory.
- [ ] I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
- [ ] Engineering team review
- [ ] Technical writer review via
@camunda/tech-writersunless working with an embedded writer.
@zaycodes could you take a look at this please? 🙏
Thanks so much for your contribution @mkalaur, great work 🚀
@mkalaur is this only applicable to 8.8 or does it also apply to 8.9 so we can include it in the 8.9 docs?
@zaycodes I haven't checked 8.9 yet, but it should apply if no changes have been done onto the components.
Hi @mkalaur -- can you please apply this to the next version of docs as well in the docs folder of this repo? I can then approve and merge this for you 👍
Hi @mkalaur -- let us know if you are having trouble with porting this to the other versions of the documentation. @zaycodes Alternatively we may need to open a new PR backporting/forwardporting?