-
Notifications
You must be signed in to change notification settings - Fork 184
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
Update "Get started with human task orchestration" guide to include Play #4401
base: main
Are you sure you want to change the base?
Update "Get started with human task orchestration" guide to include Play #4401
Conversation
@conceptualshark Don't worry, I'm going to rebase this and start again on Monday - I saw your changes, so I'll need to adapt the new stuff for this - don't spend any more time on it 😄 |
👋 🤖 🤔 Hello! 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. |
Content has changed considerably after a merge conflict, it didn't need a review at this point
This needs a review by Eric, so should not be merged - was waiting for the deploy workflow to be fixed - we can hopefully push this tomorrow |
@HanselIdes The preview environment is (finally) fixed and up for you to review: Depending on when you are able to review, we can try to get this into the release tomorrow, or push it afterwards? |
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.
This is good progress, but fundamental updates to the user journey and differences between Desktop Modeler+C8 Run, Web Modeler SM, and Web Modeler SaaS make it difficult to follow the changes. It's probably best to group the tabs as
Desktop Modeler | Web Modeler
especially because we're uniting the UX between Web Modeler SaaS and SM
This complicates the flow and also the table of contents, where there are two step 4s
|
||
import clsx from "clsx"; | ||
import Tabs from '@theme/Tabs'; | ||
import TabItem from '@theme/TabItem'; | ||
import SaasPrereqs from './react-components/saas-prerequisites.md' | ||
import Install from './react-components/install-c8run.md' | ||
|
||
Camunda 8 allows you to orchestrate processes with human tasks of any complexity. Utilizing user tasks, you can create and assign tasks to users. Then, users can perform their work and enter the necessary data to drive the business process. | ||
You can use Camunda 8 to orchestrate processes with human tasks of any complexity. User tasks allow you to create and assign tasks to users, who can then perform their work and enter the required data to drive the business process. |
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.
You can use Camunda 8 to orchestrate processes with human tasks of any complexity. User tasks allow you to create and assign tasks to users, who can then perform their work and enter the required data to drive the business process. | |
You can use Camunda 8 to orchestrate processes with human tasks of any complexity. Use the user task BPMN element to create and assign tasks to users, who can then perform their work and enter the required data to drive the business process. |
For the getting started with HTO guide, I'd also be interested in seeing @volodymyr-melnykc 's perspective as he's the HTO PM
@@ -100,13 +139,14 @@ To run this guide, make sure to be in **Implement** mode to specify the technica | |||
|
|||
1. A **start event** is automatically added to the canvas. Click it to display configuration and append options. |
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.
The start event should be automatically selected- you can check this behavior on SaaS
@@ -100,13 +139,14 @@ To run this guide, make sure to be in **Implement** mode to specify the technica | |||
|
|||
1. A **start event** is automatically added to the canvas. Click it to display configuration and append options. | |||
2. Click the rectangular **Append Task** icon to append a task. |
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.
2. Click the blue **link icon** in the lower right corner. A menu expands that allows you to create a new form. | ||
<img src={ModelerFormMenuImg} style={{width: 400}} alt="Annotation to open the form menu" /> | ||
3. Click **Create new form**. A form will be created and opened in the form editor. The form is automatically named. | ||
1. Click the blue **link icon** in the lower right corner. A menu expands that allows you to create a new form. |
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.
@@ -174,7 +213,7 @@ If the properties panel for your form doesn't open automatically, navigate to ** | |||
|
|||
## Step 3: Link the form to your process |
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.
If you create a form according to these instructions, then this step is automatically completed.
First, you must create the BPMN diagram file and project. | ||
|
||
1. Open Web Modeler, and click **New project**. Every file in Web Modeler requires a project. | ||
2. Select **Create new > BPMN diagram**. |
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.
For automation, users should always use process applications. They have the most features, including a smoother Play deployment experience
|
||
### Deploy and test run | ||
1. Click the **Play** tab to enter Play mode. | ||
1. Once the Play environment is ready, click **Start a process instance** to start testing your process. |
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.
As well as using Play mode to quickly validate and run your process in development, you can also: | ||
|
||
- Deploy the process to a [cluster](/components/concepts/clusters.md) in other environments such as testing, staging, and production. After you deploy your process, it can be run on the cluster. | ||
- Run and complete the user task in [Tasklist](/components/tasklist/introduction-to-tasklist.md). Applications such as Tasklist can be used by humans to complete tasks. As well as using Play mode and Tasklist to run a process, you can call the process via the API or an inbound trigger. Read more about [run options](/components/modeler/web-modeler/run-or-publish-your-process.md). |
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.
Thanks @HanselIdes I'll take another look at this - I really appreciate the comprehensive feedback 👍 |
@HanselIdes I've gone through the SaaS section and incorporated all your feedback - please check you are happy with the new structure, and I will move onto the SM section. https://preview.docs.camunda.cloud/pr-4401/docs/next/guides/orchestrate-human-tasks/
p.s. Ignore the right-hand menu for now, as it is still affected by the unchanged SM content. |
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.
The one thing that must be addressed is the inaccuracy between SaaS and SM. In this guide as it's written, SM represents local development (Desktop Modeler + C8 Run), not self-managed.
1. A **start event** is automatically added to the canvas. Click it to display configuration and append options. | ||
2. Click the rectangular **Append Task** icon to append a task. | ||
1. A **start event** is automatically added to the canvas and selected. | ||
2. Append a task. For example, hover over the blue plus icon and select the **Append Task** icon from the [context pad](/components/modeler/web-modeler/context-pad.md). |
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.
Arguably, the append element
option offers better discovery for automation options and fewer steps, combining step 2 and 4. @lmbateman / @nikku, do you think we should drive new users to use the append anything option?
@HanselIdes I've made those changes now, and other than the Append element comments, this is probably good to go for a final review? In summary, I changed language to Desktop/Web as suggested, added a context pad link, and removed some heading elements from the Desktop validate section to avoid them appearing in the right-hand TOC (until we can fix this so it takes tabbed content into context). |
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.
LGTM!
- Select **Self-Managed** to see an example using Camunda 8 Run and Desktop Modeler. | ||
- Select **SaaS** to see an example using Camunda 8 SaaS and Web Modeler. | ||
- Select **Desktop** to see an example using Camunda 8 Run and Desktop Modeler in a local development environment. | ||
- Select **Web** to see an example using Camunda 8 SaaS and Web Modeler. |
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.
Web Modeler Self-Managed is excluded, but that's appropriate for this stage of the journey
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.
My lingering question here is why the addition of Play changes the Web Modeler section of this guide into "validate with Play" as the end result, and not completing and checking on the task in Tasklist and Operate.
I don't think this guide should solely walk a user through building a model and using Play for initial validation. Presenting options for understanding how that process moves through/works with Operate and Tasklist is an equally important end result.
<Tabs groupId="install" defaultValue="saas" queryString values={ | ||
[ | ||
{label: 'Self-Managed', value: 'sm' }, | ||
{label: 'SaaS', value: 'saas' }, | ||
{label: 'Desktop', value: 'sm' }, |
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.
Would it be beneficial for these to read more descriptively/match the description above? "SaaS and Web Modeler" | "Self-Managed and Desktop Modeler". As labels, they're short enough to scroll by right now, and if SaaS vs SM didn't entirely capture the paths here, I don't think Desktop vs Web does either.
Per Eric's point, I don't want the implication to be that these are exclusive methods for either version, but I do think we should align with the current Getting Started experience defining SaaS and SM as the modes of moving through the guides.
|
||
In this example, you will learn how to: | ||
|
||
- Create and run your first process with a human in the loop. |
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.
I like the later wording of "route (a) process flow based on a user decision." "A human in the loop" still feels ambiguous; not blocking, but I'm not sure if a more descriptive task here would be helpful, though we describe the action enough otherwise so it may just be me.
|
||
### Create a new file | ||
Start by creating and designing a process to demonstrate how to route the process flow based on a user decision. In this example, you will create a process to decide what to eat for dinner. |
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.
Start by creating and designing a process to demonstrate how to route the process flow based on a user decision. In this example, you will create a process to decide what to eat for dinner. | |
To learn how to route a process flow based on a user decision, you will create and design a process to decide what to eat for dinner. |
5. Select the user task and click on the diamond-shaped icon to append an exclusive gateway. The gateway allows to route the process flow differently, depending on conditions. | ||
6. Select the gateway and append a task by clicking the task icon. Repeat it to create a second process flow. Name the tasks based on what the user decides to eat: in this case, we've named ours `Prepare chicken` and `Prepare salad`. | ||
1. A **start event** is automatically added to the canvas and selected. | ||
2. Append a task. For example, hover over the blue plus icon and select the **Append Task** icon from the [context pad](/components/modeler/web-modeler/context-pad.md). |
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.
Context pad is more useful for the SaaS/web modeler side of things and not the same experience in desktop. If this section is swapped to Append element
instead (and the context pad reference removed), it brings it back in line with the Desktop experience and would remove the need for another set of split/tabbed content.
@conceptualshark The goal mentioned in the guide says: The best way to "drive the process flow" is through Play. It requires no navigation, and the additional features that Tasklist has (assignee, priority, process visualization) are unnecessary and perhaps distracting. I think it makes sense to mention that you can also go through Operate and Tasklist, but it is not necessary to achieve the stated goal. If you believe the "get started" guides should feature Operate and Tasklist, then we can talk about changing their goal. Within the PM team, the focus has been around getting to 'hello world'. When I learned Python scripting (which is my background- I'm not a pro dev here), "hello world" happens in the console within a second of writing or editing the code with as little context change as possible. |
Co-authored-by: Cole Isaac <82131455+conceptualshark@users.noreply.github.com>
Co-authored-by: Cole Isaac <82131455+conceptualshark@users.noreply.github.com>
Co-authored-by: Cole Isaac <82131455+conceptualshark@users.noreply.github.com>
Co-authored-by: Cole Isaac <82131455+conceptualshark@users.noreply.github.com>
The preview environment relating to the commit 86b4640 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4401/index.html |
Description
Update the https://docs.camunda.io/docs/next/guides/orchestrate-human-tasks/ topic to include Play, milestone creation, and review as steps before running it on the cluster.
Relates to issue #4183.
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).