-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can read how to use an ad-hoc subprocess #4729
base: main
Are you sure you want to change the base?
Conversation
Extend the BPMN coverage page by the ad-hoc marker.
Add a new page for the BPMN ad-hoc marker and describe its usage.
👋 🤖 🤔 Hello, @saig0! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
For reviewers You can review the new/updated pages in the preview environment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Clear and easy to read docs, thank you @saig0
Important Do not merge! The PR has a target release 8.8. We need to wait until we publish the version 8.7. |
The preview environment relating to the commit 51b476a has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4729/index.html |
Description
Add a new page for the BPMN ad-hoc marker. Extend the BPMN coverage overview.
closes #4712
When should this change go live?
hold
label or convert to draft PR)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/
).I included my new page in the sidebar file(s).
I added a redirect for a renamed or deleted page to the .htaccess file.