Skip to content

remove c7 only content from bpmn and modeler docs #5312

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.

Sign up for GitHub

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

Merged
merged 13 commits into from
Apr 7, 2025
+21 −2,295
Merged

remove c7 only content from bpmn and modeler docs #5312

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
be8eb11
remove c7 only content from bpmn and modeler docs
christinaausley Mar 19, 2025
82a4284
Merge branch 'main' into remove-c7-content
christinaausley Mar 24, 2025
c707ada
replace flags
christinaausley Mar 31, 2025
6c26860
fix redirects
christinaausley Mar 31, 2025
dbeb46e
Merge branch 'main' into remove-c7-content
christinaausley Mar 31, 2025
a6aad81
Merge branch 'main' into remove-c7-content
christinaausley Apr 3, 2025
61489c0
fix build
christinaausley Apr 3, 2025
526be6c
add redirects
christinaausley Apr 3, 2025
b749cbd
update redirects
christinaausley Apr 3, 2025
6411608
Merge branch 'main' into remove-c7-content
christinaausley Apr 4, 2025
321421a
Update static/.htaccess
christinaausley Apr 7, 2025
b69485f
Update docs/components/modeler/desktop-modeler/flags/flags.md
christinaausley Apr 7, 2025
2464b4b
fix httl links
christinaausley Apr 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions docs/components/concepts/workflow-patterns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,14 +76,6 @@ In BPMN, you can simply model a loop:

This exclusive gateway contains the expression to decide if to continue or exit the loop. The gateway can be before or after the loop.

There is also a specific loop task marker in BPMN:

<div bpmn="workflow-patterns/loop-marker.bpmn" />

:::note
The loop task marker event is supported in Camunda 7, but not yet in Camunda 8. It is on the roadmap and will eventually be available in Camunda 8.
:::

### Static parallel branches

Imagine you want some tasks known during design time to be carried out in parallel. Refer to [Workflow Pattern 2: Parallel Split](http://www.workflowpatterns.com/patterns/control/new/wcp2.php) and [Workflow Pattern 33: Generalized AND-Join](http://www.workflowpatterns.com/patterns/control/new/wcp33.php): "The divergence of a branch into two or more parallel branches each of which execute concurrently" plus "the convergence of two or more branches into a single subsequent branch."
Expand Down Expand Up @@ -210,10 +202,6 @@ You can find more information in [our documentation about messages](/components/

Sometimes, a subprocess needs to communicate with its parent process without ending the subprocess yet. BPMN allows this by an [escalation event](/components/modeler/bpmn/bpmn-coverage.md).

:::note
The escalation event is supported in Camunda 7, but not yet in Camunda 8. It is on the roadmap and will eventually be available in Camunda 8.
:::

<div bpmn="workflow-patterns/escalation.bpmn" callouts="event" />

<span className="callout">1</span>
Expand All @@ -228,10 +216,6 @@ The subprocess can raise the escalation any time:

While messages are always targeted at one specific process instance, you might also want to inform many processes about an event at once. For example, you might regularly adjust certain customer scoring rules that always should be taken into account immediately. This can be implemented using the [signal event](/components/modeler/bpmn/bpmn-coverage.md).

:::note
The escalation event is supported in Camunda 7, but not yet in Camunda 8. It is on the roadmap and will eventually be available in Camunda 8.
:::

<div bpmn="workflow-patterns/signal-catch.bpmn" callouts="signal"/>

<span className="callout">1</span>
Expand Down
512 changes: 0 additions & 512 deletions docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md
View file
Open in desktop

This file was deleted.

Binary file removed ...r/desktop-modeler/element-templates/img/c7-defining-templates/custom-fields.png
View file
Open in desktop
Binary file not shown.
Binary file removed ...odeler/element-templates/img/c7-defining-templates/default-errors-rendering.png
View file
Open in desktop
Binary file not shown.
Binary file removed ...sktop-modeler/element-templates/img/c7-defining-templates/default-rendering.png
View file
Open in desktop
Binary file not shown.
Binary file removed ...desktop-modeler/element-templates/img/c7-defining-templates/entries-visible.png
View file
Open in desktop
Binary file not shown.
Binary file removed ...r/desktop-modeler/element-templates/img/c7-defining-templates/field-boolean.png
View file
Open in desktop
Binary file not shown.
Binary file removed .../desktop-modeler/element-templates/img/c7-defining-templates/field-dropdown.png
View file
Open in desktop
Binary file not shown.
Binary file removed .../modeler/desktop-modeler/element-templates/img/c7-defining-templates/groups.png
View file
Open in desktop
Binary file not shown.
Binary file removed ...top-modeler/element-templates/img/c7-defining-templates/scope-custom-fields.png
View file
Open in desktop
Binary file not shown.
4 changes: 2 additions & 2 deletions docs/components/modeler/desktop-modeler/flags/flags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ As a result, the app will only allow users to model BPMN diagrams.

<span class="badge badge--platform">Camunda 7 only</span>

To disable the [history time to live hint](../../reference/modeling-guidance/rules/history-time-to-live.md) in scenarios where the engine configures HTTL, configure `flags.json`:
To disable the [history time to live](https://docs.camunda.org/manual/latest/modeler/history-time-to-live/) hint in scenarios where the engine configures HTTL, configure `flags.json`:

```js
{
Expand All @@ -121,7 +121,7 @@ To disable the [history time to live hint](../../reference/modeling-guidance/rul

<span class="badge badge--platform">Camunda 7 only</span>

To set a default [history time to live](../../reference/modeling-guidance/rules/history-time-to-live.md) value to be used in newly created models, configure `flags.json`:
To set a default [history time to live](https://docs.camunda.org/manual/latest/modeler/history-time-to-live/) value to be used in newly created models, configure `flags.json`:

```js
{
Expand Down
41 changes: 0 additions & 41 deletions docs/components/modeler/reference/modeling-guidance/rules/history-time-to-live.md
View file
Open in desktop

This file was deleted.

1 change: 0 additions & 1 deletion docs/components/modeler/reference/sidebar-schema.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,6 @@ module.exports = {
"components/modeler/reference/modeling-guidance/rules/error-reference",
"components/modeler/reference/modeling-guidance/rules/escalation-reference",
"components/modeler/reference/modeling-guidance/rules/feel",
"components/modeler/reference/modeling-guidance/rules/history-time-to-live",
"components/modeler/reference/modeling-guidance/rules/message-reference",
],
},
Expand Down
1 change: 0 additions & 1 deletion sidebars.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,7 +269,6 @@ module.exports = {
"components/modeler/desktop-modeler/element-templates/configuring-templates",
"components/modeler/desktop-modeler/element-templates/using-templates",
"components/modeler/desktop-modeler/element-templates/defining-templates",
"components/modeler/desktop-modeler/element-templates/c7-defining-templates",
"components/modeler/desktop-modeler/element-templates/additional-resources",
],
},
Expand Down
13 changes: 13 additions & 0 deletions static/.htaccess
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,6 +180,19 @@ RewriteRule ^docs/next/apis-tools/tasklist-api/(.*)$ /docs/next/apis-tools/camun
# 8.7: content moves introduced prior to the release of version 8.7.
#---------------------------------------------------------------------------------

# Reroute element templates and HTTL to C7 docs
RewriteRule ^docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates/(.*)$ https://docs.camunda.org/manual/latest/modeler/element-templates/ [R=301,L]
RewriteRule ^docs/next/components/modeler/desktop-modeler/element-templates/c7-defining-templates/(.*)$ https://docs.camunda.org/manual/latest/modeler/element-templates/ [R=301,L]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@christinaausley It looks that the next redirection does not work properly. The redirection kicks in only when I remove next from the path.

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will launch a PR @barmac 👍 This likely happened with the release.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason the /next redirects need to exist? We consider the vNext docs to be in-progress. The only time we preserve URLs in vNext with a redirect is when it is required by an external link from the product or connector element templates.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm perhaps we don't need that? We don't usually link to next, so my manual try could be considered as an edge case. Sorry for unnecessary trouble.

RewriteRule ^docs/8.7/components/modeler/desktop-modeler/element-templates/c7-defining-templates/(.*)$ https://docs.camunda.org/manual/latest/modeler/element-templates/ [R=301,L]
RewriteRule ^docs/8.6/components/modeler/desktop-modeler/element-templates/c7-defining-templates/(.*)$ https://docs.camunda.org/manual/latest/modeler/element-templates/ [R=301,L]
RewriteRule ^docs/8.5/components/modeler/desktop-modeler/element-templates/c7-defining-templates/(.*)$ https://docs.camunda.org/manual/latest/modeler/element-templates/ [R=301,L]

RewriteRule ^docs/components/modeler/reference/modeling-guidance/rules/history-time-to-live/(.*)$ https://docs.camunda.org/manual/latest/modeler/history-time-to-live/ [R=301,L]
RewriteRule ^docs/next/components/modeler/reference/modeling-guidance/rules/history-time-to-live/(.*)$ https://docs.camunda.org/manual/latest/modeler/history-time-to-live/ [R=301,L]
RewriteRule ^docs/8.7/components/modeler/reference/modeling-guidance/rules/history-time-to-live/(.*)$ https://docs.camunda.org/manual/latest/modeler/history-time-to-live/ [R=301,L]
RewriteRule ^docs/8.6/components/modeler/reference/modeling-guidance/rules/history-time-to-live/(.*)$ https://docs.camunda.org/manual/latest/modeler/history-time-to-live/ [R=301,L]
RewriteRule ^docs/8.5/components/modeler/reference/modeling-guidance/rules/history-time-to-live/(.*)$ https://docs.camunda.org/manual/latest/modeler/history-time-to-live/ [R=301,L]

# Remove event ingestion from 3.14
RewriteRule ^optimize/apis-tools/optimize-api/event-ingestion/(.*)$ /optimize/apis-tools/optimize-api/overview/$1 [R=301,L]

Expand Down
16 changes: 0 additions & 16 deletions versioned_docs/version-8.5/components/concepts/workflow-patterns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,14 +76,6 @@ In BPMN, you can simply model a loop:

This exclusive gateway contains the expression to decide if to continue or exit the loop. The gateway can be before or after the loop.

There is also a specific loop task marker in BPMN:

<div bpmn="workflow-patterns/loop-marker.bpmn" />

:::note
The loop task marker event is supported in Camunda 7, but not yet in Camunda 8. It is on the roadmap and will eventually be available in Camunda 8.
:::

### Static parallel branches

Imagine you want some tasks known during design time to be carried out in parallel. Refer to [Workflow Pattern 2: Parallel Split](http://www.workflowpatterns.com/patterns/control/new/wcp2.php) and [Workflow Pattern 33: Generalized AND-Join](http://www.workflowpatterns.com/patterns/control/new/wcp33.php): "The divergence of a branch into two or more parallel branches each of which execute concurrently" plus "the convergence of two or more branches into a single subsequent branch."
Expand Down Expand Up @@ -210,10 +202,6 @@ You can find more information in [our documentation about messages](/components/

Sometimes, a subprocess needs to communicate with its parent process without ending the subprocess yet. BPMN allows this by an [escalation event](/components/modeler/bpmn/bpmn-coverage.md).

:::note
The escalation event is supported in Camunda 7, but not yet in Camunda 8. It is on the roadmap and will eventually be available in Camunda 8.
:::

<div bpmn="workflow-patterns/escalation.bpmn" callouts="event" />

<span className="callout">1</span>
Expand All @@ -228,10 +216,6 @@ The subprocess can raise the escalation any time:

While messages are always targeted at one specific process instance, you might also want to inform many processes about an event at once. For example, you might regularly adjust certain customer scoring rules that always should be taken into account immediately. This can be implemented using the [signal event](/components/modeler/bpmn/bpmn-coverage.md).

:::note
The escalation event is supported in Camunda 7, but not yet in Camunda 8. It is on the roadmap and will eventually be available in Camunda 8.
:::

<div bpmn="workflow-patterns/signal-catch.bpmn" callouts="signal"/>

<span className="callout">1</span>
Expand Down
Loading
Loading