Details
-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
2
-
Not defined
-
3 - Expected
Description
Context
I'm trying to market Optimize by saying it requires no additional setup and you can immediately get process insights. It's always there, collecting data for analysis. However, the "camunda-cloud-get-started/docker-compose.yaml" file doesn't include Optimize, nor does the "Setting up your first development process" instructions. In addition, describing "Setting up your first development process" only focuses on the development process. We should consider the entire process automation lifecycle in our getting started documentation.
The desired user journey is as follows:
- Decide to automate the first process
- Download all necessary files in 1 step, including Optimize
- Easily set up Camunda applications
- Model the first process, create a user task form, and automate a service task
- Execute the process a few times
- View resulting data in Optimize
Acceptance Criteria (Required on creation):
- Include Optimize and Identity into camunda-cloud-get-started/docker-compose.yaml
- Documentation communicates that the getting started process also includes analyzing their new process in Optimize
- The Optimize section in the Getting Started part communicates the desired workflow, shown above
Hints (Optional):
- joshua.windels has volunteered to help with the docker-compose section
- Retitling the "Integrating Optimize" section should be pushed to the public-facing branch